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 13 min ago

Incidents listed

By month, last two years · Upstash

Peak 4 · May 2026

Incidents listed: 16; Last two years
Official write-ups: 7; Linked from the incident
Major outages: 6; 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.

Upstash
May 12, 2026
Redis instances on Fly.io hanging intermittently
A subset of Upstash Redis instances hosted on Fly.io hung intermittently and returned elevated errors on 12 and 13 May; no data was lost.
Root cause, as stated by Upstash
A recent guest kernel update on the host platform interacted badly with a hypervisor bug affecting log writes, stalling the Redis process.
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

Upstash · Message Persistence Issue — QStash us-east-1
Partial outage · Aug 28, 2026
Incident report (opens in a new tab)
Upstash · Upstash Redis Partial Service Disruption
Partial outage · Jun 25, 2026 · 1 h 12 min
Incident report (opens in a new tab)
Upstash · QStash Service Disruption in the EU Region
Partial outage · Jun 19, 2026
Read the RCA (opens in a new tab)
Upstash · Upstash Redis – intermittent connection issues in some regions
Partial outage · May 14, 2026 · 1 h 44 min
Incident report (opens in a new tab)
Upstash · Fly.io Upstash Redis Service Distruption
Major outage · May 12, 2026 · 3 h 59 min
Read the RCA (opens in a new tab)
Upstash · Fly.io Upstash Redis service distruption (FRA region)
Partial outage · May 11, 2026 · 3 h 17 min
Read the RCA (opens in a new tab)
Upstash · QStash US Region Service Disruption
Major outage · May 8, 2026 · 22 min
Read the RCA (opens in a new tab)
Upstash · Region ap-northeast-1 outage on Upstash Global
Major outage · Mar 6, 2026 · 1 h 0 min
Read the RCA (opens in a new tab)
Upstash · Connectivity issue impacting Regional Databases in US-East-1
Partial outage · Dec 10, 2025 · 18 min
Incident report (opens in a new tab)
Upstash · Upstash Console and Context7 Console is Currently Experiencing issues
Major outage · Dec 5, 2025 · 15 min
Incident report (opens in a new tab)
Upstash · Upstash Console issues
Partial outage · Oct 20, 2025 · 3 h 59 min
Incident report (opens in a new tab)
Upstash · Login Issues on Upstash Console
Major outage · Oct 20, 2025
Incident report (opens in a new tab)
Upstash · Login problems on Upstash Console
Partial outage · Jun 26, 2025 · 42 min
Incident report (opens in a new tab)
Upstash · Degraded Performance
Major outage · Jun 11, 2025 · 3 h 11 min
Read the RCA (opens in a new tab)
Upstash · Disk failure in some Regional Databases
Partial outage · Jan 29, 2025
Incident report (opens in a new tab)
Upstash · Performance degradation on QStash
Partial outage · Nov 13, 2024 · 3 h 13 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 13 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.