Vendor Status Watch

← all vendors

Upstash status history

Current state: operational — “All Systems Operational” per https://status.upstash.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

3incidents, last 30 days
9incidents, last 90 days
29incidents on record
Incidents per week, last 12 weeks:

How long do Upstash incidents last?

17 minmedian incident duration29 measured
4.0 h90th percentile1 in 10 ran longer
40 minmedian, major/critical only12 incidents

From 29 incidents with a vendor-posted start and resolve time. Longest on record: QStash US Region: Schedule Degradation — 17.7 h (2026-05-05 14:24 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (29)

StartedIncidentStatusImpactDuration
2026-09-09 12:00 UTCIntermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1)resolvedminor0 min
2026-09-03 08:00 UTCUpstash Console login issueresolvednone0 min
2026-08-28 22:20 UTCMessage Persistence Issue — QStash us-east-1resolvedmajor0 min
2026-07-22 08:50 UTCFly.io infrastructure disruption affecting some Upstash Redis databases on Fly.io DFW Regionresolvednone1 h 15 min
2026-07-16 06:30 UTCQStash us-east-1 - URL Publish Errorsresolvednone0 min
2026-06-25 15:23 UTCUpstash Redis Partial Service Disruptionresolvedmajor1 h 12 min
2026-06-23 16:22 UTCQStash EU Region — Degraded Performancepostmortemminor52 min
2026-06-23 06:05 UTCBox Access and Management Operations Unavailableresolvednone0 min
2026-06-19 09:11 UTCQStash Service Disruption in the EU Regionpostmortemmajor0 min
2026-06-04 10:10 UTCFly.io - Upstash Vector service disruption on IAD regionresolvednone3 h 58 min
2026-05-29 20:18 UTCIntermittent slowness in Vector US-EAST-1 regionresolvedminor11 h 32 min
2026-05-22 23:27 UTCNew Database Creation Failing Due to Upstream Provider Issueresolvednone32 min
2026-05-14 15:47 UTCUpstash Redis – intermittent connection issues in some regionsresolvedmajor1 h 44 min
2026-05-12 09:49 UTCFly.io Upstash Redis Service Distruptionpostmortemcritical3 h 59 min
2026-05-11 15:05 UTCFly.io Upstash Redis service distruption (FRA region)postmortemmajor3 h 16 min
2026-05-08 09:46 UTCQStash US Region Service Disruptionpostmortemcritical22 min
2026-05-05 14:24 UTCQStash US Region: Schedule Degradationpostmortemminor17 h 40 min
2026-04-02 18:45 UTCFly.io Upstash Redis – iad Region Elevated Latency and Temporary Read-Only Stateresolvedminor1 h 08 min
2026-03-27 15:30 UTCUpstash Redis: GCP Global Connectivity Problemsresolvednone0 min
2026-03-06 13:50 UTCRegion ap-northeast-1 outage on Upstash Globalpostmortemcritical59 min
2026-01-23 15:30 UTCUpstash Redis: Intermittent latency on us-east-1resolvedminor0 min
2025-12-10 11:50 UTCConnectivity issue impacting Regional Databases in US-East-1resolvedmajor17 min
2025-12-05 09:03 UTCUpstash Console and Context7 Console is Currently Experiencing issuesresolvedcritical14 min
2025-12-01 07:00 UTCQStash - Message delays for Flow Control configurationsresolvedminor0 min
2025-10-20 14:52 UTCUpstash Console issuesresolvedmajor3 h 58 min
2025-10-20 07:00 UTCLogin Issues on Upstash Consoleresolvedcritical0 min
2025-10-10 15:46 UTCConnectivity issue on us-east-1resolvedminor0 min
2025-09-09 12:00 UTCTemporary Database Routing Issueresolvedminor0 min
2025-08-18 12:37 UTCConnectivity Issues in us-east-1postmortemminor0 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Upstash with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "upstash"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}