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 just now

Incidents listed

By month, last two years · Honeycomb

Peak 3 · April 2026

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

Notable outages, summarised

Read from each company's published analysis and summarised in our own words. Follow the link for the full account.

Honeycomb
Jun 24, 2026
Ingest outage in US and EU
Event ingestion returned errors for roughly 20 to 30 minutes, mainly in the US region, and alerting and service-map features were disrupted for that window.
Root cause, as stated by Honeycomb
A deployment changed how dataset schemas were cached in a backward-incompatible way, so cache reads failed and all lookups stampeded the database.
Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)

From the status pages

With a published RCA Partial and major outages Both

Honeycomb · Email notifications for SLOs, Triggers, and Anomaly Detection not sending
Partial outage · Oct 22, 2026 · 1 h 1 min
Incident report (opens in a new tab)
Honeycomb · Degraded event ingest
Partial outage · Oct 20, 2026
Incident report (opens in a new tab)
Honeycomb · Slowness in US region
Partial outage · Oct 20, 2026 · 2 h 21 min
Read the RCA (opens in a new tab)
Honeycomb · Querying issues
Degraded · Jul 31, 2026
Read the RCA (opens in a new tab)
Honeycomb · honeycomb.io marketing website not working
Partial outage · Jul 2, 2026 · 6 h 21 min
Incident report (opens in a new tab)
Honeycomb · Ingest Outage in US and EU
Partial outage · Jun 24, 2026 · 51 min
Read the RCA (opens in a new tab)
Honeycomb · Enhance Issues
Partial outage · Jun 18, 2026
Incident report (opens in a new tab)
Honeycomb · Query interuption due to database failover in the EU region
Partial outage · May 1, 2026
Incident report (opens in a new tab)
Honeycomb · Activity Log events interrupted for EU
Partial outage · Apr 20, 2026 · 7 min
Incident report (opens in a new tab)
Honeycomb · Ingest issues for some customers
Partial outage · Apr 10, 2026 · 3 h 42 min
Incident report (opens in a new tab)
Honeycomb · Partial Querying Outage
Partial outage · Apr 9, 2026
Incident report (opens in a new tab)
Honeycomb · Honeycomb UI displaying an error
Major outage · Mar 18, 2026 · 11 min
Incident report (opens in a new tab)
Honeycomb · Increased Latency and Errors for Events Ingest
Partial outage · Jan 15, 2026
Incident report (opens in a new tab)
Honeycomb · Querying and Ingest issues in EU
Partial outage · Dec 5, 2025 · 11 d 18 h
Read the RCA (opens in a new tab)
Honeycomb · Delays in SLO, Service Maps processing
Partial outage · Oct 20, 2025 · 1 d 1 h
Incident report (opens in a new tab)
Honeycomb · Investigating Querying Issues
Partial outage · Oct 20, 2025 · 2 h 40 min
Read the RCA (opens in a new tab)
Honeycomb · Delayed ingestion of events in EU region
Partial outage · Aug 13, 2025
Incident report (opens in a new tab)
Honeycomb · Ingestion delays in EU
Partial outage · Aug 12, 2025 · 20 min
Incident report (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 just now
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.