npm Status · History · Incident #118
RESOLVEDnpm Website is unavailable
Critical · Started Apr 27, 2026 · 9:06 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 #118
RESOLVEDCritical · Started Apr 27, 2026 · 9:06 PM
Duration
1h 24m
Severity
Critical
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Apr 27, 2026 · 9:06 PM
Resolved
Apr 27, 2026 · 10:30 PM
Duration
1h 24m
Severity
Critical
Event timeline
Investigating
Apr 27 · 9:06 PM npmWe are currently investigating this issue.
Investigating
Apr 27 · 10:28 PM npmWe are continuing to investigate this issue.
Resolved
Apr 27 · 10:30 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