CloudStatus

Npmjs Status Updates

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 506 days ago - Fri 2 Sep 2016 18:12 (GMT)

Source: Npmjs - npm

Npmjs History

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 506 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 511 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 511 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 511 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 511 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 511 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 515 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 515 days ago - Wed 24 Aug 2016 21:09 (GMT)

More info

public-skimdb is offline while we investigate a configuration error

Aug 24, 20:22 UTC Investigating - It will be back online as soon as we have repaired the error.

About 515 days ago - Wed 24 Aug 2016 20:22 (GMT)

More info

"fs" unpublished and restored

Aug 23, 20:34 UTC Resolved - For a few minutes today the package "fs" was unpublished from the registry in response to a user report that it was spam. It has been restored. This was a human error on my (@seldo's) part; I failed to properly follow our written internal process for checking if an unpublish is safe. My apologies to the users and builds we disrupted. More detail: the "fs" package is a non-functional package. It simply logs the word "I am fs" and exits. There is no reason it should be included in any modules. However, something like 1000 packages *do* mistakenly depend on "fs", probably because they were trying to use a built-in node module called "fs". Given this, we should have deprecated the module instead of unpublishing it, and this is what our existing process says we should do. If any of your modules are depending on "fs", you can safely remove it from your dependencies, and you should. But if you don't, things will continue to work indefinitely.

About 516 days ago - Tue 23 Aug 2016 20:35 (GMT)

More info