CloudStatus

Npmjs Status Updates

some readmes are unavailable on npmjs.com

Jan 26, 13:34 UTC Monitoring - the service is back up and running and we are monitoringJan 26, 13:09 UTC Investigating - we are looking into an issue serving readmes on the website.

About 605 days ago - Thu 26 Jan 2017 13:34 (GMT)

Source: Npmjs - npm

Npmjs History

some readmes are unavailable on npmjs.com

Jan 26, 13:09 UTC Investigating - we are looking into an issue serving readmes on the website.

About 605 days ago - Thu 26 Jan 2017 13:10 (GMT)

More info

Increased 503 rates for users in Los Angeles region

Jan 25, 13:44 UTC Resolved - Our monitoring indicated increased 503 rates originating from our CDN provider's LAX Point of Presence, starting at ~13:03 UTC up to ~13:40 UTC .

About 606 days ago - Wed 25 Jan 2017 13:45 (GMT)

More info

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 617 days ago - Fri 13 Jan 2017 23:04 (GMT)

More info

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 626 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 626 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 626 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 626 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 637 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 637 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 637 days ago - Sun 25 Dec 2016 13:43 (GMT)

More info