npm Status · History · Incident #142
RESOLVEDIssue with npm website and login.
Major · Started Mar 25, 2026 · 10:39 PM
$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 #142
RESOLVEDMajor · Started Mar 25, 2026 · 10:39 PM
Duration
46m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Mar 25, 2026 · 10:39 PM
Resolved
Mar 25, 2026 · 11:26 PM
Duration
46m
Severity
Major
Event timeline
Investigating
Mar 25 · 10:39 PM npmWe are currently investigating this issue.
Monitoring
Mar 25 · 11:10 PM npmA fix has been implemented and we are monitoring the results.
Resolved
Mar 25 · 11:26 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