# Status

Whether the Texa API, Texa AI, Texa Desk and webhooks are working, the last 90 days, and incident notes.


[https://status.texadesk.com](https://status.texadesk.com) shows whether each part of Texa is working now, checked every
minute, with the last 90 days and Texa's notes on any incident.

| Part | Checks |
|---|---|
| Texa API | it answers, and its database answers |
| Texa AI | its engine is ready |
| Texa Desk | it answers |
| Webhooks | deliveries aren't waiting behind |

Each day of the 90 is a bar: working, slow or partly working for a few minutes, not working for a few
minutes, or grey when nothing was recorded. Runs of three minutes or more that a part wasn't working
are listed as outages, found by Texa's own checks, beside the notes Texa's team posts while it works on
an incident (looking into it, cause found, fixed and watching, resolved).

## For machines

```bash
curl https://status.texadesk.com/status.json
```

```json
{"status": "operational",
 "components": {"api": "operational", "texa_ai": "operational", "texa_desk": "operational",
                "webhooks": "operational"},
 "checked_at": 1790000000}
```

Each component is `operational`, `degraded` or `down`; `status` is the worst of them.
`/status.json?history=1` adds `history` (per part, a day by day count of minutes checked, degraded and
down, and its `uptime` over 90 days), `outages` and `incidents`. It answers any origin, so a dashboard
of yours can read it from the browser.

The same page and JSON are on the API's own domain, at [https://api.texadesk.com/status](https://api.texadesk.com/status).

If something is wrong and the status page says it's working, write to
[info@texadesk.com](mailto:info@texadesk.com) with a request id (`X-Request-Id`).