All Systems Operational

About This Site

npm loves you. Here is some info about how well it's doing. (You can also follow these updates at @npmstatus on Twitter!)

Registry Reads ? Operational
Website Reads ? Operational
US East (NYC) Operational
US East (ASH) Operational
US East (IAD) Operational
US East (ATL) Operational
US Central (DAL) Operational
US Central (CHI) Operational
US West (LAX) Operational
US West (SJC) Operational
Europe (FRA) Operational
Europe (AMS) Operational
Europe (LON) Operational
Asia/Pacific (AU) Operational
Asia/Pacific (TYO) Operational
Asia/Pacific (NZ) Operational
Asia/Pacific (SIN) Operational
ec2-us-east-1 Operational
ec2-us-west-2 Operational
www ? Operational
replicate.npmjs.com ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Registry Uptime
Fetching
Registry Response Time
Fetching
Website Uptime
Fetching
Website Response Time
Fetching
Past Incidents
Mar 30, 2017
Resolved - we have verified that "unpublish -f" is back to working normally.
Mar 30, 02:00 UTC
Monitoring - We have pushed and tested a fix for forced package unpublishes and are watching logs to verify.
Mar 30, 01:14 UTC
Identified - A bug has been identified related to "npm unpublish -f", resulting in packages only partially being removed from the registry. This results in the packages continuing to be installable, but in users being unable to publish updates. We are currently working on a fix, and will keep this issue updated.
Mar 29, 19:22 UTC
Mar 28, 2017
Resolved - This incident has been resolved.
Mar 28, 14:52 UTC
Monitoring - orignal configuration has been restored we are keeping an eye on things.
Mar 28, 14:40 UTC
Identified - A networking issue caused many authentication requests to our eu servers timeout.
We redirected this traffic to us_east for the time being and error rates have dropped.
Mar 28, 14:02 UTC
Investigating - We are currently investigating this issue.
Mar 28, 13:50 UTC
Mar 27, 2017

No incidents reported.

Mar 26, 2017

No incidents reported.

Mar 25, 2017
Resolved - Everything looks clear.
Mar 25, 03:31 UTC
Monitoring - The bug that was causing too many couchdb document updates has been fixed, and changes should now be flowing through the system at a normal rate again. We're monitoring to make sure the backlog drains as expected.
Mar 24, 23:17 UTC
Identified - We've identified the root cause of the replication delays. Publications have been accepted & stored, but replication on our CouchDB instances is behind because of unexpected load caused by a bug elsewhere that creates many document updates when certain package data is changed. We're working on a fix.
Mar 24, 21:18 UTC
Investigating - We are investigating lag on replicating publications to our leaf nodes as well as downstream to registry mirrors.
Mar 24, 20:28 UTC
Mar 23, 2017

No incidents reported.

Mar 22, 2017

No incidents reported.

Mar 21, 2017

No incidents reported.

Mar 20, 2017

No incidents reported.

Mar 19, 2017

No incidents reported.

Mar 18, 2017

No incidents reported.

Mar 17, 2017
Resolved - We've resolved the problem that was causing delayed package publishes. All previous and current new package publishes should now work as expected.
Mar 17, 16:33 UTC
Monitoring - A fix has been implemented for the delayed package publishes and we are monitoring the results.
Mar 17, 15:32 UTC
Identified - We are currently investigating an issue where newly published package versions are delayed and therefore are inaccessible for installation. They appear updated on the website and the CLI does not throw an error on publish, yet an `npm install` of the newly published package version may fail. We've identified the source of the issue and are actively fixing the issue.
Mar 17, 15:21 UTC
Mar 16, 2017

No incidents reported.