CloudStatus

Npmjs Status Updates

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 534 days ago - Sat 6 Aug 2016 02:00 (GMT)

Source: Npmjs - npm

Npmjs History

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 534 days ago - Fri 5 Aug 2016 15:05 (GMT)

More info

skimdb.npmjs.com unavailable

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 534 days ago - Fri 5 Aug 2016 14:23 (GMT)

More info

skimdb.npmjs.com unavailable

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 534 days ago - Fri 5 Aug 2016 11:40 (GMT)

More info

skimdb.npmjs.com unavailable

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 534 days ago - Fri 5 Aug 2016 11:39 (GMT)

More info

Intermittent website timeouts and 503's

Aug 3, 13:19 UTC Resolved - Starting at 11:13 UTC our monitoring started reporting increased 503 and timeout rate originating from the website caused by increased crawler traffic. While investigating the issue we discovered that some of our services weren't configured to load balance across database servers, which caused one of them to become overloaded due to increased traffic. We reconfigured our services to alleviate that and saw error and timeout rates drop to base levels around 12:46 UTC .

About 536 days ago - Wed 3 Aug 2016 13:20 (GMT)

More info

Increased 503 rates

Jul 26, 16:44 UTC Resolved - Our monitoring indicates that no more burst were registered after 14:23 UTC . We are still investigating the root cause.Jul 26, 14:45 UTC Monitoring - Our monitoring registered a short burst of increased 503 rates, starting at 14:03 UTC and ending at 14:23 UTC . We are monitoring the situation and increasing monitoring in order to determine the root cause.

About 544 days ago - Tue 26 Jul 2016 16:45 (GMT)

More info

Increased 503 rates

Jul 26, 14:45 UTC Monitoring - Our monitoring registered a short burst of increased 503 rates, starting at 14:03 UTC and ending at 14:23 UTC . We are monitoring the situation and increasing monitoring in order to determine the root cause.

About 544 days ago - Tue 26 Jul 2016 14:46 (GMT)

More info

Increased 503 rates

Jul 25, 17:08 UTC Resolved - We confirmed that 503 rates have dropped down to base levels for an extended period of time. No root cause has been determined yet, but we will continue investigating.Jul 25, 14:58 UTC Monitoring - 503 rates have dropped down. We are continuing to monitor the incident.Jul 25, 14:05 UTC Investigating - We've confirmed that the situation is an on-going, albeit intermittent problem and are investigating.Jul 25, 13:19 UTC Monitoring - Starting at 12:30 UTC we saw an increase in 503 responses from the registry. The situation seemed to have resolved at 13:10 UTC , but we will continue monitoring and investigating the reasons of this outage.

About 545 days ago - Mon 25 Jul 2016 17:09 (GMT)

More info

Increased 503 rates

Jul 25, 14:58 UTC Monitoring - 503 rates have dropped down. We are continuing to monitor the incident.Jul 25, 14:05 UTC Investigating - We've confirmed that the situation is an on-going, albeit intermittent problem and are investigating.Jul 25, 13:19 UTC Monitoring - Starting at 12:30 UTC we saw an increase in 503 responses from the registry. The situation seemed to have resolved at 13:10 UTC , but we will continue monitoring and investigating the reasons of this outage.

About 545 days ago - Mon 25 Jul 2016 15:01 (GMT)

More info

Increased 503 rates

Jul 25, 14:58 UTC Monitoring - 503 rates have dropped down. We are continuing to monitor the incident.Jul 25, 14:05 UTC Investigating - We've confirmed that the situation is an on-going, albeit intermittent problem and are investigating.Jul 25, 13:19 UTC Monitoring - Starting at 12:30 UTC we saw an increase in 503 responses from the registry. The situation seemed to have resolved at 13:10 UTC , but we will continue monitoring and investigating the reasons of this outage.

About 545 days ago - Mon 25 Jul 2016 14:58 (GMT)

More info