npm Status · History · Incident #151
RESOLVEDDegraded performance for package publish
Minor · Started Mar 5, 2026 · 11:41 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 #151
RESOLVEDMinor · Started Mar 5, 2026 · 11:41 AM
Duration
5h 54m
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Mar 5, 2026 · 11:41 AM
Resolved
Mar 5, 2026 · 5:35 PM
Duration
5h 54m
Severity
Minor
Event timeline
Investigating
Mar 5 · 11:41 AM npmWe are currently investigating this issue.
Monitoring
Mar 5 · 1:01 PM npmA fix has been implemented and we are monitoring the results.
Resolved
Mar 5 · 5:35 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