- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 29of 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 5h 4m it lasted.
Anything that failed between 2026-02-24 12:31 UTC and 2026-02-24 17:34 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 4
- investigating
We are currently investigating a small number of clusters facing I/O errors in us-east-1 region
provider
- identified
A routine update caused an issue with one of our storage nodes. We are currently working on a remediation
provider
- monitoring
All active clusters have recovered.
provider
- resolved
All good.
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-3145a08888
Is Xata still down?
No, this incident was resolved 2026-02-24 17:34 UTC. For Xata's live state, see https://down.guide/xata.
How long did it last?
5h 4m, from 2026-02-24 12:31 UTC to 2026-02-24 17:34 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.