Rewindex

CompaniesnpmIncidents

npm: npm Enterprise partial outage due to Google Compute Engine

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

Google Cloud outage, Jun 2, 2019 · 8 vendors, 8 incidents

npm’s incident blames Google Cloud as the cause. (hop 1, posted +1 h 4 min vs the first vendor naming Google Cloud)

“…npm Enterprise partial outage due to Google Compute Engine This incident has been resolved.…”

Swipe sideways to see the whole diagram.

Google Cloudown incident not archivedWithin an hour1 vendor, 1 blamed Google CloudPendo1 to 4 hours later2 vendors, 2 blamed Google Cloudnpm, Confluentnpm (this incident)posted +1 h 4 min
Google Cloudown incident not archivedWithin an hour1 vendor, 1 blamed GoogleCloudPendo1 to 4 hours later2 vendors, 2 blamed GoogleCloudnpm, Confluentnpm (this incident)posted +1 h 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["Google Cloud<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>1 vendor, 1 blamed Google Cloud<br/>Pendo"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 2 blamed Google Cloud<br/>npm, Confluent"]:::blames
  root --> h4
  me["npm (this incident)<br/>posted +1 h 4 min"]:::me
  h4 --- 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