What was measured
The comparison is based on precomputed observations from the i6eal AI Latency Index. Medians of daily measurements in two completed UTC weeks are compared, only for weekdays with a value in both weeks. Seven endpoints had sufficient paired days and unchanged model and route descriptions; three of them show a change flagged in the index.
What the numbers suggest
You can read from this data how response time shifted within the same, unchanged endpoint between the two weeks. For Mistral Small via the gateway route the median dropped clearly, and for Claude Haiku 4.5 via AWS Bedrock it also dropped. For GPT-5 mini via the direct OpenAI route the value rose. These directions only apply within each endpoint.
Where the evidence ends
The measurement is a short synthetic probe with a short prompt, not a measurement of your full workload. It establishes no cause for the changes, no statistical significance, and no statement about model quality or reliability. Direct and gateway routes are not ranked against each other, so the table is not a ranking of providers.
What you can take away
For your own architecture decisions the key point is that latency varies between weeks and can develop differently per endpoint. If you want to assess latency for a specific application, a measurement of your own with your prompts and load is worthwhile.
Observed latency changes
| Endpoint | Route | Paired days per week | Before TTFT (ms) | Current TTFT (ms) | Change |
|---|---|---|---|---|---|
| Mistral Small (Mistral) | gateway | 7 | 443.00 | 332.00 | -25.06 % |
| Claude Haiku 4.5 (AWS Bedrock) | direct | 7 | 703.00 | 573.00 | -18.49 % |
| GPT-5 mini (OpenAI) | direct | 7 | 685.00 | 809.00 | +18.10 % |
2026-10-19–2026-10-25 → 2026-10-26–2026-11-01 (UTC).
Coverage and measurement limits
7 endpoints have sufficient paired days and unchanged model/route descriptions. 0 endpoints have insufficient paired days; 0 were excluded because model/route descriptions changed.
TTFT measures time to the first content token from a Lambda in Frankfurt. This compares medians of daily measurements in two completed UTC weeks. Only weekdays with a value in both weeks count; each endpoint needs at least five paired days. The collector discards a warm-up and keeps the faster of two successful probes per measurement round. This is a short synthetic probe, not a measurement of your entire workload. Direct and gateway routes are not ranked against each other. Observed differences establish no cause, statistical significance, model quality or reliability.
i6eal KI-Latenz-Index. Source timestamp: 2026-11-02T01:20:59.204Z.
Sources
Editorially owned by Ideal Syka. Sources and method: Newsroom & method. Tips and corrections: ai@i6eal.de.
