CloudStatus

Npmjs Status Updates

Increased 503 rates for public packages

Jun 9, 14:30 UTC Resolved - We've identified the issue as a case of a service's process getting stuck and resolved it by rolling the affected service.Jun 9, 14:25 UTC Investigating - We're currently investigating issues related to accessing scoped packages.

About 226 days ago - Fri 9 Jun 2017 14:30 (GMT)

Source: Npmjs - npm

Npmjs History

elevated level of 503s in Europe

May 2, 15:19 UTC Resolved - This incident has been resolved.May 2, 15:08 UTC Monitoring - A fix has been implemented and we are monitoring the results.May 2, 15:00 UTC Investigating - We are currently seeing an elevated level of 503s for our Points of Presence in Europe, affecting both the registry and the website.

About 51 days ago - Fri 1 Dec 2017 10:58 (GMT)

More info

503s for scoped packages

May 4, 13:52 UTC Resolved - This incident has been resolved.May 4, 12:38 UTC Monitoring - A fix has been implemented and we are monitoring the results.May 4, 12:27 UTC Investigating - We are currently experiencing 503s for scoped packages, the team is investigating.

About 51 days ago - Fri 1 Dec 2017 10:58 (GMT)

More info

Tarball and package pages outage

May 8, 21:18 UTC Resolved - We have identified the outage to be caused by one of our package servers' TLS terminator shutting down due to a misconfiguration. In addition to this, that service did not restart properly, causing need for human intervention. We are taking steps to fix the configuration that caused the incident and add more detailed monitoring.May 8, 20:50 UTC Investigating - We are currently investigating an outage causing unavailability of registry's tarballs and website's package pages.

About 51 days ago - Fri 1 Dec 2017 10:58 (GMT)

More info

elevated level of 503s on /search endpoint

May 9, 21:10 UTC Resolved - This incident has been resolved.May 9, 19:38 UTC Monitoring - A fix has been implemented and we are monitoring the results.May 9, 19:24 UTC Investigating - We are currently seeing an elevated level of 503s on all requests to our /search endpoint. The team is currently investigating.

About 51 days ago - Fri 1 Dec 2017 10:58 (GMT)

More info

package tarball issues in us-east.

Apr 21, 02:36 UTC Resolved - Appears to have been a network flicker. Apologies for the trouble!Apr 21, 02:35 UTC Investigating - We are investigating an issue with a tarball server in us-east.

About 275 days ago - Fri 21 Apr 2017 02:37 (GMT)

More info

package tarball issues in us-east.

Apr 21, 02:35 UTC Investigating - We are investigating an issue with a tarball server in us-east.

About 275 days ago - Fri 21 Apr 2017 02:36 (GMT)

More info

replication lag on publications

Mar 25, 03:31 UTC Resolved - Everything looks clear.Mar 24, 23:17 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, 21:18 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, 20:28 UTC Investigating - We are investigating lag on replicating publications to our leaf nodes as well as downstream to registry mirrors.

About 293 days ago - Mon 3 Apr 2017 22:42 (GMT)

More info

increased rate of 503s in eu

Mar 28, 14:52 UTC Resolved - This incident has been resolved.Mar 28, 14:40 UTC Monitoring - orignal configuration has been restored we are keeping an eye on things.Mar 28, 14:02 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, 13:50 UTC Investigating - We are currently investigating this issue.

About 293 days ago - Mon 3 Apr 2017 22:42 (GMT)

More info

forced unpublishes currently failing

Mar 30, 02:00 UTC Resolved - we have verified that "unpublish -f" is back to working normally.Mar 30, 01:14 UTC Monitoring - We have pushed and tested a fix for forced package unpublishes and are watching logs to verify.Mar 29, 19:22 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.

About 293 days ago - Mon 3 Apr 2017 22:42 (GMT)

More info

Delayed Package Publishes

Mar 17, 16:33 UTC 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, 15:32 UTC Monitoring - A fix has been implemented for the delayed package publishes and we are monitoring the results.Mar 17, 15:21 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.

About 310 days ago - Fri 17 Mar 2017 16:34 (GMT)

More info