CloudStatus

Npmjs Status Updates

Partially-failed publications earlier today

Mar 25, 18:39 UTC Investigating - A bad configuration released earlier in today caused package publications to fail partially, leaving an uninstallable version recorded in the package metadata. The visible symptom is that the registry will report that the version exists, but respond with a 404 when the tarball is requested. The misconfiguration has been fixed, but we are investigating now to identify the packages affected & clean up the metadata.

About 842 days ago - Fri 25 Mar 2016 18:40 (GMT)

Source: Npmjs - npm

Npmjs History

Partially-failed publications earlier today

Mar 25, 18:39 UTC Investigating - A mis-configuration earlier in the day caused package publications to fail partially, leaving an uninstallable version recorded in the package metadata. The misconfiguration has been fixed, but we are investigating now to identify the packages affected & clean up the metadata.

About 842 days ago - Fri 25 Mar 2016 18:39 (GMT)

More info

Increased publish error rates

Mar 25, 16:48 UTC Resolved - We've removed affected hardware from the publish path, and are working on adding additional capacity. Publishes should be back to normal. Our apologies.Mar 25, 16:43 UTC Identified - We're seeing increased error rates on publishes due to a hardware failure. We're working on replacing affected instances.

About 842 days ago - Fri 25 Mar 2016 16:49 (GMT)

More info

Increased publish error rates

Mar 25, 16:43 UTC Identified - We're seeing increased error rates on publishes due to a hardware failure. We're working on replacing affected instances.

About 842 days ago - Fri 25 Mar 2016 16:43 (GMT)

More info

Increased 502 rates for publishes

Mar 24, 19:20 UTC Resolved - We've confirmed that the issue is now fixed, and that publishes work across the board again. Our apologies.Mar 24, 19:00 UTC Monitoring - We've updated configuration on affected servers and are now monitoring the situation further.Mar 24, 18:40 UTC Identified - We've identified the problem to be a configuration file pointing at a server that no longer exists. We're reconfiguring our servers in order to fix the issue.Mar 24, 18:33 UTC Investigating - We're investigating increased rates of 502 responses to publishes from our servers in the US East datacenter.

About 843 days ago - Thu 24 Mar 2016 19:21 (GMT)

More info

Increased 502 rates for publishes

Mar 24, 19:00 UTC Monitoring - We've updated configuration on affected servers and are now monitoring the situation further.Mar 24, 18:40 UTC Identified - We've identified the problem to be a configuration file pointing at a server that no longer exists. We're reconfiguring our servers in order to fix the issue.Mar 24, 18:33 UTC Investigating - We're investigating increased rates of 502 responses to publishes from our servers in the US East datacenter.

About 843 days ago - Thu 24 Mar 2016 19:05 (GMT)

More info

Increased 502 rates for publishes

Mar 24, 18:40 UTC Identified - We've identified the problem to be a configuration file pointing at a server that no longer exists. We're reconfiguring our servers in order to fix the issue.Mar 24, 18:33 UTC Investigating - We're investigating increased rates of 502 responses to publishes from our servers in the US East datacenter.

About 843 days ago - Thu 24 Mar 2016 18:41 (GMT)

More info

Increased 502 rates for publishes

Mar 24, 18:33 UTC Investigating - We're investigating increased rates of 502 responses to publishes from our servers in the US East datacenter.

About 843 days ago - Thu 24 Mar 2016 18:33 (GMT)

More info

increased publish latency

Mar 24, 17:46 UTC Resolved - We've confirmed that the issue is now fixed, and that publishes are back to normal. Our apologies.Mar 24, 17:36 UTC Monitoring - We've fixed the misconfiguration and are now monitoring.publishes.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 843 days ago - Thu 24 Mar 2016 17:47 (GMT)

More info

increased publish latency

Mar 24, 17:36 UTC Monitoring - We've fixed the misconfiguration and are now monitoring.publishes.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 843 days ago - Thu 24 Mar 2016 17:37 (GMT)

More info

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 843 days ago - Thu 24 Mar 2016 17:30 (GMT)

More info