- Level
- confirmed
- Worst impact
- Major outage
- Components
- N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Oregon, USA (us-west-2), Frankfurt, Germany (eu-central-1), Ireland (eu-west-1), Singapore (ap-southeast-1), Sydney, Australia (ap-southeast-2), Mumbai, India (ap-south-1), Tokyo, Japan (ap-northeast-1), São Paulo, Brazil (sa-east-1), Ohio, USA (us-east-2), London, UK (eu-west-2)
- Regions
- ap-northeast-1, ap-south-1, ap-southeast-1, ap-southeast-2, apac, au, eu, eu-central-1, eu-west-1, eu-west-2, in, jp, latam, sa-east-1, us, us-east-1, us-east-2, us-west-1, us-west-2
- Down Index
- 62of 100
What to do
Check whether you use Upstash N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Oregon, USA (us-west-2), Frankfurt, Germany (eu-central-1) and 8 more in ap-northeast-1, ap-south-1, ap-southeast-1, ap-southeast-2. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 11m it lasted.
Anything that failed between 2025-06-11 06:51 UTC and 2025-06-11 10:02 UTC may need a replay.Subscribe to Upstash's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=upstash works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Upstash 5
- investigating
We are currently investigating this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
- postmortem
A routine system maintenance operation at the OS level led to the application of system updates across multiple EC2 instances in our clusters in several AWS regions. These updates included changes to networking components, which inadvertently triggered restarts. As a result, several EC2 nodes failed health checks and temporarily dropped out of the cluster, disrupting high availability and causing partial connectivity issues for some clients and operations. We have since reproduced the issue in a controlled environment and verified the root cause. To prevent a recurrence, we are updating our node maintenance strategy to ensure greater control over the timing and impact of system-level changes and excluding networking components from automated upgrades.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-774bb4b3c2
Is Upstash still down?
No, this incident was resolved 2025-06-11 10:02 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
3h 11m, from 2025-06-11 06:51 UTC to 2025-06-11 10:02 UTC, by the times Upstash posted.
What was affected?
Upstash named N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Oregon, USA (us-west-2), Frankfurt, Germany (eu-central-1) and 8 more in ap-northeast-1, ap-south-1, ap-southeast-1, ap-southeast-2.
What caused it?
Upstash hasn't published a root cause. If it does, it shows here.
Where does this come from?
Upstash's official status page, https://status.upstash.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.