Rewindex

CompaniesHarnessIncidents

Harness: Harness Impacted due to ongoing Cloudflare Incident

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

Cloudflare outage, Jun 21, 2022 · 30 vendors, 30 incidents

Harness’s incident blames Cloudflare as the cause. (hop 1, posted +37 min vs the first vendor naming Cloudflare)

“…Harness Impacted due to ongoing Cloudflare Incident We can confirm normal operation. Get Ship Done! We will continue to monitor and ensure stability.…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour5 vendors, 5 blamed CloudflareDoppler, LiveKit, Lattice, Mattermost +1Harness (this incident)posted +37 min
Cloudflareown incident not archivedWithin an hour5 vendors, 5 blamed CloudflareDoppler, LiveKit, Lattice,Mattermost +1Harness (this incident)posted +37 min
Harness 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/>5 vendors, 5 blamed Cloudflare<br/>Doppler, LiveKit, Lattice, Mattermost +1"]:::blames
  root --> h1
  me["Harness (this incident)<br/>posted +37 min"]:::me
  h1 --- 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

    We can confirm normal operation. Get Ship Done! We will continue to monitor and ensure stability.

From Harness’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.harness.io (opens in new tab).

Harness profileRecent Harness incidentsMarkdownJSON