CloudStatus

Npmjs Status Updates

increased rate of 503s in eu

Mar 28, 14:52 UTC Resolved - This incident has been resolved.Mar 28, 14:40 UTC Monitoring - orignal configuration has been restored we are keeping an eye on things.Mar 28, 14:02 UTC Identified - A networking issue caused many authentication requests to our eu servers timeout. We redirected this traffic to us_east for the time being and error rates have dropped.Mar 28, 13:50 UTC Investigating - We are currently investigating this issue.

About 299 days ago - Tue 28 Mar 2017 14:52 (GMT)

Source: Npmjs - npm

Npmjs History

replication lag on publications

Mar 25, 03:31 UTC Resolved - Everything looks clear.Mar 24, 23:17 UTC Monitoring - The bug that was causing too many couchdb document updates has been fixed, and changes should now be flowing through the system at a normal rate again. We're monitoring to make sure the backlog drains as expected.Mar 24, 21:18 UTC Identified - We've identified the root cause of the replication delays. Publications have been accepted & stored, but replication on our CouchDB instances is behind because of unexpected load caused by a bug elsewhere that creates many document updates when certain package data is changed. We're working on a fix.Mar 24, 20:28 UTC Investigating - We are investigating lag on replicating publications to our leaf nodes as well as downstream to registry mirrors.

About 293 days ago - Mon 3 Apr 2017 22:42 (GMT)

More info

Delayed Package Publishes

Mar 17, 16:33 UTC Resolved - We've resolved the problem that was causing delayed package publishes. All previous and current new package publishes should now work as expected.Mar 17, 15:32 UTC Monitoring - A fix has been implemented for the delayed package publishes and we are monitoring the results.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 16:34 (GMT)

More info

Delayed Package Publishes

Mar 17, 15:32 UTC Monitoring - A fix has been implemented for the delayed package publishes and we are monitoring the results.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:32 (GMT)

More info

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:22 (GMT)

More info

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