Minor impactResolvedDatabases

Upstash incident: Fly.io Upstash Redis – iad Region Elevated Latency and Temporary Read-Only State

Upstash reported this minor-impact incident on its official status page on Apr 2, 2026, 18:45 UTC. It was resolved after 1h 8m.

Right now Upstash is operational. Live Upstash status →

🔔 Get alerted when Upstash has issuesFree · email alerts · no credit card
Apr 2, 2026, 18:45 UTC
started
Apr 2, 2026, 19:53 UTC
resolved
1h 8m
duration
Minor
impact

Timeline

updates from Upstash's status page ↗
  1. resolvedApr 2, 2026, 19:53 UTC

    Replication complete, incident resolved.

  2. identifiedApr 2, 2026, 18:45 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Upstash's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Upstash have incidents?

Upstash reported 3 incidents in the last 90 days, 1 of them major or critical. See Upstash's uptime and incident history

← Previous: Region ap-northeast-1 outage on Upstash Global (Mar 6, 2026)Next: QStash US Region: Schedule Degradation (May 5, 2026) →
Upstash incident on Apr 2, 2026: Fly.io Upstash Redis – iad Region Elevated Latency and Temporary Read-Only State · APIStatus.watch