CloudStatus

Npmjs Status Updates

increased publish latency

Mar 24, 17:29 UTC Identified - We've identified the issue to be caused by a misconfiguration of some of the hosts which handle storing tarballs. We are working on resolving that misconfiguration.Mar 24, 17:16 UTC Investigating - we have noticed an increase in publish delay and failure rate. we are investigating

About 668 days ago - Thu 24 Mar 2016 17:29 (GMT)

Source: Npmjs - npm

Npmjs History

increased publish latency

Mar 24, 17:16 UTC Investigating - we have noticed an increase in publish delay and failure rate. we are investigating

About 668 days ago - Thu 24 Mar 2016 17:17 (GMT)

More info

Website and private package installation issues

Mar 24, 02:52 UTC Resolved - The failed hardware has been replaced and services have been switched back into redundant mode.Mar 24, 01:07 UTC Monitoring - All services have been failed over and service should be restored. We're double-checking our work before closing this incident.Mar 24, 00:51 UTC Update - We are failing over to redundant hardware.Mar 24, 00:43 UTC Identified - A hardware failure is causing website downtime and problems with installing private packages. Engineers are taking mitigation steps.

About 668 days ago - Thu 24 Mar 2016 02:53 (GMT)

More info

Website and private package installation issues

Mar 24, 01:07 UTC Monitoring - All services have been failed over and service should be restored. We're double-checking our work before closing this incident.Mar 24, 00:51 UTC Update - We are failing over to redundant hardware.Mar 24, 00:43 UTC Identified - A hardware failure is causing website downtime and problems with installing private packages. Engineers are taking mitigation steps.

About 669 days ago - Thu 24 Mar 2016 01:08 (GMT)

More info

Website and private package installation issues

Mar 24, 00:51 UTC Update - We are failing over to redundant hardware.Mar 24, 00:43 UTC Identified - A hardware failure is causing website downtime and problems with installing private packages. Engineers are taking mitigation steps.

About 669 days ago - Thu 24 Mar 2016 00:51 (GMT)

More info

Website and private package installation issues

Mar 24, 00:43 UTC Identified - A hardware failure is causing website downtime and problems with installing private packages. Engineers are taking mitigation steps.

About 669 days ago - Thu 24 Mar 2016 00:44 (GMT)

More info

increase 503 rate from our Australia based tarball servers

Mar 17, 22:04 UTC Resolved - Errors rates have been returned to normal.Mar 17, 21:47 UTC Investigating - We are currently investigating this issue.

About 675 days ago - Thu 17 Mar 2016 22:04 (GMT)

More info

Increased 504 rates for tarballs

Mar 17, 20:11 UTC Resolved - the servers in question have been removed from rotation. access has been confirmed.Mar 17, 19:06 UTC Update - Some recently-published packages are temporarily unavailable due to capacity issues on older package servers. The older servers are being taken out of rotation, which will restore access to these packages.Mar 17, 18:58 UTC Identified - We are seeing increased error rates due to faulty tarballs servers. We are working on removing those servers from rotation.

About 675 days ago - Thu 17 Mar 2016 20:11 (GMT)

More info

elevated 503s for json from the SJC PoP

Mar 11, 16:16 UTC Resolved - This incident has been resolved.Mar 11, 15:24 UTC Investigating - We are currently investigating this issue.

About 681 days ago - Fri 11 Mar 2016 16:16 (GMT)

More info

503s on installs

Mar 10, 21:35 UTC Resolved - The problem has been resolved.Mar 10, 21:17 UTC Investigating - There is some disruption in registry traffic. The registry team is looking into it.

About 682 days ago - Thu 10 Mar 2016 21:35 (GMT)

More info

elevated 404 rates for scoped modules

Mar 9, 19:16 UTC Resolved - From 10:17am PST to 10:39am PST today the registry was returning 404s for some scoped module tarballs. We rolled out a configuration change to our CDN and served an incorrect version format in package.json files. The incident was resolved by rolling back to the previous configuration. 404 rates are now back to normal.

About 683 days ago - Wed 9 Mar 2016 19:16 (GMT)

More info