Latency Benchmarks

Measured, not marketed. The headline number below is computed live from production — we reconcile every detected launch against its on-chain confirmation, continuously — and the one-off comparisons are dated, sampled, and described down to their error bars.

Launch detection vs chain confirmation

Live · last 24h

Our pre-execution pipeline reconstructs pump.fun deploys from shred-level data before the validator has executed them. Every detection is stamped, then reconciled against the confirmed stream's arrival — so this head start is a continuously self-audited production metric, not a benchmark we ran once.

Median head start

294ms

before confirmation

p10

157ms

p90

431ms

Launches reconciled

29,373

last 24 hours

Head-to-head vs a specialist launch feed

Measured 2026-09-01

We raced our detection stream against a leading specialist pump.fun shred-feed provider (the class of feed sniper bots build on), live, on the same machine clock: their public WebSocket delivery vs our detection timestamp, per token.

Races won

91%

155 of 170 launches

Median lead

164ms

we delivered first

Internal overhead

1ms

detection → delivery bus, p50 (n=204)

Sample

170

consecutive live launches

Vs public aggregator APIs

Measured 2026-09-01

For freshly created tokens, we polled the most widely used public aggregator's token API every 3 seconds from the moment our pipeline detected each launch, until the token became visible there.

Median lead

~61s

until aggregator visibility

Fastest aggregator case

+30s

slowest +63s (±3s sampling)

Sample

consecutive launches, zero misses

API serving latency

Live · last 24h

Probed every 5 minutes from an independent server at a different provider, over the public internet, with a real API key — the customer path, not localhost.

REST p50

108ms

authenticated request

REST p95

227ms

WebSocket p50

80ms

connect + first frame

WebSocket p95

162ms

Methodology & honest limits

Head start— detection timestamp (pre-execution shred pipeline) vs the confirmed gRPC stream's arrival for the same mint, reconciled in production for every deploy. Slot times changed to ~300ms in September 2026; the metric reflects whatever the network does today.
Specialist race — both feeds timestamped on the same machine; their figure includes their network hop to our measurement box, ours includes our full pipeline to the delivery bus. One session, 170 consecutive launches, no exclusions.
Aggregator comparison — measures their public API visibility (what a user or agent can query), not their internal pipeline, with ±3s polling granularity.
Serving latency — EU probe to EU servers; other continents add network round-trip. Event streams carry the same freshness regardless of subscriber location.
Where the speed lives: the pre-confirmation class is delivered on thesniper:deploysWebSocket channel and webhooks; REST endpoints serve confirmed, committed state.

Read the docs Licensing & embeds Live status & verification Data integrity

Methodology & honest limits

Head start— detection timestamp (pre-execution shred pipeline) vs the confirmed gRPC stream's arrival for the same mint, reconciled in production for every deploy. Slot times changed to ~300ms in September 2026; the metric reflects whatever the network does today.

Specialist race — both feeds timestamped on the same machine; their figure includes their network hop to our measurement box, ours includes our full pipeline to the delivery bus. One session, 170 consecutive launches, no exclusions.

Aggregator comparison — measures their public API visibility (what a user or agent can query), not their internal pipeline, with ±3s polling granularity.

Serving latency — EU probe to EU servers; other continents add network round-trip. Event streams carry the same freshness regardless of subscriber location.

Where the speed lives: the pre-confirmation class is delivered on thesniper:deploysWebSocket channel and webhooks; REST endpoints serve confirmed, committed state.