I'm opening this issue because:

• [x] npm is crashing.
• [x] npm is producing an incorrect install.
• [x] npm is doing something I don't understand.
• [x] npm is producing incorrect or undesirable behavior.

all of the above.

What's going wrong?

This afternoon all servers in our AWS EU-Frankfurt environment started throwing the error regardless of what package we are trying to install

npm ERR! code E418 npm ERR! 418 I'm a teapot: commander@~2.3.0

It then locks up and does not exit the process.

How can the CLI team reproduce the problem?

npm install

There is nothing being written to the npm-debug.log as the process does not do anything

supporting information:

• npm -v prints: 5.6.0

• node -v prints: 8.9.0

• npm config get registry prints: registry.npmjs.org/

• Windows, OS X/macOS, or Linux?: Amazon Linux AMI release 2017.09

• Network issues:

  • Geographic location where npm was run: AWS - EU
  • [x ] I use a proxy to connect to the npm registry.
  • [x ] I use a proxy to connect to the web.
  • [x ] I use a proxy when downloading Git repos.
  • [ ] I access the npm registry via a VPN
  • [ ] I don't use a proxy, but have limited or unreliable internet access.

• Container: No container.