CloudStatus

Npmjs Status Updates

Connectivity disruption for users in certain areas

Oct 21, 18:24 UTC Update - Mitigation has significantly improved internal registry error rates. Users may still be unable to connect to npm due to DNS issues local to them.Oct 21, 16:40 UTC Update - For updates on how this global DNS incident is affecting our CDN, watch their status incident: https://status.fastly.com/incidents/50qkgsyvk9s4Oct 21, 14:10 UTC Monitoring - We have rolled out our workaround for the DDOS on our DNS provider. Error rates have dropped. Continuing to monitor to ensure that all services are working again.Oct 21, 13:03 UTC Update - We are acting on a plan to give ourselves backup DNS for our internal services. For more information on the DDOS that is causing this outage, you can read Dyn's status page: https://www.dynstatus.com/incidents/nlr4yrr162t8Oct 21, 12:14 UTC Identified - Our DNS provider is currently experiencing a DDoS. We are investigating potential solutions on our part.Oct 21, 12:10 UTC Investigating - We are investigating connectivity problems reported by our monitoring. We suspect that they might be disrupting service for users in certain geographical areas, but have no information about what the areas are exactly or what the root cause for disruption is.

About 552 days ago - Fri 21 Oct 2016 18:24 (GMT)

Source: Npmjs - npm

Npmjs History

Connectivity disruption for users in certain areas

Oct 21, 14:10 UTC Monitoring - We have rolled out our workaround for the DDOS on our DNS provider. Error rates have dropped. Continuing to monitor to ensure that all services are working again.Oct 21, 13:03 UTC Update - We are acting on a plan to give ourselves backup DNS for our internal services. For more information on the DDOS that is causing this outage, you can read Dyn's status page: https://www.dynstatus.com/incidents/nlr4yrr162t8Oct 21, 12:14 UTC Identified - Our DNS provider is currently experiencing a DDoS. We are investigating potential solutions on our part.Oct 21, 12:10 UTC Investigating - We are investigating connectivity problems reported by our monitoring. We suspect that they might be disrupting service for users in certain geographical areas, but have no information about what the areas are exactly or what the root cause for disruption is.

About 552 days ago - Fri 21 Oct 2016 14:11 (GMT)

More info

Connectivity disruption for users in certain areas

Oct 21, 13:03 UTC Update - We are acting on a plan to give ourselves backup DNS for our internal services. For more information on the DDOS that is causing this outage, you can read Dyn's status page: https://www.dynstatus.com/incidents/nlr4yrr162t8Oct 21, 12:14 UTC Identified - Our DNS provider is currently experiencing a DDoS. We are investigating potential solutions on our part.Oct 21, 12:10 UTC Investigating - We are investigating connectivity problems reported by our monitoring. We suspect that they might be disrupting service for users in certain geographical areas, but have no information about what the areas are exactly or what the root cause for disruption is.

About 552 days ago - Fri 21 Oct 2016 13:04 (GMT)

More info

Connectivity disruption for users in certain areas

Oct 21, 12:14 UTC Identified - Our DNS provider is currently experiencing a DDoS. We are investigating potential solutions on our part.Oct 21, 12:10 UTC Investigating - We are investigating connectivity problems reported by our monitoring. We suspect that they might be disrupting service for users in certain geographical areas, but have no information about what the areas are exactly or what the root cause for disruption is.

About 552 days ago - Fri 21 Oct 2016 12:15 (GMT)

More info

Connectivity disruption for users in certain areas

Oct 21, 12:10 UTC Investigating - We are investigating connectivity problems reported by our monitoring. We suspect that they might be disrupting service for users in certain geographical areas, but have no information about what the areas are exactly or what the root cause for disruption is.

About 552 days ago - Fri 21 Oct 2016 12:11 (GMT)

More info

skimdb.npmjs.com has been replaced

Oct 18, 20:56 UTC Resolved - Today we replaced skimdb.npmjs.com, the server that provides a public replication endpoint for un-scoped npm packages. The new server is running on new hardware, which should help solve stability issues that we have seen over the past several weeks. Users consuming the CouchDB _changes feed should reset their sequence number.

About 555 days ago - Tue 18 Oct 2016 20:58 (GMT)

More info

Increased 503s for the npmjs.com website

Oct 10, 05:41 UTC Resolved - A blip on a package metadata box left zombie connections on a DB box, consuming needed connections & causing 503s on the website. The old connections have been flushed and the service appears to have recovered.Oct 10, 04:47 UTC Monitoring - The server that failed came back online and we were able to reconstitute the services backing the npmjs.com website to mitigate the cause of the 503s. We are currently monitoring the situation.Oct 10, 04:31 UTC Investigating - We're currently seeing an increased number of 503 responses from the npmjs.com website due to an unanticipated server failure. We are currently investigating the situation.

About 564 days ago - Mon 10 Oct 2016 05:42 (GMT)

More info

Increased 503s for the npmjs.com website

Oct 10, 04:47 UTC Monitoring - The server that failed came back online and we were able to reconstitute the services backing the npmjs.com website to mitigate the cause of the 503s. We are currently monitoring the situation.Oct 10, 04:31 UTC Investigating - We're currently seeing an increased number of 503 responses from the npmjs.com website due to an unanticipated server failure. We are currently investigating the situation.

About 564 days ago - Mon 10 Oct 2016 04:47 (GMT)

More info

Increased 503s for the npmjs.com website

Oct 10, 04:31 UTC Investigating - We're currently seeing an increased number of 503 responses from the npmjs.com website due to an unanticipated server failure. We are currently investigating the situation.

About 564 days ago - Mon 10 Oct 2016 04:32 (GMT)

More info

replicate.npmjs.com outage

Oct 7, 23:17 UTC Resolved - Friday afternoon, between the hours of 2PM PDT and 4PM PDT , we experienced a partial outage of the registry's scoped replication endpoint. All systems are back online, and we have added additional monitoring to detect this category of failure faster in the future.

About 566 days ago - Fri 7 Oct 2016 23:18 (GMT)

More info

Increased 503 rate on tarball downloads served from Sydney

Sep 28, 05:45 UTC Resolved - The 503 rate has returned to nominal levels.Sep 28, 05:24 UTC Monitoring - 503 rate decreased, continuing to monitor.Sep 28, 04:59 UTC Investigating - Increased 503 rate on tarball downloads served from Sydney.

About 576 days ago - Wed 28 Sep 2016 05:45 (GMT)

More info