Incident with npm registry and website affecting logins and publishing
At a glance · npm's status
ResolvedLasted 34 min
- First posted
- on npm Status
- Ended
- · marked resolved
- Affects
- 4 services: npm website, npm package installation, npm package publishing +1
- Edited
- Not since we first saw it
- Source
- npm Status · checked 1 min ago
In short
npm reported degraded service affecting 4 Developer tools services, including npm website, npm package installation and npm package publishing, starting 22:31 UTC on 7 Aug 2025. npm marked it resolved at 23:05 UTC after 34 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.
7 Aug 2025
npmFirst public postFrom npm's own incident history, before our archive started.
+14 min
npmMitigated, now monitoring
+34 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 · 4 services
- Status
- resolved
- Services
- npm website, npm package installation, npm package publishing, npm security audit
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 ·
The issue has been identified and a remediation is being put into place.
Investigating ·
We are currently investigating this issue.
Last updated