CloudStatus

Npmjs Status Updates

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 640 days ago - Mon 25 Jul 2016 14:59 (GMT)

Source: Npmjs - npm

Npmjs History

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 640 days ago - Mon 25 Jul 2016 14:58 (GMT)

More info

Increased 503 rates

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 640 days ago - Mon 25 Jul 2016 14:06 (GMT)

More info

Increased 503 rates

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 640 days ago - Mon 25 Jul 2016 14:05 (GMT)

More info

Increased 503 rates

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 640 days ago - Mon 25 Jul 2016 13:19 (GMT)

More info

Slew of 503s on npmjs.com

Jul 20, 18:10 UTC Resolved - The npmjs.com website was down for up to 15 minutes today, between 10:30 AM PT and 10:45 AM PT. This was due to a web spider, which slammed the website with a 500% spike in requests in the span of that time. We have identified the bot and banned its user agent.

About 645 days ago - Wed 20 Jul 2016 18:11 (GMT)

More info

Reported 502s serving tarballs to some regions

Jul 6, 17:01 UTC Resolved - Issues with tarball serving should be resolved now. A writeup of the outage will be made available on the npmjs.org blog.Jul 6, 14:54 UTC Identified - We have identified the root cause of the issue serving some tarballs and are currently executing a fix.Jul 6, 13:47 UTC Update - we have confirmed the issue and are working on identificationJul 6, 13:38 UTC Investigating - We are currently investigating this issue.

About 659 days ago - Wed 6 Jul 2016 17:02 (GMT)

More info

Reported 502s serving tarballs to some regions

Jul 6, 14:54 UTC Identified - We have identified the root cause of the issue serving some tarballs and are currently executing a fix.Jul 6, 13:47 UTC Update - we have confirmed the issue and are working on identificationJul 6, 13:38 UTC Investigating - We are currently investigating this issue.

About 659 days ago - Wed 6 Jul 2016 14:55 (GMT)

More info

Reported 502s serving tarballs to some regions

Jul 6, 13:47 UTC Update - we have confirmed the issue and are working on identificationJul 6, 13:38 UTC Investigating - We are currently investigating this issue.

About 659 days ago - Wed 6 Jul 2016 13:47 (GMT)

More info

Reported 502s serving tarballs to some regions

Jul 6, 13:38 UTC Investigating - We are currently investigating this issue.

About 659 days ago - Wed 6 Jul 2016 13:39 (GMT)

More info

Some couchdb hosts are behind

Jun 16, 22:46 UTC Resolved - The couchdb in question rebooted; registry package metadata should be up to date.Jun 16, 22:38 UTC Investigating - Some registry requests will have stale data.

About 679 days ago - Thu 16 Jun 2016 22:46 (GMT)

More info