Status
All systems operationalEvery route is tested with a real request every five minutes: a chat completion, an embedding, a transcription and so on, not a ping. Last run 2026-11-01 12:05 UTC.
| Check | Now | Latency | Uptime 24 h | Uptime 7 d | Last 4 hours |
|---|---|---|---|---|---|
| API gateway | Operational | 80 ms | 100% | 97.82% | |
| Model list | Operational | 14 ms | 100% | 97.82% | |
| Chat (Together-hosted models) | Operational | 453 ms | 100% | 97.67% | |
| Chat: GPT-OSS 120B | Operational | 463 ms | 100% | 97.87% | |
| Chat (DeepInfra-hosted models) | Operational | 531 ms | 100% | 97.77% | |
| Responses API | Operational | 3,159 ms | 100% | 97.77% | |
| Embeddings | Operational | 289 ms | 100% | 98.02% | |
| Rerank | Operational | 279 ms | 99.65% | 97.42% | |
| Text to speech | Operational | 329 ms | 100% | 98.07% | |
| Speech to text | Operational | 651 ms | 100% | 98.12% |
Uptime is the share of probes that passed. History began 2026-10-24 12:05 UTC. Latency is the whole request as seen from the probe, generation included.
What is checked. The chat checks send a one-line prompt with thinking switched off to a model on each upstream, plus GPT-OSS 120B separately because it is the most used; they pass when text comes back. The Responses API check passes on a completed response. Embeddings must return a 1,024-dimension vector, rerank must put the right passage first, text to speech must return audio, and speech to text must transcribe that audio correctly. Probes run on the API server itself, so a network problem between you and us would not show here. A single failed probe is usually a busy backend and clears on retry; two or more in a row are listed as an incident below.
If your requests fail while everything here is green, check the error docs first: 401 and 402 are account-side, and 404 model_not_found means the id is not in the catalog.
Incidents
| When (UTC) | Event |
|---|---|
| 2026-10-29 20:36 | Responses API failed 2 probes in a row, until 20:41. |
| 2026-10-29 00:30 | Rerank failed 3 probes in a row, until 00:40. |
| 2026-10-28 12:40 | Chat (DeepInfra-hosted models) failed 2 probes in a row, until 12:45. |
| 2026-10-28 11:07 | API gateway failed 3 probes in a row, until 11:09. |
| 2026-10-28 11:07 | Model list failed 3 probes in a row, until 11:09. |
| 2026-10-28 11:07 | Chat (Together-hosted models) failed 2 probes in a row, until 11:08. |
| 2026-10-28 11:07 | Chat: GPT-OSS 120B failed 2 probes in a row, until 11:08. |
| 2026-10-28 11:07 | Chat (DeepInfra-hosted models) failed 2 probes in a row, until 11:08. |
| 2026-10-27 06:17 | API gateway failed 8 probes in a row, until 06:45. |
| 2026-10-27 06:17 | Model list failed 8 probes in a row, until 06:45. |
| 2026-10-27 06:17 | Chat (Together-hosted models) failed 7 probes in a row, until 06:44. |
| 2026-10-27 06:17 | Chat: GPT-OSS 120B failed 7 probes in a row, until 06:44. |
| 2026-09-17 | Status page moved from page-load pings to scheduled end-to-end probes. Gateway updates during the day added routes and fixed tool-calling bugs; see the changelog. |
| 2026-09-16 | TLS certificate for api.inferenceapis.com renewed after a lapse earlier in the day. Requests during the lapse failed certificate validation. |
Something wrong that is not shown here? Tell us.
