- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 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 50m it lasted.
Anything that failed between 2026-07-22 19:04 UTC and 2026-07-22 19:54 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
GCP regions are failing to provision new branches. Investigating the cause.
provider
- identified
Issue is identified and we are applying a fix.
provider
- monitoring
Issue should be solved, monitoring.
provider
- resolved
Issue is now 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-1aa24d0bde
Is Xata still down?
No, this incident was resolved 2026-07-22 19:54 UTC. For Xata's live state, see https://down.guide/xata.
How long did it last?
50m, from 2026-07-22 19:04 UTC to 2026-07-22 19:54 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.