Rewindex

CompaniesSemaphoreIncidents

Semaphore: Delays in job processing on Semaphore 2.0 for a1-standard-4 machines, Xcode 12

MinorStatus: resolvedStarted Resolved (50 min)1 updatestatus.semaphore.io (opens in new tab)
Part of an outage event

Auth0 outage, Apr 20, 2021 · 12 vendors, 12 incidents

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

Swipe sideways to see the whole diagram.

same windowAuth0own incident not archivedWithin an hour3 vendors, 3 blamed Auth0Wiz, Logz.io, Firebolt1 to 4 hours later1 vendor, 1 blamed Auth0LeverSemaphore (this incident)posted +9 min
same windowAuth0own incident not archivedWithin an hour3 vendors, 3 blamed Auth0Wiz, Logz.io, Firebolt1 to 4 hours later1 vendor, 1 blamed Auth0LeverSemaphore (this incident)posted +9 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["Auth0<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 3 blamed Auth0<br/>Wiz, Logz.io, Firebolt"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Auth0<br/>Lever"]:::blames
  root --> h4
  me["Semaphore (this incident)<br/>posted +9 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