- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us, us-east-1
- Down Index
- 41of 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 10h 2m it lasted.
Anything that failed between 2026-01-07 12:00 UTC and 2026-01-07 22:03 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 investigating an increase in IO errors on clusters in the us-east-1 region.
provider
- identified
We have identified an issue affecting the connectivity of several clusters in the us-east-1 region and are working on a fix.
provider
- identified
We have identified a small number of affected clusters. We are working on restoring service to these clusters.
provider
- resolved
Availability has been restored. A few clusters are still in recovering, but their owners have been contacted.
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-8b8f2ccac7
Is Xata still down?
No, this incident was resolved 2026-01-07 22:03 UTC. For Xata's live state, see https://down.guide/xata.
How long did it last?
10h 2m, from 2026-01-07 12:00 UTC to 2026-01-07 22:03 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.