Status
Which engines are answering
0 of 5 measured engines answered every scan in the last 30 days. The rest missed runs, listed below.
- Window
- 30 days
- Scans counted
- 41
- Engines measured
- 5 of 5
Per engine
Answered means the run completed and its numbers were usable. An engine needs 3 runs inside the window before this page will call its state at all.
- ChatGPTAnswered 0 of 41 runsNot answering
- PerplexityAnswered 11 of 41 runsNot answering
- ClaudeAnswered 0 of 41 runsNot answering
- GeminiAnswered 35 of 41 runsMissed runs
- AI OverviewsAnswered 19 of 41 runsNot answering
Oldest run counted Jul 30, 2026, newest Aug 22, 2026. Sample capped at the most recent 500 runs.
How this page is built
The mechanism, so the numbers above can be argued with.
- Every scan records the engines it asked and the ones where more than half the calls failed, which is the same signal a customer report uses to say an engine did not respond rather than reporting a measured zero.
- This page counts those verdicts over the last 30 days. It is the providers as we reach them on real customer traffic, not a synthetic ping from a probe network, which is the only version of the question worth answering.
- Mock runs are excluded, so a development environment cannot paint this page.
- Below 3 runs an engine reads as not enough runs, because a state drawn from one or two samples is a claim about a population from a sample that cannot carry it.
- Counts are cached and refresh every 5 minutes. Loading this page never starts a scan.
The prompt basket, the sampling and the confidence band are all written up in the method.
What we shipped
The changelog is the other half of this page: what moved, when, and the commit it landed in. Most recent entry Aug 22, 2026.