npm Status · History · Incident #122
RESOLVEDIncreased errors in viewing packages and authentication on npmjs.com
Minor · Started Apr 1, 2026 · 10:05 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
npm Status · History · Incident #122
RESOLVEDMinor · Started Apr 1, 2026 · 10:05 AM
Duration
3h 6m
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Apr 1, 2026 · 10:05 AM
Resolved
Apr 1, 2026 · 1:12 PM
Duration
3h 6m
Severity
None
Event timeline
Investigating
Apr 1 · 10:05 AM npmWe are observing increased errors in viewing packages and authentication on npmjs website. We are investigating this issue.
Monitoring
Apr 1 · 12:20 PM npmA fix has been implemented and we are monitoring the results.
Resolved
Apr 1 · 1:12 PM npmThis incident has been resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT