- Level
- confirmed
- Worst impact
- Degraded
- Regions
- ap-southeast-1
- Down Index
- 12of 100
What to do
Check whether you use Upstash in ap-southeast-1. 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 0m it lasted.
Anything that failed between 2024-03-13 09:30 UTC and 2024-03-13 08:30 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 1
- resolved
We have taken actions to increase the capacity of the region. During the operation, clients might have experienced higher than usual latencies for about 15 minutes.
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-fd371dd15b
Is Upstash still down?
No, this incident was resolved 2024-03-13 08:30 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
0m, from 2024-03-13 09:30 UTC to 2024-03-13 08:30 UTC, by the times Upstash posted.
What was affected?
Upstash named in ap-southeast-1.
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.