Thursday, 20 September, 2018 UTC
Summary
Sep 20, 00:56 UTC
Resolved - The APIs remain stable and all systems are back to normal. We're resolving this incident.
Resolved - The APIs remain stable and all systems are back to normal. We're resolving this incident.
Sep 20, 00:21 UTC
Monitoring - We have identified a configuration error responsible for the overload and rectified it. Package pages and scoped package reads appear to be back to normal. We are closely monitoring the situation.
Monitoring - We have identified a configuration error responsible for the overload and rectified it. Package pages and scoped package reads appear to be back to normal. We are closely monitoring the situation.
Sep 20, 00:05 UTC
Update - We have partially restored the website, so you can read package READMEs again, and access to scoped packages is slow but restored. We are working on a more permanent solution.
Update - We have partially restored the website, so you can read package READMEs again, and access to scoped packages is slow but restored. We are working on a more permanent solution.
Sep 19, 23:39 UTC
Update - Our API that checks for whether a package is private or not is overloaded; this is leading to scoped packages being unavailable. No data has been lost and we are working on restoring the API. We apologize for the inconvenience.
Update - Our API that checks for whether a package is private or not is overloaded; this is leading to scoped packages being unavailable. No data has been lost and we are working on restoring the API. We apologize for the inconvenience.
Sep 19, 23:17 UTC
Update - Website package pages are also affected.
Update - Website package pages are also affected.
Sep 19, 22:40 UTC
Identified - The registry is experiencing a partial outage for scoped package reads: users will see intermittent timeouts and 503 responses. We are working on a fix.
Identified - The registry is experiencing a partial outage for scoped package reads: users will see intermittent timeouts and 503 responses. We are working on a fix.