CloudStatus

Npmjs Status Updates

private package issues.

Dec 12, 22:26 UTC Investigating - some customers are unable to access private packages. we are investigating.

About 215 days ago - Tue 12 Dec 2017 22:26 (GMT)

Source: Npmjs - npm

Npmjs History

increased timeouts on registry and website

Jul 13, 23:18 UTC Resolved - Between the 3:55 and 4:10 (PDT ) an increased rate of 503s was observed on the registry and npmjs.com website. We believe we have isolated the underlying issue and corrected it. We will be looking into adding additional monitoring, to identify this specific category of failure faster.

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

More info

Delays in ACL & Payment Status changes

Aug 23, 03:46 UTC Resolved - The queue has caught up. Package ownership & scope payment changes should be reflected immediately.Aug 22, 23:22 UTC Monitoring - We've rolled out a fix for the lagging queue, and are monitoring its progress. Delays are expected.Aug 22, 21:30 UTC Identified - We have identified the slowdown as coming from an unusually high number of incoming invalidation events. The backlog is being slowly worked through, but not at an acceptable pace. We're now working on mitigations so we can process the backlog more rapidly and keep up with the incoming volume.Aug 22, 19:30 UTC Investigating - An invalidation queue is running behind. We are investigating the root cause. Users upgrading an unpaid org or user to a paid user or org may experience errors when accessing existing private packages. New private packages are unaffected. Adding or removing maintainers from a package will not be reflected in "npm owner ls".

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

More info

500s on package servers and npmjs.com

Sep 6, 23:38 UTC Resolved - We've resolved an issue regarding 500s on package servers and npmjs.com. Package installs and npmjs.com page views should have returned to normal. We identified the culprit as a bot making an unusually high rate of requests on a route that was not cached. We've blocked the offending IP and intend to implement additional measures to prevent this from occurring again in the future.Sep 6, 21:36 UTC Investigating - We are currently investigating an issue where we are seeing intermittent 500s on package installs and pages from npmjs.com. Packages servers are experiencing delays, and you may notice website and installation failures.

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

More info

503s for scoped packages

Sep 20, 21:24 UTC Resolved - This incident has been resolved.Sep 20, 20:03 UTC Monitoring - A fix has been implemented and we are monitoring the results.Sep 20, 16:24 UTC Identified - The issue has been identified and a fix is being implemented.Sep 20, 15:59 UTC Investigating - We are currently investigating an uptick in 503 responses for scoped package requests.

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

More info

Increased 503 Rate in SE Asia

Sep 22, 08:05 UTC Resolved - We are not seeing increased error rates anymore. We'll continue monitoring this incident internally.Sep 22, 06:48 UTC Monitoring - The error rate has decreased. We are monitoring and preparing to reroute if the error rate increases.Sep 22, 06:45 UTC Investigating - We're seeing a high error rate from our SE Asia point-of-presence, registry and website are affected. Investigating!

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

More info

503s on packages

Sep 25, 13:37 UTC Resolved - Between 11:10 UTC until 12:30 UTC today we saw an elevated rate of 503 on requests for packages and package data. It should now be resolved.

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

More info

increased rate of 503s in European and East Coast POPs

Oct 18, 21:39 UTC Resolved - The publishing and installation issues were related to upstream network connectivity issues with AWS.Oct 18, 21:16 UTC Investigating - we are seeing an increased rate of 503s in npm's European and East-Coast servers. The issue is affecting these users' ability to publish modules and to install scoped modules. Our ops team is currently investigating.

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

More info

Registry and Website reads

Oct 23, 00:57 UTC Resolved - This incident has been resolved.Oct 22, 23:40 UTC Investigating - Seeing an increased rate of 503s on website package pages as well as during installs in multiple regions

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

More info

503s on npmjs website and package pages

Oct 25, 21:23 UTC Resolved - This incident has been resolved.Oct 25, 20:54 UTC Monitoring - We're currently monitoring a spike in 503s on the npmjs.com website.

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

More info

Increased rate of 503s on packages

Nov 8, 23:23 UTC Resolved - we were seeing an increased rate of 503s, due to a bug in our failover logic. This bug is being addressed to prevent these timeouts in the future.Nov 8, 19:17 UTC Investigating - We're currently seeing an increased rate of 503s accessing some packages

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

More info