CloudStatus

Npmjs Status Updates

increased origin latency resulting in burst of 503s

Jan 13, 23:03 UTC Resolved - briefly, between (2:54 - 2:58PM PDT ) we saw a increase in origin latency, resulting in increased 503s from the registry; the problem has been resolved and we are investigating the underlying cause.

About 548 days ago - Fri 13 Jan 2017 23:03 (GMT)

Source: Npmjs - npm

Npmjs History

website not responding

Jan 5, 05:23 UTC Resolved - All services back to normal.Jan 5, 04:51 UTC Monitoring - We have successfully failed over to our secondary & removed the temporary workaround.Jan 5, 04:32 UTC Identified - We indeed lost a database primary host. We are failing over to the secondary now. In the meantime, we've deployed a workaround that restores website functionality, albeit with no billing data. The website will temporarily report placeholder billing data; this workaround will be backed out shortly.Jan 5, 04:24 UTC Investigating - Our website is not responding to requests right now. An instance providing a backing service has gone down. We are in the process of restarting and/or replacing the downed host.

About 557 days ago - Thu 5 Jan 2017 05:24 (GMT)

More info

website not responding

Jan 5, 04:51 UTC Monitoring - We have successfully failed over to our secondary & removed the temporary workaround.Jan 5, 04:32 UTC Identified - We indeed lost a database primary host. We are failing over to the secondary now. In the meantime, we've deployed a workaround that restores website functionality, albeit with no billing data. The website will temporarily report placeholder billing data; this workaround will be backed out shortly.Jan 5, 04:24 UTC Investigating - Our website is not responding to requests right now. An instance providing a backing service has gone down. We are in the process of restarting and/or replacing the downed host.

About 557 days ago - Thu 5 Jan 2017 04:52 (GMT)

More info

website not responding

Jan 5, 04:32 UTC Identified - We indeed lost a database primary host. We are failing over to the secondary now. In the meantime, we've deployed a workaround that restores website functionality, albeit with no billing data. The website will temporarily report placeholder billing data; this workaround will be backed out shortly.Jan 5, 04:24 UTC Investigating - Our website is not responding to requests right now. An instance providing a backing service has gone down. We are in the process of restarting and/or replacing the downed host.

About 557 days ago - Thu 5 Jan 2017 04:33 (GMT)

More info

website not responding

Jan 5, 04:24 UTC Investigating - Our website is not responding to requests right now. An instance providing a backing service has gone down. We are in the process of restarting and/or replacing the downed host.

About 557 days ago - Thu 5 Jan 2017 04:25 (GMT)

More info

Website unavailable

Dec 25, 14:13 UTC Resolved - Website is back up and we're working on resolving the root cause of the issue.Dec 25, 14:03 UTC Monitoring - We've restored Redis service and are monitoring website health.Dec 25, 13:42 UTC Investigating - We are investigating website unavailability caused by a failure of one of our Redis services.

About 567 days ago - Sun 25 Dec 2016 14:14 (GMT)

More info

Website unavailable

Dec 25, 14:03 UTC Monitoring - We've restored Redis service and are monitoring website health.Dec 25, 13:42 UTC Investigating - We are investigating website unavailability caused by a failure of one of our Redis services.

About 567 days ago - Sun 25 Dec 2016 14:04 (GMT)

More info

Website unavailable

Dec 25, 13:42 UTC Investigating - We are investigating website unavailability caused by a failure of one of our Redis services.

About 567 days ago - Sun 25 Dec 2016 13:43 (GMT)

More info

Downloads API unavailability

Nov 22, 11:12 UTC Resolved - Downloads API is now back online. The unavailability was caused by an outdated SSL certificate being deployed to the machine handling api.npmjs.org traffic, which, due to a misconfiguration, our monitoring did not catch in time.Nov 22, 10:38 UTC Investigating - We are investigating unavailability of the downloads API (api.npmjs.org).

About 601 days ago - Tue 22 Nov 2016 11:14 (GMT)

More info

Downloads API unavailability

Nov 22, 10:38 UTC Investigating - We are investigating unavailability of the downloads API (api.npmjs.org).

About 601 days ago - Tue 22 Nov 2016 10:39 (GMT)

More info

increased incidence of 404s for recently-published packages

Nov 17, 23:39 UTC Resolved - We believe everything is back to normal.Nov 17, 21:27 UTC Monitoring - The configuration fix seems to have addressed the problem with some tarballs 404ing shortly after publication. Continuing to monitor.Nov 17, 18:29 UTC Investigating - We're looking into reports of recent publications 404ing after seeming to work initially. A misconfiguration has been identified & is being corrected, but we are investigating further.

About 605 days ago - Thu 17 Nov 2016 23:40 (GMT)

More info