Resolved -
Our CDN continues to monitor, but given several hours of normal performance we are resolving this incident. We'll re-open it if the situation deteriorates again.
Mar 28, 08:53 UTC

Update -
Performance has returned almost to normal, but the attack is still under way. You can monitor our CDN's status directly at their own incident report at https://status.fastly.com/incidents/pvh7f631yx5f
Mar 28, 03:38 UTC

Monitoring -
Along with GitHub and other services today, we are feeling the effects of an unprecedentedly large and sophisticated DDoS attack. We are not the target of the attack, but we share infrastructure with the target and are being hit by side-effects of the attack.

Our CDN provider are hard at work mitigating the attack, and we will update here as things develop.
Mar 27, 22:03 UTC

For 2 hours 8am - 10am Pacific time a small percentage of requests, approximately 2%, for package tarballs were timing out (HTTP 503). This issue has now been corrected, but we are conducting a more detailed investigation into the root cause.
Mar 21, 17:31 UTC

The npmjs.com website was briefly offline at around 15:30 PDT today. The redis service used for caching was unavailable for a short time and the site was most distressed about the absence. It has received counseling.
Mar 20, 23:32 UTC

The website was sporadically available over the course of about 50 minutes this morning as a result of a major network problem in Amazon's AWS us-west-2 region. Unlike the registry itself, the website is not completely redundant across AWS east and west regions. We have long-term plans in place to improve this design and we are continuing to work towards them.
Mar 20, 15:09 UTC

A misconfiguration caused a production push to the registry to fail, leading to 120 seconds of registry unavailability from 13:34 - 13:36 Pacific Time before the change was rolled back. We have modified our push process to catch this form of error in future.
Mar 19, 21:19 UTC