CloudStatus

Npmjs Status Updates

private package issues.

Dec 13, 02:18 UTC Update - things should be back to normal. we are monitoring private package access and billing. A few more cleanup actions will follow in the morning to ensure that accounts are as they should be.Dec 12, 23:44 UTC Monitoring - Billing information should now be correct for most customers. we are restoring some missing changes from within the last 24 hours.Dec 12, 23:21 UTC Update - The mitigation has been deployed and access to private packages has been restored. The website may still show that there is no payment information.Dec 12, 23:06 UTC Identified - the issue has been identified but we are still working on the mitigation.Dec 12, 22:40 UTC Update - we’re deploying a potential mitigation to the issueDec 12, 22:26 UTC Investigating - some customers are unable to access private packages. we are investigating.

About 215 days ago - Wed 13 Dec 2017 02:18 (GMT)

Source: Npmjs - npm

Npmjs History

private package issues.

Dec 12, 23:44 UTC Monitoring - Billing information should now be correct for most customers. we are restoring some missing changes from within the last 24 hours.Dec 12, 23:21 UTC Update - The mitigation has been deployed and access to private packages has been restored. The website may still show that there is no payment information.Dec 12, 23:06 UTC Identified - the issue has been identified but we are still working on the mitigation.Dec 12, 22:40 UTC Update - we’re deploying a potential mitigation to the issueDec 12, 22:26 UTC Investigating - some customers are unable to access private packages. we are investigating.

About 215 days ago - Tue 12 Dec 2017 23:45 (GMT)

More info

private package issues.

Dec 12, 23:21 UTC Update - The mitigation has been deployed and access to private packages has been restored. The website may still show that there is no payment information.Dec 12, 23:06 UTC Identified - the issue has been identified but we are still working on the mitigation.Dec 12, 22:40 UTC Update - we’re deploying a potential mitigation to the issueDec 12, 22:26 UTC Investigating - some customers are unable to access private packages. we are investigating.

About 215 days ago - Tue 12 Dec 2017 23:21 (GMT)

More info

private package issues.

Dec 12, 23:06 UTC Identified - the issue has been identified but we are still working on the mitigation.Dec 12, 22:40 UTC Update - we’re deploying a potential mitigation to the issueDec 12, 22:26 UTC Investigating - some customers are unable to access private packages. we are investigating.

About 215 days ago - Tue 12 Dec 2017 23:06 (GMT)

More info

private package issues.

Dec 12, 22:40 UTC Update - we’re deploying a potential mitigation to the issueDec 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:41 (GMT)

More info

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:27 (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