npm publishing impacted
At a glance · npm's status
ResolvedLasted 2 h 27 min
- First posted
- on npm Status
- Ended
- · marked resolved
- Affects
- npm package publishing
- Edited
- Not since we first saw it
- Source
- npm Status · checked 1 min ago
In short
npm reported degraded service affecting npm package publishing, starting 20:01 UTC on 17 Feb. npm marked it resolved at 22:28 UTC after 2 h 27 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.
17 Feb
npmFirst public postFrom npm's own incident history, before our archive started.
+1 h 16 min
npmMitigated, now monitoring
+2 h 27 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 package publishing
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 are currently investigating this issue.
Last updated