Issues with npm package publish and private install
At a glance · npm's status
ResolvedLasted 5 h 57 min
- First posted
- on npm Status
- Ended
- · marked resolved
- Affects
- npm package installation, npm package publishing, npm replication feed
- Edited
- Not since we first saw it
- Source
- npm Status · checked 1 min ago
In short
npm reported degraded service affecting npm package installation, npm package publishing and npm replication feed, starting 00:50 UTC on 27 Sep. npm marked it resolved at 06:47 UTC after 5 h 57 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.
27 Sep
npmFirst public postFrom npm's own incident history, before our archive started.
+39 min
npmMitigated, now monitoring
+5 h 57 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 · 3 services
- Status
- resolved
- Services
- npm package installation, npm package publishing, npm replication feed
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