Increased 502 and 503 rates for the website
Incident Report for npm
Resolved
At 7:55 UTC our monitoring alerted us to increased 502 and 503 rates for the website. We've determined the culprit to be a stuck Node.js process and restarted it at 8:12 UTC, which fixed the issue immediately. We will continue investigating the root cause of this problem.
Posted Aug 19, 2016 - 10:20 UTC