Solana, right now
How to be faster on Solana?
If you build on Solana, you’ve said one of these.
Same strategy as the next desk — only my bot fills late.
The price prints. I send. My transaction doesn’t make it.
I’ve swapped every RPC provider — and nothing changes.
What professional tuning
You’ve tuned the code. You’ve upgraded the box. Neither is the bottleneck — you’re chasing a leader that won’t stop moving, from too far away.
Hardware and code alone won’t win the slot. You win it on timing and location.
Speed you can buy. Understanding is the edge.
See how you get there first
The moving target
The fastest place to be never sits still.
Every slot — Solana’s ~400 ms turn to build a block — a different validator becomes the leader, and whoever sits closest to it wins.
Unlike a fixed spot you can camp next to once, on Solana the fastest seat is never the same one twice.
~400 ms · a new leader every slot
The fastest seat, slot by slot
The leader rotates around the world, slot by slot. Win one, and the next is already somewhere else.
Watch it move
Enhanced Solana RPC, Geyser gRPC & Shredstream
Epoch —
— countries
Leader
—
Live block producer
Distance is latency
Cross a continent, and you fall 100–300 ms behind.
Light through fiber and a stack of routers sets a floor no hardware can beat. Same rack is about 0.1 ms. Across an ocean it’s 100–300 ms — and a slot only lasts about 400 ms.
So when the leader is on your doorstep you’re inside the window — and when it’s a hemisphere away, you’ve already missed it. Being fast for every slot means being near wherever the leader lands.
Round-trip floor by distance · the physics, not a benchmark
What distance costs a packet
- Same network
- 0.1 ms
- Same datacenter
- 0.3 ms
- Same city
- 1 ms
- Neighboring country
- 5–10 ms
- Cross-continent
- 100–300 ms
A continent away is hundreds of times a same-rack hop — and more than a whole slot. Proximity isn’t a tweak; it’s the budget.
Coverage — why one city isn’t enough
The most crowded city is still only about a quarter of the network.
Frankfurt is where operators pile in — yet even the busiest city holds only about a quarter of the network, by validators and by stake alike. For most slots the live leader is somewhere else.
Covering everywhere is the ideal; budgets force a choice. So the question isn’t only who is biggest, but who has the fewest machines crowded into it — the least contested. Amsterdam carries comparable stake to Frankfurt with far fewer validators packed in — often the quieter, better seat.
Where Solana’s validators sit
Coverage — a node already next to every leader
Wherever the leader lands, a strong, Solana-direct node is already there.
The leader role circles the globe slot by slot — so the node that wins is the one already closest to it. A node in the same region skips the long-haul hop that adds the lag.
So we don’t lean on one place. Steady speed means being close on every slot — and because the leader keeps moving region to region, that takes coverage across regions. We run validator-grade nodes where Solana’s stake concentrates, on one low-latency fabric, and we keep adding regions — every new region is more slots where you’re already beside the leader.
Global Data Center Partner
Speed is determined by distance to Solana.
The region matters. But a city name alone is not a network path. Even in the same city, external transit and extra hops can add latency. ERPC selects data centers close to Solana servers, then keeps routes short with no external transit and sustained turbo boost.
ERPC premium route
no external transit
minimum RTT
City-name selection
external transit / 7 hops
70x slower
- 01Same data centerChoose the region first, then the data center closest to Solana.
- 02No external transitAvoid external AS paths to keep RTT and jitter tight.
- 03Full throttleERPC excludes power-saving profiles and keeps resources in sustained turbo boost.
Stake-weighted priority (SWQoS)
If your transactions keep failing, you’re stuck in the spam lane.
Solana’s leaders split priority bandwidth in two. Connections backed by stake — SOL committed to a validator — get 80% of it. Everyone else fights over the other 20% — the lane that’s packed with spam.
Firing straight at the leader feels like the fast move — but with no stake, that’s the crowded 20% lane, and under load your transaction never makes the block.
So the real answer is a staked validator. We run a top-tier one wired into high-quality RPC lines — hardware placed right next to Solana — so your transactions get through the wide lane.
A top-tier validator in our Shinobi Performance Pool
How Solana’s leaders split priority bandwidth
Stake rides the wide 80% lane into the validator — before any fee. No stake, you’re crammed in the 20% spam lane.
80 / 20 split set by Solana’s leaders, not by us
Measured benchmark
Same-class machine. Not the same speed.
AMD Turin, 4 vCPU, Amsterdam, Ubuntu 24.04 — the same on both boxes, one major cloud and ours. The spec sheet says they’re equals. The bench says otherwise.
Same silicon. The gap is our tuning — the box dialed in and seated right next to Solana.
node_bench · same run, same region
ERPC vs a major cloud · same spec
- CPU computesysbench · 4 threads · higher is better
- more CPU throughput1.9×
- Memory bandwidthSTREAM Triad · 4 GiB · higher is better
- more memory bandwidth3.2×
- Disk IOPSfio · 4K randread · QD32 · higher is better
- more disk IOPS16.6×
- Disk latency · p99fio · 4K randread · QD32 · lower is better
- faster at the tail25.7×
events/s
MB/s
IOPS
µs
The whole environment, at the highest grade.
ERPC tunes every layer between you and the slot — RPC, streaming, validators, the bare metal underneath — and seats it all next to Solana. Pulling that together used to be your job. Now you just combine our products — the fastest line to Solana.