◆ BENCHMARKS

How we measure. And what we won't fake.

Our edge is physics: co-located bare metal at Equinix FR13, beside the Solana stake clusters and the Jito Block Engine. This page documents exactly how we benchmark - and we publish numbers only once they're measured against a real workload. The first dated reports, raw evidence, and reproduction instructions below.

◢ Benchmark your stackView pricing →

◆ WHAT WE MEASURE

The three numbers that decide a trade.

P50 / P99 latency

Round-trip time from request to response. We report the median (P50) and the tail (P99) - for trading the tail matters more than the average, so we never hide it behind a single number.

Landing rate

The share of sendTransaction calls that land in the target slot window under real load. A fast send that doesn't land is worthless, so we measure landing, not just submission.

First-seen delta

How much earlier the preprocessed stream surfaces a transaction versus waiting for confirmation - measured against your own subscription, not a synthetic feed.

◆ WHERE & HOW

Measured where it actually runs.

Where

Co-located bare metal at Equinix FR13 (Frankfurt), racked beside Solana stake clusters and the Jito Block Engine. Single-region today; the edge is physical distance, not a marketing claim.

Against your workload

We measure with your methods, regions, and traffic shape - not a best-case synthetic loop. Numbers depend on where you are and what you do, so one hero figure would be dishonest.

Window

Rolling 24-hour measurement, P50 and P99 reported side by side, landing rate as a share. Each published report is dated and carries its own methodology so you can check the work.

◆ REPORTS

Published runs.

2026-07-13 · 02:54 UTC

DoubleZero IBRL versus public Internet

One-hour leader-paced A/B from Frankfurt: for every eligible Solana leader window (DZ TPU open), one transaction through DoubleZero IBRL and one through the public Internet. Same host, relay binary, transaction shape, blockhash, slot trigger, and leader TPU endpoint.

98% PoH earlier or tied201 same-slot pairsDoubleZero IBRL vs public Internet · Frankfurt
View report →
2026-07-11 · 07:56 UTC

SubscribeDeshred versus processed gRPC

55,424 matched Pump AMM transaction signatures comparing rpc edge pre-execution deshred with normal processed Yellowstone gRPC.

99.92% deshred first4.64 ms median lead55,424 paired signatures
View report →
2026-06-30 · 09:14 UTCinitial run

QUIC transaction relay, the first 1-hour run

2,202 transactions sent through the co-located QUIC relay (Yellowstone TPU, Frankfurt). First-seen (deshred) and processed timing matched by signature.

96.3% observed104 ms p50 first-seenYellowstone TPU · Frankfurt
View report →

Looking for continuous operational signals? The solbench live board is pending co-located numbers - separate from these reviewed, published reports.

// want it measured against your own stack? start an onboarding benchmark - DM us on Telegram. last updated 2026-07-13

◆ BENCHMARK FAQ

Honest answers, no hero numbers.

Why don't you publish a single latency number?
Because it would be marketing, not measurement. Real latency depends on your region, your call mix, and current network conditions. We co-locate at Equinix FR13 beside the stake clusters and the Jito Block Engine to win on physics, then benchmark the actual numbers against your workload during onboarding - and publish dated reports with the methodology attached.
Where are your servers?
Equinix FR13 in Frankfurt - co-located bare metal beside Solana stake clusters and the Jito Block Engine. It is a single region today, chosen for proximity to where blocks are built.
What does 'landing rate' mean?
The share of sendTransaction calls that actually land in the target slot window under real load. A transaction sender that submits fast but doesn't land is useless to a trader, so landing rate is the number we hold ourselves to.
How do I see real numbers for my setup?
Start an onboarding benchmark - we measure P50/P99 latency, landing rate, and first-seen delta against your own methods and region. Qualified teams can also request 24h testing access or a vetted 15-day Trader trial. Ask on Telegram: https://t.me/rpcedge.
Are there published reports yet?
Yes - Reports above covers a DoubleZero IBRL vs public Internet leader-paced A/B (PoH placement and distance scaling), a SubscribeDeshred vs processed gRPC lifecycle race, and the initial 1-hour QUIC sender baseline. Every report links to raw evidence and an open harness.