DataXAPI status

All systems normal

The state of 207 endpoints on 21 platforms is read live when this page opens: what is live, what is paused, and every incident with what was charged. A call that fails is charged $0.00.

State read 2026-10-21 08:10 UTC
In service now207 / 207endpoints, 0 paused
When an upstream failsRetried for youon the same route, or switched to a backup route
A route that keeps failingPaused, then backautomatically, as soon as it works again
Charged for failures$0.00a call that fails is released at once

By platform

What is live right now on each platform. An endpoint's own page says the same for that endpoint.

Checked every day with real calls · 4 days on record

Each endpoint's page says whether it is live right now. Browse endpoints →

What happens when something breaks

01Retried for you

An upstream that fails is tried again in the same call, on the same route, and the call switches to a backup route where the endpoint has one. You do not write the retry loop.

02Paused, then back

A route that keeps failing is paused automatically, so calls stop going to it. It is checked again every few minutes and takes calls again as soon as it works. When every route of an endpoint is paused, the endpoint answers 503 capability_paused and this page says so.

03Never charged for a failure

A failed, timed-out or uncertain call costs nothing: what it held is released at once. Every incident below says what was charged.

Incidents

What broke, for how long, and who paid for it.

No incidents on record.An incident is written here when one happens, and stays for 90 days, with what was charged for it.

Changelog

Stable parts only grow. What changed for callers is written here.

The full changelog →

Follow updates without an account:RSS /changelog/feed.xmlJSON GET /v1/catalog/status