Vendor reports: major outageResolved · vendor status “postmortem”Official status API

Fly.io Upstash Redis Service Distruption

Reported by Upstash · Cloud & Infrastructure · source last read just now

Official source (opens in a new tab)
Vendor start
May 12, 2026, 09:49 UTC
Vendor's clock
Resolved
May 12, 2026, 13:48 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
3 h 59 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Upstash reports major outage: "Fly.io Upstash Redis Service Distruption".[E1, E2]
  • The vendor marked it resolved at 2026-05-12 13:48 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-05-12 13:48 UTC · summary s1, evidence 8064637b2e166342

Evidence (7)
  1. E1Upstash reports major outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Fly.io Upstash Redis Service Distruption". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "postmortem". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-05-12 09:49 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-05-12 13:48 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Upstash is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. May 12, 2026, 09:49 UTCVendor-reported startVendor time
  2. May 12, 2026, 13:48 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.