CloudStatus

Npmjs Status Updates

Delayed Package Publishes

Mar 17, 15:21 UTC Identified - We are currently investigating an issue where newly published package versions are delayed and therefore are inaccessible for installation. They appear updated on the website and the CLI does not throw an error on publish, yet an `npm install` of the newly published package version may fail. We've identified the source of the issue and are actively fixing the issue.

About 310 days ago - Fri 17 Mar 2017 15:21 (GMT)

Source: Npmjs - npm

Npmjs History

increased rate of 503s.

Mar 15, 16:27 UTC Resolved - An increased request rate caused by bot behavior caused slower than usual response times and increased error rates. Lasted from 15:00 - 15:45

About 312 days ago - Wed 15 Mar 2017 16:28 (GMT)

More info

www search 503

Feb 16, 16:00 UTC Resolved - we found some invalid search queries causing increased load on our search cluster. we are adding additional filtering and should be out of the woods.Feb 16, 15:20 UTC Monitoring - we've drained a backlog of failing requests on our search cluster. serch seems to be working again. we are monitoring.Feb 16, 14:35 UTC Investigating - we are investigating an increased rate of 503s returned from website search.

About 339 days ago - Thu 16 Feb 2017 16:00 (GMT)

More info

www search 503

Feb 16, 15:20 UTC Monitoring - we've drained a backlog of failing requests on our search cluster. serch seems to be working again. we are monitoring.Feb 16, 14:35 UTC Investigating - we are investigating an increased rate of 503s returned from website search.

About 339 days ago - Thu 16 Feb 2017 15:20 (GMT)

More info

www search 503

Feb 16, 14:35 UTC Investigating - we are investigating an increased rate of 503s returned from website search.

About 339 days ago - Thu 16 Feb 2017 14:35 (GMT)

More info

some readmes are unavailable on npmjs.com

Jan 26, 16:50 UTC Resolved - README rendering of new package publications was lagging behind, due to a production database running out of space. We have corrected this issue, and will be adding monitoring to prevent similar issues in the future. The database that ran out of space stored only README information, which has now caught up. No data was lost.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 360 days ago - Thu 26 Jan 2017 16:51 (GMT)

More info

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 360 days ago - Thu 26 Jan 2017 13:35 (GMT)

More info

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 360 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 361 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 373 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 381 days ago - Thu 5 Jan 2017 05:24 (GMT)

More info