Outages and root causes.

Two years of public outages, and what each company said caused them. Every entry links to the company's own write-up; nothing here is our speculation.

Status pages re-read 5 min ago

Incidents listed

By month, last two years · Harness

Peak 4 · August 2026

Incidents listed: 8; Last two years
Official write-ups: 8; Linked from the incident
Major outages: 2; As graded by each company
Services: 1; With at least one entry

From the status pages

With a published RCA Partial and major outages Both

Harness · Prod1: IACM Stages are failing and pipelines are intermittently failing to start.
Partial outage · Oct 6, 2026 · 58 min
Read the RCA (opens in a new tab)
Harness · API Login failures
Major outage · Sep 15, 2026 · 21 min
Read the RCA (opens in a new tab)
Harness · MTLS Outage with Delegates
Major outage · Sep 14, 2026 · 8 h 28 min
Read the RCA (opens in a new tab)
Harness · Feature Management & Experimentation (FME) user interface unavailable
Partial outage · Aug 24, 2026 · 16 min
Read the RCA (opens in a new tab)
Harness · All modules are running slow in Prod1/2/3/4 due to cloud provider incident
Partial outage · Aug 20, 2026 · 2 h 7 min
Read the RCA (opens in a new tab)
Harness · Data ingestion is delayed on Traceable US production
Partial outage · Aug 19, 2026 · 2 h 44 min
Read the RCA (opens in a new tab)
Harness · SEI 2.0 dashboards are not loading
Partial outage · Aug 6, 2026 · 1 h 31 min
Read the RCA (opens in a new tab)
Harness · The Prod3 & Prod1 environment is experiencing intermittent outages. We are currently investigating the issue.
Partial outage · Jul 27, 2026 · 6 h 51 min
Read the RCA (opens in a new tab)

Who publishes root causes

Write-ups posted on status pages, last two years

Public information only

Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.

Sources

Official status pages: incident titles, severity, times and the link to each published root-cause analysis, exactly as each company posted them
Company engineering blogs and incident reports: the basis for the notable-outage summaries, each linked from its card

How fresh it is

Incidents and RCA links: re-read from every status page about once an hour; last run 5 min ago
Notable-outage summaries: written by hand and last checked against their sources on Nov 10, 2026

Titles, severity and times are as published on each company's status page. "Published RCA" means the company posted a postmortem on that incident's official page; we link to it and do not reproduce it. Many companies publish root causes on a blog instead, or not at all, so the absence of a link is not evidence that no analysis exists. Severity grading differs between companies and is not comparable across them. This is not a complete record of every outage.

statuswall is independent and is not affiliated with, sponsored by or endorsed by any company named here. Company and product names are used only to identify whose public information is being referred to. The information is provided as is, for general reference, with no guarantee that it is complete, current or free of error; it is not security, legal or purchasing advice. Where this page and an official source differ, the official source is right.