Degraded Performance in View Package and Login on npmjs.com
At a glance · npm's status
ResolvedLasted 2 h 36 min
- First posted
- on npm Status
- Ended
- · marked resolved
- Affects
- npm website
- Edited
- Not since we first saw it
- Source
- npm Status · checked 1 min ago
In short
npm reported degraded service affecting npm website, starting 19:12 UTC on 31 Mar. npm marked it resolved at 21:49 UTC after 2 h 36 min.
npm says
npm's latest update, , in short excerpts.
This incident has been resolved.
Timeline
Times in UTC, npm's own where it gives them.
31 Mar
npmFirst public postFrom npm's own incident history, before our archive started.
+2 h
npmMitigated, now monitoring
+2 h 37 min
npmResolved
What npm changed
npm adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on npm's page.
One version so far. If npm edits it, each change shows here with what was removed and added.
First version we captured ·
As first seen: resolved · 1 service
- Status
- resolved
- Services
- npm website
Seen by us · npm's timestamp · npm's page
Affected services
Official updates
Posted by npm Status, newest first. The newest are quoted in their first sentence; the full text of each is on npm's page.
Resolved ·
This incident has been resolved.
Monitoring ·
A fix has been implemented and we are monitoring the results.
Investigating ·
We have implemented initial fixes and are continuing to investigate this issue
Investigating ·
We are seeing degraded performance in package viewing and authentication on npmjs website.
Last updated