Rewindex

CompaniesSemaphoreIncidents

Semaphore: Builds are not starting

MajorStatus: resolvedStarted Resolved (3.8 h)1 updatestatus.semaphore.io (opens in new tab)
Part of an outage event

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

Semaphore’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +28 min vs the first vendor naming Google Cloud)

Swipe sideways to see the whole diagram.

same windowGoogle Cloudown incident not archivedWithin an hour1 vendor, 1 blamed Google CloudPendo1 to 4 hours later2 vendors, 2 blamed Google Cloudnpm, ConfluentSemaphore (this incident)posted +28 min
same windowGoogle Cloudown incident not archivedWithin an hour1 vendor, 1 blamed GoogleCloudPendo1 to 4 hours later2 vendors, 2 blamed GoogleCloudnpm, ConfluentSemaphore (this incident)posted +28 min
Semaphore 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["Semaphore (this incident)<br/>posted +28 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 Semaphore’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.semaphore.io (opens in new tab).

Semaphore profileRecent Semaphore incidentsMarkdownJSON