OverblastAI gateway status
Checking…
Reading the last hour of requests.
Components
Each judged on its own requests over the last 24 hours. When it has too few to tell, it is judged on all traffic on our router instead, and its line says so.
Checking…
Everything on our router
Both products that run on it, and the two together. A quiet hour for one is judged on all of it.
Where the time goes
Every request split into the part spent in Overblast and the part spent with the model provider.
Loading…
The last hour, minute by minute
The slowest 5% of each minute’s requests, end to end.
Loading…
Breakdowns
The last 24 hours. Times are median / slowest 5%.
Loading…
Models available
How many models the gateway serves today, by kind.
What is measured
- Real traffic only: every model request to the AI gateway at /ai/v1, in the EU, US and global regions. Nothing here is a synthetic probe.
- Refused requests (no key, over a limit, out of balance) are counted in the requests, and never in the times, because they never reach a model provider.
- A failure is a request the model provider did not answer properly, or one we did not. Bad requests and refusals are not failures.
- The Overblast AI gateway and sponsoredtokens.com share one router and the same model providers. When the gateway has fewer than twenty requests in a window, its verdict is made from both products’ requests, and the sentence beside it says so. Every time on this page is the gateway’s own.
- “Overblast (ours)” is the time spent in Overblast before the model provider is called. The rest is the model provider. Model providers are not named on this page.
- Percentiles do not add up, so the total beside each bar is measured on its own and will not equal its three parts.
- All times are UTC. The data is updated every minute, and this page checks again every minute while it is open.