CloudStatus

Npmjs Status Updates

elevated rates of 500s from the registry

Sep 2, 18:49 UTC Resolved - 50x error rates for the registry appear to be back to normal.Sep 2, 18:37 UTC Monitoring - We've identified some wedged processes & restarted them. Monitoring response rates to confirm the fix.Sep 2, 18:12 UTC Investigating - We are investigating elevated rates of 503s and 504s on registry requests right now.

About 601 days ago - Fri 2 Sep 2016 18:49 (GMT)

Source: Npmjs - npm

Npmjs History

elevated rates of 500s from the registry

Sep 2, 18:37 UTC Monitoring - We've identified some wedged processes & restarted them. Monitoring response rates to confirm the fix.Sep 2, 18:12 UTC Investigating - We are investigating elevated rates of 503s and 504s on registry requests right now.

About 601 days ago - Fri 2 Sep 2016 18:38 (GMT)

More info

elevated rates of 500s from the registry

Sep 2, 18:12 UTC Investigating - We are investigating elevated rates of 503s and 504s on registry requests right now.

About 601 days ago - Fri 2 Sep 2016 18:14 (GMT)

More info

elevated rates of 500s from the registry

Sep 2, 18:12 UTC Investigating - We are investigating elevated rates of 503s and 504s on registry requests right now.

About 601 days ago - Fri 2 Sep 2016 18:12 (GMT)

More info

Increased 503 rates for European users

Aug 28, 17:51 UTC Resolved - We've replaced affected hardware and European users should be going through our European infrastructure again.Aug 28, 15:05 UTC Monitoring - We redirected European traffic to other, healthy regions, as we continue to restore our European infrastructure.Aug 28, 14:58 UTC Identified - We're currently experiencing a hardware failure in our European region.

About 606 days ago - Sun 28 Aug 2016 17:51 (GMT)

More info

Increased 503 rates for European users

Aug 28, 15:05 UTC Monitoring - We redirected European traffic to other, healthy regions, as we continue to restore our European infrastructure.Aug 28, 14:58 UTC Identified - We're currently experiencing a hardware failure in our European region.

About 606 days ago - Sun 28 Aug 2016 15:08 (GMT)

More info

Increased 503 rates for European users

Aug 28, 15:05 UTC Monitoring - We redirected European traffic to other, healthy regions, as we continue to restore our European infrastructure.Aug 28, 14:58 UTC Identified - We're currently experiencing a hardware failure in our European region.

About 606 days ago - Sun 28 Aug 2016 15:06 (GMT)

More info

Increased 503 rates for European users

Aug 28, 14:58 UTC Identified - We're currently experiencing a hardware failure in our European region.

About 606 days ago - Sun 28 Aug 2016 14:59 (GMT)

More info

Increased 503 rates for European users

Aug 28, 14:58 UTC Identified - We're currently experiencing a hardware failure in our European region.

About 606 days ago - Sun 28 Aug 2016 14:58 (GMT)

More info

public-skimdb is offline while we investigate a configuration error

Aug 24, 23:35 UTC Resolved - skimdb.npmjs.com is back in service. The sequence number advertised by couchdb has changed. Your follow scripts might need to be updated.Aug 24, 21:08 UTC Monitoring - A brand new registry public replication point has been provisioned & is catching up. It'll be online at the usual url & IP address once its database is caught up.Aug 24, 20:22 UTC Investigating - It will be back online as soon as we have repaired the error.

About 610 days ago - Wed 24 Aug 2016 23:36 (GMT)

More info

public-skimdb is offline while we investigate a configuration error

Aug 24, 21:08 UTC Monitoring - A brand new registry public replication point has been provisioned & is catching up. It'll be online at the usual url & IP address once its database is caught up.Aug 24, 20:22 UTC Investigating - It will be back online as soon as we have repaired the error.

About 610 days ago - Wed 24 Aug 2016 21:09 (GMT)

More info