How can my agent or app check Xata status?

Fetch https://upbutler.com/status/xata/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"xata"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Xata's?

Add "xata" to the dependencies of your UpButler workspace. When one of your monitors fails while Xata has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Xata down?

Xata publishes no status we can read

Right now

Unknown. No machine-readable official status; see their status page.

No official machine-readable status

For agents

proceed

Proceed.

GET upbutler.com/status/xata/status.agent.json

MCP: upstream_status {"service":"xata"}

Postgres platform with branching.

What Xata says

status.xata.io has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful.

Their site: status.xata.io

What UpButler measured

There is no keyless endpoint of Xata that says anything useful, so UpButler does not probe it. To check your own Xata account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Xata incidents, last 90 days

Without a machine-readable source there is no incident history to show. Xata keeps its own at status.xata.io.

Get alerted when Xata goes down

Xata publishes no incidents we can read, so there is nothing to send an alert about. If you depend on it, monitor your own use of it: add a monitor with your key or URL.

Status badge

Show Xata's current status in a README or an internal wiki. It updates by itself.

[![Xata status](https://upbutler.com/status/xata/badge.svg)](https://upbutler.com/status/xata)

Tell your outage from Xata's

Declare that your project depends on Xata. When one of your monitors fails while Xata has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - xata

Ask before you retry

curl -s https://upbutler.com/status/xata/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "xata",
  "verdict": "proceed",
  "status": "unknown",
  "reason": "No machine-readable official status; see their status page",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Xata down right now?: We cannot tell. status.xata.io has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful. Their own status page is at https://status.xata.io.
Where does this status come from?: status.xata.io has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful.
How can my agent or app check Xata status?: Fetch https://upbutler.com/status/xata/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"xata"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Xata's?: Add "xata" to the dependencies of your UpButler workspace. When one of your monitors fails while Xata has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Xata. Status and incident text belong to Xata and are read from their public status source; the probe result is UpButler's own measurement.