Cloudflare vs VercelAI Gateway Benchmark Comparison
Cloudflare and Vercel were each faster in 1 of 4 shared AI gateway benchmarks, and 2 were 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 | Vercel | Result | Ratio |
|---|---|---|---|---|
| Anthropic Cold end-to-end latency · Run October 30, 2026 | 519ms 100% success | 495ms 100% success | Roughly even | 1.05x |
| OpenAI Cold end-to-end latency · Run October 30, 2026 | 803ms 100% success | 735ms 100% success | Vercel faster | 1.09x |
| Gemini Cold end-to-end latency · Run October 30, 2026 | 1971ms 100% success | 1966ms 100% success | Roughly even | 1.00x |
| Kimi Cold end-to-end latency · Run October 30, 2026 | 2100ms 100% success | 2209ms 100% success | Cloudflare faster | 1.05x |
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
The medians are within 5% of each other (519ms vs 495ms), so this counts as roughly even.
Median cold end-to-end latency over time
16 runs from July 22, 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
Vercel had a 1.09x lower median cold end-to-end latency (735ms vs 803ms for Cloudflare).
Median cold end-to-end latency over time
11 runs from August 21, 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
The medians are within 5% of each other (1971ms vs 1966ms), so this counts as roughly even.
Median cold end-to-end latency over time
10 runs from August 21, 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
Cloudflare had a 1.05x lower median cold end-to-end latency (2100ms vs 2209ms for Vercel).
Median cold end-to-end latency over time
11 runs from August 21, 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 and Vercel were each faster in 1 of 4 shared AI gateway benchmarks, and 2 were roughly even. In Anthropic (October 30, 2026), Cloudflare had a median cold end-to-end latency of 519ms and Vercel 495ms, which counts as roughly even. In OpenAI (October 30, 2026), Vercel had a median cold end-to-end latency of 735ms versus 803ms for Cloudflare, 1.09x faster. In Gemini (October 30, 2026), Cloudflare had a median cold end-to-end latency of 1971ms and Vercel 1966ms, which counts as roughly even. In Kimi (October 30, 2026), Cloudflare had a median cold end-to-end latency of 2100ms versus 2209ms for Vercel, 1.05x faster.