Most "latency benchmarks" are marketing screenshots. This one is a leader-paced paired A/B with published eligibility rules, same-slot tables, and an open harness.

If you route Solana transactions for a living, you care about produced-block order, not a vanity RTT tile.

The experiment in one screen

FieldValue
ArmsDoubleZero vs Public Internet
Methodleader-paced paired A/B
Window1 hour
Captured2026-07-13 · 02:54 UTC
RouteDoubleZero IBRL vs public Internet · Frankfurt
Paired leader runs246
Same-slot pairs201
Leader identities29
PoH candidate-or-tied98.0%

Eligible windows only: the leader has DoubleZero TPU open. Both arms shared the Frankfurt host, relay binary, transaction shape, recent blockhash, slot trigger, and leader TPU endpoint.

Full tables: benchmark report.

Same-slot is the only fair table

A pair only enters the comparison when both arms land in the same produced slot. Different-slot and one-arm-only outcomes are coverage. They are not timing wins.

Placement metricDoubleZero earlierSamePublic earlier
Preceding PoH ticks911064
Processed tx index115086
Entry index113484

PoH ticks and processed transaction index describe block order. First-observed milliseconds include receiver and read-path noise. Treat placement as primary.

Distance is the real variable

Short-haul leaders and long-haul leaders are not the same race.

DistanceSame-slot pairsDoubleZero earlierTiedPublic earlier
Under 1,000 km10951013
1,000-5,000 km1010
At least 5,000 km908541
Coordinate unavailable1100

Under 1,000 km, most pairs landed in the same PoH interval. Beyond 5,000 km in this window, DoubleZero led on preceding PoH ticks in 85 of 90 same-slot pairs.

If your leaders sit next door, the public Internet path can look fine on PoH. If your leaders sit an ocean away, the route choice shows up in the same tables.

How to read without over-claiming

  1. Read eligibility first. Only windows that match the method count.
  2. Prefer placement metrics over observation time.
  3. Slice by distance before you generalize.
  4. One hour is evidence for that window, not a product promise.
  5. Open the harness if you disagree with the design.

Harness: solana-tx-bench.

Next

Open the full report, check the same-slot and distance tables, then run the harness on your own traffic shape if you need a second opinion.

All runs: /benchmarks.

If you want the same class of path control in production, get started or start self-serve on app..

Frequently asked questions

What is a leader-paced paired A/B?
For each eligible leader window, the harness sends one transaction through the candidate path and one through the baseline path with the same host, binary, transaction shape, recent blockhash, slot trigger, and leader TPU endpoint. Only pairs that land in the same produced slot enter the timing tables.
Why prefer PoH placement over first-observed milliseconds?
Preceding PoH ticks and processed transaction index describe order inside the produced block. First-observed milliseconds include receiver and read-path noise. Treat placement as primary and observation time as secondary.
Does one hour prove a product SLA?
No. One measured window is evidence for that window under published eligibility rules. Continuous multi-route runs and open harnesses are how you keep claims honest over time.