- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 24of 100
What to do
Check whether you use Xata in us, us-east-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 27m it lasted.
Anything that failed between 2026-04-30 07:55 UTC and 2026-04-30 08:23 UTC may need a replay.Subscribe to Xata's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=xata works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Xata 3
- investigating
We're seeing some child branches of older database instances remain in "Setting up primary".
provider
- monitoring
Issue is now solved, continuing to monitor.
provider
- resolved
All branches are up now.
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-490632cd49
Is Xata still down?
No, this incident was resolved 2026-04-30 08:23 UTC. For Xata's live state, see https://down.guide/xata.
How long did it last?
27m, from 2026-04-30 07:55 UTC to 2026-04-30 08:23 UTC, by the times Xata posted.
What was affected?
Xata named in us, us-east-1.
What caused it?
Xata hasn't published a root cause. If it does, it shows here.
Where does this come from?
Xata's official status page, https://www.xatastatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.