- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 31of 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 3d 15h it lasted.
Anything that failed between 2025-11-25 10:26 UTC and 2025-11-29 01:31 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
- identified
New branches (parents and/or children) may experience delayed provisioning in the us-east-1 region.
provider
- monitoring
The incident has been resolved and we are continuing to monitor.
provider
- resolved
The incident has been resolved.
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-99354e5551
Is Xata still down?
No, this incident was resolved 2025-11-29 01:31 UTC. For Xata's live state, see https://down.guide/xata.
How long did it last?
3d 15h, from 2025-11-25 10:26 UTC to 2025-11-29 01:31 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.