CloudStatus

Npmjs Status Updates

Elevatse 503s from SIN pop

Nov 7, 10:51 UTC Update - We made some changes to our cdn configuration to route more requests from SIN away from their previous backends. It looks like 503 rate is dropping but not resolved.Nov 7, 10:35 UTC Investigating - we are seeing elevated 503s from our cdns singapore pop.

About 535 days ago - Mon 7 Nov 2016 10:51 (GMT)

Source: Npmjs - npm

Npmjs History

Elevatse 503s from SIN pop

Nov 7, 10:35 UTC Investigating - we are seeing elevated 503s from our cdns singapore pop.

About 535 days ago - Mon 7 Nov 2016 10:36 (GMT)

More info

download counts API server replaced

Oct 28, 17:57 UTC Resolved - we have replaced and tuned-up https://api.npmjs.org/downloads/point/last-month, such that weekly and monthly statistics will again return results.

About 545 days ago - Fri 28 Oct 2016 17:58 (GMT)

More info

replicate.npmjs.com replaced

Oct 21, 21:53 UTC Resolved - Today we replaced replicate.npmjs.com, the server that provides a public replication endpoint for npm packages. The new server is running on faster 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 552 days ago - Fri 21 Oct 2016 21:53 (GMT)

More info

Connectivity disruption for users in certain areas

Oct 21, 20:47 UTC Resolved - Our systems are back to full operation. Local DNS issues are still lingering for some users.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 20:48 (GMT)

More info

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 20:28 (GMT)

More info

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