- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 100
What to do
Check whether your product depends on Xata. 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 34m it lasted.
Anything that failed between 2026-07-28 07:35 UTC and 2026-07-28 08:08 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 issue affecting provisioning of new clusters
provider
- identified
We have identified the root cause on new nodes added after capacity increase, we are working on remediating the issue
provider
- monitoring
We have implemented a fix and are currently monitoring the situation
provider
- resolved
The issue 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-561d1312c7
Is Xata still down?
No, this incident was resolved 2026-07-28 08:08 UTC. For Xata's live state, see https://down.guide/xata.
How long did it last?
34m, from 2026-07-28 07:35 UTC to 2026-07-28 08:08 UTC, by the times Xata posted.
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.