Is Xata Down?

No — Xata is up

Reachable from all 8 checked regions

Average response time: 208ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://www.xatastatus.com

Xata uptime

100%

Last 7 days

99.82%

Last 30 days

99.82%

Last 90 days

282ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 19 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

16-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

343ms

DNS 165ms TCP 8ms TLS 26ms TTFB 308ms

arn

271ms

DNS 61ms TCP 1ms TLS 11ms TTFB 258ms

bom

105ms

DNS 36ms TCP 1ms TLS 10ms TTFB 93ms

cdg

266ms

DNS 37ms TCP 9ms TLS 16ms TTFB 236ms

sin

58ms

DNS 8ms TCP 1ms TLS 7ms TTFB 49ms

sjc

93ms

DNS 39ms TCP 1ms TLS 9ms TTFB 86ms

syd

183ms

DNS 125ms TCP 1ms TLS 7ms TTFB 176ms

yyz

346ms

DNS 80ms TCP 17ms TLS 39ms TTFB 296ms

What Xata does

Xata is a managed Postgres platform for application developers, providing serverless databases with branching, schema management and a console for browsing data. Applications connect over standard Postgres connections while the management APIs handle provisioning and branches. Teams that use it hold their production application data there, so database connectivity sits on the path of nearly every request.

What an outage looks like

Applications fail to connect to the database or time out on queries while the rest of the stack is healthy. Xata reports database connectivity per cloud region, so a failure in one region leaves databases elsewhere untouched. The Console and Management APIs are separate components, so you can lose the ability to inspect or provision while running applications keep querying normally.

What to do about it

Read www.xatastatus.com, which is an own-domain page rather than the usual status subdomain, and find the row for your database's region. If the affected row is Console or Management APIs, your application is unaffected and only administration is blocked. Avoid creating or migrating branches during an incident, since a partially applied schema change is harder to reverse than a delayed one.

Is it down for everyone, or just you?

If this page says Xata is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Xata outage FAQ

Where is the Xata status page?

It is at www.xatastatus.com, on its own domain rather than a status subdomain of xata.io, which is why the usual guess does not resolve. Xata's own support documentation points to the same address and offers a subscription for incident notifications. Bookmark it before you need it, since finding it mid-incident costs time.

My Xata console is down. Can my application still reach the database?

Usually yes. Xata reports Console and Management APIs as components separate from database connectivity, so applications can keep querying while you cannot open the console or provision anything. Treat it as lost administration rather than an application outage, and confirm by checking your own connection rather than judging from the console.

Does a Xata outage in one region affect my database elsewhere?

No, connectivity is reported per region. Xata lists database connectivity separately for AWS us-east-1, AWS eu-central-1, AWS us-west-2, GCP us-central1 and GCP asia-southeast1, so an incident in one leaves the others serving normally. Check the row matching where your database actually lives rather than the headline state.

Will I lose data written during a Xata incident?

A connectivity failure normally prevents writes rather than losing accepted ones, so the usual outcome is queries that error rather than data that disappears. Xata does not publish a guarantee covering every failure mode, so verify recent writes once connectivity returns instead of assuming. Application-side retries are what turn a short outage into duplicate rows.

How we measure this

We request Xata's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Xata publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Xata goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required