Issues publishing and installing packages
At a glance · npm's status
ResolvedLasted 12 h 4 min
- First posted
- on npm Status
- Ended
- · marked resolved
- Affects
- npm package installation, 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 installation and npm package publishing, starting 02:46 UTC on 11 Apr 2025. npm marked it resolved at 14:51 UTC after 12 h 4 min.
npm says
npm's latest update, , in short excerpts.
This incident was caused due to an internal bug during regular database maintenance, its resolved now.
Timeline
Times in UTC, npm's own where it gives them.
11 Apr 2025
npmFirst public postFrom npm's own incident history, before our archive started.
+10 h 6 min
npmMitigated, now monitoring
+12 h 5 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 · 2 services
- Status
- resolved
- Services
- npm package installation, 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 was caused due to an internal bug during regular database maintenance, its resolved now.
Monitoring ·
We are monitoring results
Identified ·
We are continuing to work on a fix to restore older access tokens.
Identified ·
The issue has been identified and a fix is being implemented.
Investigating ·
We are investigating issues with access tokens, in the meantime user can recreate new tokens to unblock themselves.
Last updated