All providers reachable
Probed directly from our servers when you load this page, at most once every five minutes. Nothing on this page is a stored marketing figure.
We publish two separate signals and never blend them. A probe asks the provider for its model list — cheap, immediate, and it answers “is anyone home”. Real traffic success is the share of routed requests that actually completed, which is slower to move but is what your users experienced. A provider can pass every probe while failing every completion, and averaging the two would hide exactly that.
We publish no uptime SLA. We have not been running long enough for one to mean anything, and a number we cannot evidence is worth less than no number at all.
- Probe latency
- 1.30s
- Probes up
- 100.0%
- Real traffic
- none yet
- Probe latency
- 302ms
- Probes up
- 100.0%
- Real traffic
- none yet
- Probe latency
- 279ms
- Probes up
- 100.0%
- Real traffic
- 5 req
- Probe latency
- 1.28s
- Probes up
- 100.0%
- Real traffic
- none yet
- Probe latency
- 574ms
- Probes up
- 100.0%
- Real traffic
- 55.0%
- Probe latency
- 86ms
- Probes up
- 9 samples
- Real traffic
- 2 req
What happens when one of these is down
Models served by more than one provider fail over automatically: a 429 or 5xx moves the request to the next route before the first token is sent. Models with a single provider fail with a 502 or 504 naming that provider — we do not silently substitute a different model, because a quietly different answer is much harder to notice than an error.
| Signal | Refreshed | Window |
|---|---|---|
| Reachability probe | On page load, at most every 5 minutes | Latest result |
| Probe success rate | Same | 30 days, shown at 10+ samples |
| Real traffic success | Continuously | 30 days, shown at 20+ requests |