Initial run - a single 1-hour window on mainnet, published raw and unedited. Continuous, multi-route benchmarks follow. The point of publishing early is the method: match by signature, separate ACK from first-seen, show the tail.
The experiment in one screen
| Field | Value |
|---|---|
| Method | QUIC transaction relay |
| Window | 1 hour |
| Captured | 2026-06-30 · 09:14 UTC |
| Route | Yellowstone TPU · Frankfurt |
| Submissions | 2,202 |
| Observed | 2,121 (96.32%) |
| Deshred p50 / p90 / p99 | 104 / 375 / 838 ms |
| Route ACK p50 | 0.01 ms |
Methodology note: ACK latency is gateway health, not landing latency. Landing evidence uses deshred and processed observations matched by signature - so the number that matters is submit → first-seen, not the gateway ACK.
Full tables: benchmark report.
Percentiles (submit path)
| Percentile | Client ACK (ms) | Route ACK (ms) | Deshred (ms) | Processed (ms) |
|---|---|---|---|---|
| p50 | 0.31 | 0.01 | 104 | 106 |
| p75 | 0.37 | 0.01 | 199 | 200 |
| p90 | 0.48 | 0.02 | 375 | 375 |
| p95 | 0.58 | 0.02 | 511 | 511 |
| p99 | 0.79 | 0.03 | 838 | 839 |
| max | 1.62 | 0.11 | 45,412 | 45,417 |
Tail latency is real and shown, not hidden.
By leader region (deshred)
| Region | Submitted | Observed | Rate | p50 (ms) | p90 (ms) | p99 (ms) |
|---|---|---|---|---|---|---|
| Europe | 1,311 | 1,260 | 96.1% | 70 | 260 | 1,022 |
| Asia Pacific | 271 | 248 | 91.5% | 265 | 650 | 788 |
| US East | 194 | 191 | 98.5% | 159 | 360 | 782 |
| US Central | 140 | 138 | 98.6% | 111 | 178 | 413 |
| US West | 46 | 46 | 100% | 167 | 443 | 467 |
| Unknown | 240 | 238 | 99.2% | 109 | 199 | 614 |
Fastest leaders sat where the physics is best: Frankfurt validators landed at 20-48 ms p50, with Amsterdam and Stockholm close behind.
How to read without over-claiming
- Do not quote route ACK as landing latency.
- Read observation rate and tails together - a clean p50 with a 45 s max is still a real path.
- Region tables are leader geography, not client geography.
- One hour is the first public window, not a continuous SLA board.
Harness: solana-tx-bench.
Next
Open the full report and compare with later leader-paced A/B runs on /benchmarks.
To send on the co-located path in production, get started or start self-serve on app..