Npmjs Status Updates
Increased 504 rates for tarballs
Mar 17, 20:11 UTC Resolved - the servers in question have been removed from rotation. access has been confirmed.Mar 17, 19:06 UTC Update - Some recently-published packages are temporarily unavailable due to capacity issues on older package servers. The older servers are being taken out of rotation, which will restore access to these packages.Mar 17, 18:58 UTC Identified - We are seeing increased error rates due to faulty tarballs servers. We are working on removing those servers from rotation.
About 675 days ago - Thu 17 Mar 2016 20:11 (GMT)
Source: Npmjs - npm
elevated 503s for json from the SJC PoP
Mar 11, 16:16 UTC Resolved - This incident has been resolved.Mar 11, 15:24 UTC Investigating - We are currently investigating this issue.
About 681 days ago - Fri 11 Mar 2016 16:16 (GMT)More info
503s on installs
Mar 10, 21:35 UTC Resolved - The problem has been resolved.Mar 10, 21:17 UTC Investigating - There is some disruption in registry traffic. The registry team is looking into it.
About 682 days ago - Thu 10 Mar 2016 21:35 (GMT)More info
elevated 404 rates for scoped modules
Mar 9, 19:16 UTC Resolved - From 10:17am PST to 10:39am PST today the registry was returning 404s for some scoped module tarballs. We rolled out a configuration change to our CDN and served an incorrect version format in package.json files. The incident was resolved by rolling back to the previous configuration. 404 rates are now back to normal.
About 683 days ago - Wed 9 Mar 2016 19:16 (GMT)More info
Increased registry 503 rates
Mar 2, 04:33 UTC Resolved - We've now resolved this issue for all the packages. We will be publishing a post-mortem regarding this issue. Our apologies!Mar 2, 02:26 UTC Identified - We've resolved the issue for most of packages and are currently working on full resolution.Mar 2, 02:15 UTC Investigating - We are seeing increased rates of 503 responses from the registry and we're investigating.
About 690 days ago - Wed 2 Mar 2016 04:33 (GMT)More info
Investigating 503 rate on registry
Feb 22, 22:16 UTC Resolved - The issues with the POP appear to be resolved.Feb 22, 21:32 UTC Update - The POP outage is affecting www traffic as well.Feb 22, 21:29 UTC Investigating - Investigations currently point at problems with one of our CDN's POPs.
About 699 days ago - Mon 22 Feb 2016 22:16 (GMT)More info
Difficulties with our CDN
Feb 18, 21:15 UTC Resolved - Registry 503 responses were elevated because of errors with one of the points of presence of our CDN provider. They identified & fixed the incident. (You can read more details in their incident report here: https://status.fastly.com/incidents/gjgcmfljjdpk .) Registry responses should be back to normal.Feb 18, 20:22 UTC Investigating - Registry services are responding with 503 errors at an elevated rate possibly because of issues with our CDN. We are investigating.
About 703 days ago - Thu 18 Feb 2016 21:15 (GMT)More info
Increased WWW 503 rates for some users
Feb 18, 03:13 UTC Resolved - We started observing short influxes of increased 503 rates for some WWW users starting at around 10:30 UTC today, up to 15:00 UTC today. This was identified as a misconfiguration and has since been fixed, with additional steps being taken to prevent this class of a problem in the future. Our apologies.
About 703 days ago - Thu 18 Feb 2016 03:13 (GMT)More info
Feb 5, 00:33 UTC Resolved - Publications are back to normal.Feb 5, 00:25 UTC Monitoring - Replication has been repaired and all endpoints are now up to date with reality.Feb 5, 00:15 UTC Identified - There is an ongoing delay with replication of new package publishes. Publishes are successful but are not visible everywhere. Engineers are working on the issue and we will update shortly.Feb 4, 23:43 UTC Monitoring - Publications were failing because of a bug in our new publication flow that stacked up open connections to the registry write primary. We've rolled back to earlier code that is a little slower but doesn't leak connections while we debug the problem in our testing environment. Publications should now be succeeding.Feb 4, 23:09 UTC Investigating - We are investigating failing writes to the registry.
About 717 days ago - Fri 5 Feb 2016 00:33 (GMT)More info
503s on www and auth failures on CLI
Jan 30, 08:10 UTC Resolved - Our authentication services were briefly overloaded by an external event, leading to auth failures on package pages and the command line. Monitoring detected the incident and it was resolved after approximately 30 minutes of instability.
About 722 days ago - Sat 30 Jan 2016 08:10 (GMT)More info
Elevated 503 rates for users in Europe
Jan 28, 23:16 UTC Resolved - The registry was returning elevated 503 rates to our users in Europe from 7:00 UTC to 13:00 UTC due to a misconfiguration of one of the package servers. Our apologies!
About 724 days ago - Thu 28 Jan 2016 23:16 (GMT)More info