Cloudflare vs LLM APIAI Gateway Benchmark Comparison
Cloudflare was faster in 3 of 4 shared AI gateway benchmarks, and 1 was roughly even.
- Shared benchmarks
- 4
- Last run
- October 30, 2026
Scorecard
Median of each benchmark's primary metric; lower is better. Medians within 5% count as roughly even, and a benchmark gets no speed verdict when either provider completed fewer than 50% of runs.
| Benchmark | Cloudflare | LLM API | Result | Ratio |
|---|---|---|---|---|
| Anthropic Cold end-to-end latency · Run October 30, 2026 | 519ms 100% success | 762ms 100% success | Cloudflare faster | 1.47x |
| OpenAI Cold end-to-end latency · Run October 30, 2026 | 803ms 100% success | 1781ms 100% success | Cloudflare faster | 2.22x |
| Gemini Cold end-to-end latency · Run October 30, 2026 | 1971ms 100% success | 2220ms 100% success | Cloudflare faster | 1.13x |
| Kimi Cold end-to-end latency · Run October 30, 2026 | 2100ms 100% success | 2118ms 100% success | Roughly even | 1.01x |
Anthropic
Run October 30, 2026Time for a cold request routed through the gateway to Claude Haiku 4.5 to return its complete response.
Cold end-to-end latency
Cloudflare had a 1.47x lower median cold end-to-end latency (519ms vs 762ms for LLM API).
Median cold end-to-end latency over time
10 runs from August 28, 2026 to October 30, 2026.
OpenAI
Run October 30, 2026Time for a cold request routed through the gateway to GPT-5.4 Mini to return its complete response.
Cold end-to-end latency
Cloudflare had a 2.22x lower median cold end-to-end latency (803ms vs 1781ms for LLM API).
Median cold end-to-end latency over time
10 runs from August 28, 2026 to October 30, 2026.
Gemini
Run October 30, 2026Time for a cold request routed through the gateway to Gemini 3.6 Flash to return its complete response.
Cold end-to-end latency
Cloudflare had a 1.13x lower median cold end-to-end latency (1971ms vs 2220ms for LLM API).
Median cold end-to-end latency over time
9 runs from August 28, 2026 to October 30, 2026.
Kimi
Run October 30, 2026Time for a cold request routed through the gateway to Kimi K3 to return its complete response.
Cold end-to-end latency
The medians are within 5% of each other (2100ms vs 2118ms), so this counts as roughly even.
Median cold end-to-end latency over time
10 runs from August 28, 2026 to October 30, 2026.
Methodology
- One workload, every provider. The same script, payload, and model hit every provider, addressed the way its own API expects. Nobody gets a tuned or special path.
- Repeated on a schedule. Every suite runs many iterations per provider, automated on a recurring schedule, so results reflect steady state rather than one lucky request.
- Raw results published. Every run is committed as JSON to the public benchmarks repo, next to the code that produced it. Nothing is cherry-picked or held back.
- How this comparison is built. Each benchmark compares the two providers' medians; results within 5% count as roughly even. A comparison is published only when both providers completed the latency benchmark on at least two of the same model families reliably: at least 50% success for each provider, in benchmark runs from the last 30 days.
Frequently asked questions
Have another question? Email us.
Cloudflare was faster in 3 of 4 shared AI gateway benchmarks, and 1 was roughly even. In Anthropic (October 30, 2026), Cloudflare had a median cold end-to-end latency of 519ms versus 762ms for LLM API, 1.47x faster. In OpenAI (October 30, 2026), Cloudflare had a median cold end-to-end latency of 803ms versus 1781ms for LLM API, 2.22x faster. In Gemini (October 30, 2026), Cloudflare had a median cold end-to-end latency of 1971ms versus 2220ms for LLM API, 1.13x faster. In Kimi (October 30, 2026), Cloudflare had a median cold end-to-end latency of 2100ms and LLM API 2118ms, which counts as roughly even.