npm Outage History

24 incidents recorded over the last 365 days, 24 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live npm status99.43% uptime history

Every Recorded npm Incident

npm incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jul 30, 2026intermittent Publish FailuresThis incident has been resolved.4h 23mResolved
Jul 24, 2026Publish and Install failuresThis incident has been resolved.30 minResolved
Jul 23, 2026intermittent Publish and Install FailuresThis incident has been resolved.3h 42mResolved
Jun 12, 2026intermittent Publish FailuresThis incident has been resolved.48 minResolved
Apr 29, 2026npm website issuesThis incident has been resolved.42 minResolved
Apr 29, 2026Degraded Performance in View Package and Login on npmjs.comThis incident has been resolved.2h 47mResolved
Apr 28, 2026npm website degraded serviceThis incident has been resolved.2h 29mResolved
Apr 27, 2026npm Website is unavailableThis incident has been resolved.1h 24mResolved
Apr 1, 2026Increased errors in viewing packages and authentication on npmjs.comThis incident has been resolved.3h 6mResolved
Mar 31, 2026Degraded Performance in View Package and Login on npmjs.comThis incident has been resolved.2h 36mResolved
Mar 30, 2026delay and errors viewing packages and submitting web based authenticationThis incident has been resolved.2h 36mResolved
Mar 30, 2026delay and errors viewing packages and submitting web based authenticationThis incident has been resolved.1h 4mResolved
Mar 25, 2026Issue with npm website and login.This incident has been resolved.46 minResolved
Mar 5, 2026Degraded performance for package publishThis incident has been resolved.5h 54mResolved
Feb 25, 2026Degraded performance with package installationThis incident has been resolved.1h 20mResolved
Feb 17, 2026npm publishing impactedThis incident has been resolved.2h 27mResolved
Jan 29, 2026Degraded Experience Installing and Viewing PackagesThis incident has been resolved.45 minResolved
Dec 5, 2025Issue connecting to website and registryThis incident has been resolved.39 minResolved
Nov 18, 2025npmjs.com - Service DisruptionWe have confirmed that all systems are now fully operational and the connectivity issues have been completely resolved.5h 36mResolved
Nov 6, 2025Issue with npm website and loginThis incident has been resolved.32 minResolved
Oct 20, 2025Issue with package publishingThis incident has been resolved.2h 55mResolved
Oct 20, 2025Degraded performance of package publish and installThis incident has been resolved.4h 0mResolved
Oct 3, 2025Degraded performance on npmjs.comThis incident has been resolved.7h 34mResolved
Aug 26, 2025Degraded Package Install ExperienceThis incident has been resolved.3h 9mResolved

How to Read This npm Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before npm acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single npm outage in this window ran 7h 34m, against a mean recovery of 2h 34m. If you depend on npm in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.