CloudStatus

Npmjs Status Updates

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

Source: Npmjs - npm

Npmjs History

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

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 610 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 611 days ago - Tue 23 Aug 2016 20:35 (GMT)

More info

Increased 502 and 503 rates for the website

Aug 19, 10:20 UTC Resolved - At 7:55 UTC our monitoring alerted us to increased 502 and 503 rates for the website. We've determined the culprit to be a stuck Node.js process and restarted it at 8:12 UTC , which fixed the issue immediately. We will continue investigating the root cause of this problem.

About 615 days ago - Fri 19 Aug 2016 10:21 (GMT)

More info

Intermittent website timeouts and 503s

Aug 15, 22:52 UTC Resolved - Starting at 22:06 UTC our monitoring started reporting increased 503 and timeout rate originating from the website. We detected what we think was an accidental mis-use of an endpoint that was creating extraordinary load. We have blocked the IP responsible and are contacting the user involved. This was resolved at 22:30 UTC .

About 619 days ago - Mon 15 Aug 2016 23:00 (GMT)

More info

Intermittent website timeouts and 503s

Aug 15, 22:52 UTC Resolved - Starting at 22:06 UTC our monitoring started reporting increased 503 and timeout rate originating from the website. This was resolved at 22:30 UTC .

About 619 days ago - Mon 15 Aug 2016 22:53 (GMT)

More info

skimdb.npmjs.com IP address change & sequence number jump

Aug 6, 02:13 UTC Completed - Cutover is complete. DNS will take time to propagate, so the older hardware is still serving the unscoped public registry database and will continue to do so until Monday.Aug 6, 02:01 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Aug 6, 01:07 UTC Scheduled - The hardware underlying skimdb.npmjs.com instance turned out to be under-provisioned. To cope with observed load we're replacing it with a faster instance. When we do this cutover, we'll also take the opportunity to assign a permanent IP address for skimdb.npmjs.com to help make cutting over to hot spares much smoother in the future. You will observe two changes: skimdb.npmjs.com will begin resolving to 52.205.193.105, and the advertised sequence number of the registry database in the couchdb changes feed will change.

About 629 days ago - Sat 6 Aug 2016 02:14 (GMT)

More info

skimdb.npmjs.com IP address change & sequence number jump

Aug 6, 02:01 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Aug 6, 01:07 UTC Scheduled - The hardware underlying skimdb.npmjs.com instance turned out to be under-provisioned. To cope with observed load we're replacing it with a faster instance. When we do this cutover, we'll also take the opportunity to assign a permanent IP address for skimdb.npmjs.com to help make cutting over to hot spares much smoother in the future. You will observe two changes: skimdb.npmjs.com will begin resolving to 52.205.193.105, and the advertised sequence number of the registry database in the couchdb changes feed will change.

About 629 days ago - Sat 6 Aug 2016 02:01 (GMT)

More info

skimdb.npmjs.com IP address change & sequence number jump

Aug 6, 01:07 UTC Scheduled - The hardware underlying skimdb.npmjs.com instance turned out to be under-provisioned. To cope with observed load we're replacing it with a faster instance. When we do this cutover, we'll also take the opportunity to assign a permanent IP address for skimdb.npmjs.com to help make cutting over to hot spares much smoother in the future. You will observe two changes: skimdb.npmjs.com will begin resolving to 52.205.193.105, and the advertised sequence number of the registry database in the couchdb changes feed will change.

About 629 days ago - Sat 6 Aug 2016 01:08 (GMT)

More info

skimdb.npmjs.com unavailable

Aug 5, 15:04 UTC Resolved - The new skimdb.npmjs.com should now be fully accessible.Aug 5, 14:23 UTC Monitoring - We replaced the failing host and repointed the DNS record. Please note that since the underlying host for skimdb.npmjs.com was replaced, the sequence number has changed. If you're following skimdb.npmjs.com for replication purposes, it is advisable to restart your followers from sequence 0.Aug 5, 11:39 UTC Identified - The underlying virtual host handling skimdb.npmjs.com traffic became unavailable. We are working on bringing up a replacement host.

About 629 days ago - Fri 5 Aug 2016 15:05 (GMT)

More info