Order to confirmation

Timed from order submit to the order appearing on the venue's own account feed, not to an acknowledgement of receipt: confirmation is the point the order is live in the book and can be filled.

Order → Confirmation

Updated

3-day windowLower is better

Each mark = one measured order20× slow motion

Order-to-confirmation latency by endpoint: median and number of measured orders.
EndpointMedian latencyOrders measured
Nado7.4ms mediann=4,292
Bullet (direct)7.7ms mediann=4,306
Lighter11.2ms mediann=4,317
Bullet (via Cloudflare)12.4ms mediann=4,288
Pacifica17.6ms mediann=4,320
Aster103ms mediann=4,316

Tail latency

Median To p99 To p99.9 Slowest order 100 ms
Endpointp99Slowest
  1. Nado146 ms612 msNado: median 7.4 ms, p99 146 ms, p99.9 397 ms, slowest 612 ms.
  2. Bullet (direct)59.4 ms128 msBullet (direct): median 7.7 ms, p99 59.4 ms, p99.9 94.1 ms, slowest 128 ms.
  3. Lighter384 ms1,380 msLighter: median 11.2 ms, p99 384 ms, p99.9 910 ms, slowest 1,380 ms.
  4. Bullet (via Cloudflare)94.2 ms1,587 msBullet (via Cloudflare): median 12.4 ms, p99 94.2 ms, p99.9 252 ms, slowest 1,587 ms.
  5. Pacifica36.4 ms74.3 msPacifica: median 17.6 ms, p99 36.4 ms, p99.9 51.5 ms, slowest 74.3 ms.
  6. Aster177 ms459 msAster: median 103 ms, p99 177 ms, p99.9 346 ms, slowest 459 ms.

Log scale. Lower is better.

Tail latency by endpoint: measured orders, median, 99th percentile, 99.9th percentile, slowest measured order, and the number of orders slower than 100, 250, 500 milliseconds.
EndpointOrdersp50p99p99.9SlowestOver 100 msOver 250 msOver 500 ms
Nado4,2927.4 ms146 ms397 ms612 ms245151
Bullet (direct)4,3067.7 ms59.4 ms94.1 ms128 ms200
Lighter4,31711.2 ms384 ms910 ms1,380 ms2009025
Bullet (via Cloudflare)4,28812.4 ms94.2 ms252 ms1,587 ms43132
Pacifica4,32017.6 ms36.4 ms51.5 ms74.3 ms000
Aster4,316103 ms177 ms346 ms459 ms2,433140

Quoting means cancelling: every time the price moves, the order resting at the old one has to go. Cancels carry the same tail as orders, so one cancel in a hundred takes at least your p99 to land. Until it lands, your stale quote is still resting where the fastest taker on the other side can lift it. That is latency arbitrage, and it is paid out of your PnL.

The length of each exposure is set by p99, not p50. The frequency is set by your quote rate. Per $1M quoted, one basis point of adverse selection is $100. At 100 orders a second you settle that bill once a second.

Window
72 hours to 2026-11-15 11:24 UTC · 25,839 orders · 6 endpoints
Timed
One interval per order: submit to account-feed confirmation. The cancel that follows is not in it, and neither is signing. No network-floor subtraction, no speed-bump adjustment.
Harness
One m8gd.2xlarge in ap-northeast-1d. One client, one clock, identical for every endpoint.
Orders
One order per measurement, one measurement a minute per endpoint, submitted singly and cancelled once it confirms. Post-only, so it rests or is rejected and never trades. Batch submissions are excluded.
Transport
One WebSocket per endpoint, held open across measurements. No order opens a connection, so no figure here includes a TCP or TLS handshake. What is timed is the venue and the round trip.
Endpoints
Bullet (direct) hits our trading API load balancer with nothing in front of it. Bullet (via Cloudflare) is the same engine behind Cloudflare, which is there to absorb abuse and charges latency and a good deal of jitter for it, so market makers take the direct path.
Volleys
A display grouping on the track. Orders do not arrive synchronised across venues.
Cancels
Measured separately by the same collector and not shown here: a long order tail means a long cancel tail.
Prior art
Inspired by Check the Chain's benchmark. Ours is written from scratch in Rust, so no garbage collector can pause the harness in the middle of a measurement.