We started checking Upstash on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Upstash reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Upstash's own status page declared. Below it, any public chatter we saw about Upstash and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Upstash's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Upstash in the last 24 hours, which is not evidence that nothing is wrong.
Upstash's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Upstash's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Upstash next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
430
US-West
99.70%
329
Europe
100.00%
300
Asia-Pacific
100.00%
182
Their declared record
Upstash's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Brief connection proxy degradation in us-east-1Minor incident
Sep 29, 2026, 3:12 PM UTC to Sep 29, 2026, 3:12 PM UTC (0 min)resolved
their latest update (Sep 29, 2026, 3:12 PM UTC): Between 15:12 and 15:16 UTC, we observed a brief increase in load on the connection proxy layer in us-east-1, which may have affected some existing and new connections.
The team responded quickly and resolved the issue. All systems are now fully operational.
Intermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1)Minor incident
Sep 9, 2026, 12:00 PM UTC to Sep 9, 2026, 12:00 PM UTC (0 min)resolved
their latest update (Sep 9, 2026, 12:00 PM UTC): Upstash Vector experienced a brief DNS resolution issue in the US East (us-east-1) region lasting approximately 20 minutes. During this period, new DNS resolution attempts may have failed.
Existing connections and clients with cached DNS records were not affected.
The issue has…
Upstash Console login issueAll systems operational
Sep 3, 2026, 8:00 AM UTC to Sep 3, 2026, 8:00 AM UTC (0 min)resolved
their latest update (Sep 3, 2026, 8:00 AM UTC): We experienced a brief issue affecting access to the Upstash Console. Our team quickly identified the cause and resolved the issue within minutes.
The console is now operating normally.
Aug 28, 2026, 10:20 PM UTC to Aug 28, 2026, 10:20 PM UTC (0 min)resolved
their latest update (Aug 28, 2026, 10:20 PM UTC): Between 22:20 and 22:33 UTC, QStash clients in us-east-1 experienced disruptions related to message persistence. The team applied a fix, and service has been restored.
Fly.io infrastructure disruption affecting some Upstash Redis databases on Fly.io DFW RegionAll systems operational
Jul 22, 2026, 8:50 AM UTC to Jul 22, 2026, 10:05 AM UTC (1h 15m)resolved
their latest update (Jul 22, 2026, 10:05 AM UTC): This incident has been resolved.
QStash us-east-1 - URL Publish ErrorsAll systems operational
Jul 16, 2026, 6:30 AM UTC to Jul 16, 2026, 6:30 AM UTC (0 min)resolved
their latest update (Jul 16, 2026, 6:30 AM UTC): Partial outage due to http parsing errors. Problem was resolved couple minutes later. If problem continues, refreshing the DNS cache is recommended.
Upstash Redis Partial Service DisruptionPartial outage
Jun 25, 2026, 3:23 PM UTC to Jun 25, 2026, 4:36 PM UTC (1h 12m)resolved
their latest update (Jun 25, 2026, 4:36 PM UTC): This incident has been resolved, we will publish RCA soon.
QStash EU Region — Degraded PerformanceMinor incident
Jun 23, 2026, 4:22 PM UTC to Jun 23, 2026, 5:14 PM UTC (52 min)postmortem published
their latest update (Jun 24, 2026, 12:28 PM UTC): ### **Summary**
On June 23, 2026, QStash users in the EU-CENTRAL-1 region experienced elevated latency and degraded performance. The issue was caused by a regression introduced in a recent enhancement to Flow Control scheduling logic. The change increased resource consumption un…
Box Access and Management Operations UnavailableAll systems operational
Jun 23, 2026, 6:05 AM UTC to Jun 23, 2026, 6:05 AM UTC (0 min)resolved
their latest update (Jun 23, 2026, 6:05 AM UTC): Between 01:18 and 04:03 UTC, customers were unable to access running boxes or perform create, read, update, or delete operations. Running containers were not affected and continued operating throughout. The issue has been fully resolved and all box operations are functioning norm…
QStash Service Disruption in the EU RegionPartial outage
Jun 19, 2026, 9:11 AM UTC to Jun 19, 2026, 9:11 AM UTC (0 min)postmortem published
their latest update (Jun 19, 2026, 1:52 PM UTC): ## What happened
A configuration change applied to QStash's EU networking layer introduced an outbound connectivity fault. Between **09:11 and 09:45 UTC**, a subset of QStash instances had degraded egress connectivity, and some dispatched messages may have failed on their initia…
Showing the 10 most recent of 50 incidents Upstash has declared in the history we hold.
These entries are Upstash's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Upstash's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.