New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages — May 2026
Services Pricing Dashboard

Upstash Outage History

Uptime record, past incidents, and downtime history for Upstash.

Checking current status...
89% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Feb 25May 25

Monthly Uptime

Month Uptime Days Tracked Days with Issues
May 2026 72% 25 7
April 2026 93.3% 30 2
March 2026 96.8% 31 1
February 2026 100% 5 0

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Feb 24 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

May 2026
New Database Creation Failing Due to Upstream Provider Issue

Started: May 22, 11:27 PM

monitoring
Upstream issue resolved — new database creation is working again. We're monitoring to confirm full recovery.
May 22, 11:48 PM
investigating
New database provisioning is currently failing due to an ongoing upstream provider issue affecting DNS. Existing databases and connections are unaffected — only the creation flow is impacted. We're monitoring the situation and will update once the upstream issue is resolved.
May 22, 11:27 PM
Upstash Redis – intermittent connection issues in some regions
major

Started: May 14, 3:47 PM

monitoring
A fix has been implemented and we are monitoring.
May 14, 4:00 PM
identified
The issue has been identified and a fix is being implemented.
May 14, 3:49 PM
monitoring
We identified intermittent connection issues affecting some regions. Fix is being deployed. We'll update the list of affected regions shortly.
May 14, 3:47 PM
Fly.io Upstash Redis Service Distruption
critical

Started: May 12, 9:49 AM

monitoring
A fix has been implemented and we are monitoring the results.
May 12, 12:05 PM
identified
The issue has been identified and the fix is being implemented.
May 12, 10:50 AM
investigating
Some regions are experiencing connectivity issues due to an ongoing network problem. We are currently investigating
May 12, 9:49 AM
Fly.io Upstash Redis service distruption (FRA region)
major

Started: May 11, 3:05 PM

investigating
We are working with Fly team to investigate the root cause.
May 11, 5:19 PM
investigating
We are continuing to investigate the issue.
May 11, 3:07 PM
investigating
Some databases may experience increased latency or timeouts in Fly.io’s FRA region.
May 11, 3:05 PM
QStash US Region Service Distruption
critical

Started: May 8, 9:46 AM

monitoring
A fix has been implemented and we are monitoring the results.
May 8, 10:06 AM
investigating
We are continuing to investigate this issue.
May 8, 9:46 AM
investigating
We are currently investigating the issue.
May 8, 9:46 AM
QStash US Region: Schedule Degradation
minor

Started: May 5, 2:24 PM

monitoring
Main schedule functionality is back to normal. We are currently checking if previously created schedules are delivered as expected before marking the incident as resolved.
May 5, 9:31 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 5, 3:44 PM
identified
We are continuing to work on a fix for this issue.
May 5, 2:29 PM
identified
We are currently experiencing issues in the US region. - Duplicate Deliveries: During this period, some scheduled jobs may be executed twice. - Schedule Disruption: Schedules created between April 24, 2026 and May 2, 2026 are currently not running. Our team is actively working on a fix. Once the migration is complete, affected schedules will resume normal operation. We will provide updates as progress continues.
May 5, 2:24 PM
April 2026
QStash us-east-1 Schedules
major

Started: Apr 27, 4:09 PM

monitoring
A fix has been implemented and we are monitoring the results.
Apr 27, 7:04 PM
identified
Some users on QStash US might be experiencing schedule issues.
Apr 27, 4:09 PM
Fly.io Upstash Redis – iad Region Elevated Latency and Temporary Read-Only State
minor

Started: Apr 2, 6:45 PM

identified
Servers in the iad region experienced unexpected disk load, resulting in elevated latencies and a temporary read-only state. We are migrating replicas to new instances to mitigate the issue and expect to have it fully resolved shortly.
Apr 2, 6:45 PM