Reaction time · real-time multimodal AI and transport

The first byte is the product.

Voice agents, models, robots and live media all wait for the same thing: the first byte of the answer. We build the engine and the network that make it leave sooner.

→ In sprinting, a start under 100 ms is ruled a false start: no human reacts that fast. Our robot control step, camera in to action out, is 82 ms at p99.9.

·· ms Your first byte · this page, measured by your browser just now
53 msFirst audio byte · Qwen3-TTS 1.7B · one RTX A5000 · p50
82 msRobot control step · camera in, action out · p99.9
7.7 msRelay round trip · same metro · p99.9
§1 · four first bytes

One product, measured four ways.

The wait has the same shape everywhere. Only the position of the first byte moves.

01 / VOICE
WAITFIRST BYTE

First audio byte in 53 ms

Qwen3-TTS 1.7B starts to speak 53 ms after the request, on one RTX A5000.

p50 · p95 76 msSpeech to text 42 ms
02 / INFERENCE
WAITFIRST BYTE

Frontier models, served

Open mixture-of-experts models from DeepSeek, Qwen and Mistral, on our own engine and RTX PRO 6000 cards.

Open MoE modelsRTX PRO 6000
03 / ROBOTICS
WAITFIRST BYTE

First action in 82 ms

Camera frames in, π0.5 action chunk out, Noida to our Mumbai relay and back.

p99.920,000 steps · 0 failures
04 / RELAY
FIRST BYTE

First object in 7.7 ms

Robot to relay to responder and back, inside one metro. No head-of-line blocking between streams.

p99.9 · p50 4.6 msMoQ over QUIC
§2 · scroll is time

Everything happens before the first byte.

050100150
  1. 000 msCaller stops speakingt = 0
  2. 042 msFinal transcriptParakeet TDT 0.6B v3 · one H100 · p50 42 ms, p95 62 ms
  3. 111 msFirst token3B model on our engine with a shared task prompt · p50 69 ms
  4. 164 msFirst audio byteQwen3-TTS 1.7B · one RTX A5000 · p50 53 ms, p95 76 ms

Three p50 values from three separate runs, added together. It is a chain of parts, not one measured call. The phone network is not included.

§3 · measured from where you are

Your round trip, right now.

Your browser just timed our relays. The hatched bar is the physics floor from your city. Nobody beats it; the job is to get close.

Round trip to each relay···
Mumbairelay.firstbyte.fast···
Frankfurtrelay-fra.firstbyte.fast···
Londonrelay-lon.firstbyte.fast···
New Yorkrelay-us.firstbyte.fast···
0255075100
Milliseconds · solid = measured by you, best of 4 · hatched = straight-line fiber floor
§4 · iso-latency

Lines of equal wait.

Each contour joins places with the same round-trip floor to the nearest relay. Drop a pin anywhere to read the physics.

20 ms40 ms80 msTokyoSingaporeSydneyManilaDubaiNairobiLagosJohannesburgSão PauloMexico CitySan FranciscoChicagoDelhiSeoulMUMBAIFRANKFURTLONDONNEW YORK
Pin···
Nearest relay···
Distance···
Round-trip floor···

Floor, not a promise: straight-line fiber at ~204 km per ms. Real cables bend, so a real round trip is always higher. Click the map or use the arrow keys.

§5 · the literal byte

This is a first byte.

One packet of a voice call, field by field. Hover a field to read it.

On the wire · QUIC short header
After decryption · STREAM frame + MoQT object
Wire · 1 byte

The first byte

0x43 = 0100 0011. Header form 0: a short header, used once the connection is up. Fixed bit 1. Spin bit 0. Key phase 0. The last two bits say the packet number is 4 bytes long. Shown after header protection is removed.

An example packet built by hand for this page. Field layout follows QUIC (RFC 9000) and the MoQT draft we run.

Send us your slowest first byte.

Tell us the route, the model and the percentile you care about. We measure it on our stack and send you the numbers with the method.