Is Xata Down?

No — Xata is up

Xata's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 291 ms

Right now

The verdict is the worse of these two. How we decide

Xata's status page

xatastatus.com · read 2 minutes ago · checked every 3 minutes

Operational

Xata's components, as its status page reports them
Component	Status
Console	Operational
Management APIs	Operational

5 locations All operational

Open their status page

FlareWarden checks

xata.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 291 ms
Checked: 55 minutes ago

By region

Amsterdam reachable, 362 ms
Chicago reachable, 165 ms
Paris reachable, 252 ms
San Jose reachable, 236 ms
Singapore reachable, 135 ms
Stockholm reachable, 819 ms
Sydney reachable, 174 ms
Toronto reachable, 190 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	135 ms	6 ms	19 ms	341 ms
Chicago	66 ms	11 ms	17 ms	131 ms
Paris	20 ms	9 ms	20 ms	212 ms
San Jose	78 ms	4 ms	10 ms	221 ms
Singapore	75 ms	2 ms	8 ms	127 ms
Stockholm	66 ms	1 ms	10 ms	810 ms
Sydney	112 ms	1 ms	7 ms	167 ms
Toronto	55 ms	11 ms	30 ms	156 ms

We check that xata.io loads, not every feature behind it. Test it yourself

History

Incidents Xata reported

Since Oct 22, 15 days · from xatastatus.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Xata website availability

Measured by FlareWarden · xata.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 328ms

Last 30 days

65-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of xata.io from multiple regions every 6 hours. Xata's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 65 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Xata itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Xata goes down

We check Xata every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required