CloudStatus

Npmjs Status Updates

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

Source: Npmjs - npm

Npmjs History

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

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 545 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 545 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 545 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 550 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 564 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 564 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 564 days ago - Wed 6 Jul 2016 13:47 (GMT)

More info