Rewindex

CompaniesnpmIncidents

npm: Issues accessing npm

MajorStatus: resolvedStarted Resolved (41 min)1 updatestatus.npmjs.org (opens in new tab)
Part of an outage event

Cloudflare outage, Dec 16, 2021 · 10 vendors, 10 incidents

npm’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted −4 min vs the first vendor naming Cloudflare)

Swipe sideways to see the whole diagram.

same windowCloudflareown incident not archivedWithin an hour2 vendors, 2 blamed CloudflareHubSpot, Optimizelynpm (this incident)posted −4 min
same windowCloudflareown incident not archivedWithin an hour2 vendors, 2 blamed CloudflareHubSpot, Optimizelynpm (this incident)posted −4 min
npm is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 2 blamed Cloudflare<br/>HubSpot, Optimizely"]:::blames
  root --> h1
  me["npm (this incident)<br/>posted −4 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    This incident has been resolved.

From npm’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on status.npmjs.org (opens in new tab).

npm profileRecent npm incidentsMarkdownJSON