Cloudflare vs NeonAI Gateway Benchmark Comparison

Cloudflare
Faster in 0 of 2
vs
Neon
Faster in 1 of 2

Neon was faster in 1 of 2 shared AI gateway benchmarks, and 1 was roughly even.

Shared benchmarks
2
Last run
October 30, 2026
Want the full run details?Sign up free →

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.

BenchmarkCloudflareNeonResultRatio
OpenAI
Cold end-to-end latency · Run October 30, 2026
803ms
100% success
830ms
100% success
Roughly even
1.03x
Kimi
Cold end-to-end latency · Run October 30, 2026
2100ms
100% success
947ms
100% success
Neon faster
2.22x

OpenAI

Run October 30, 2026

Time for a cold request routed through the gateway to GPT-5.4 Mini to return its complete response.

Cold end-to-end latency

Cloudflare

100% success
Median
803ms
P95
1155ms
P99
1537ms
Cloudflare OpenAI results →

Neon

100% success
Median
830ms
P95
989ms
P99
1022ms
Neon OpenAI results →

The medians are within 5% of each other (803ms vs 830ms), so this counts as roughly even.

Median cold end-to-end latency over time

10 runs from August 21, 2026 to October 30, 2026.

CloudflareNeon
View the full OpenAI leaderboard →

Kimi

Run October 30, 2026

Time for a cold request routed through the gateway to Kimi K3 to return its complete response.

Cold end-to-end latency

Cloudflare

100% success
Median
2100ms
P95
2891ms
P99
2973ms
Cloudflare Kimi results →

Neon

100% success
Median
947ms
P95
1665ms
P99
2312ms
Neon Kimi results →

Neon had a 2.22x lower median cold end-to-end latency (947ms vs 2100ms for Cloudflare).

Median cold end-to-end latency over time

11 runs from August 21, 2026 to October 30, 2026.

CloudflareNeon
View the full Kimi leaderboard →

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.

Neon was faster in 1 of 2 shared AI gateway benchmarks, and 1 was roughly even. In OpenAI (October 30, 2026), Cloudflare had a median cold end-to-end latency of 803ms and Neon 830ms, which counts as roughly even. In Kimi (October 30, 2026), Neon had a median cold end-to-end latency of 947ms versus 2100ms for Cloudflare, 2.22x faster.

PartnersGoogle Cloud Run