NO. 21ATLASCUSTOMER STORYRIFTBORN GAMES
Riftborn shipped a worldwide launch without a queue.
They rebuilt their realtime netcode on the Arc mesh and took a flagship multiplayer title from a fragile three-region rollout to a single, simultaneous global launch. Players felt the signal — not the seams.
- R-01PEAK
+318%
concurrent playerspeak at global launch — zero queue formed - R-02p99
11ms
p99 net tickdown from 74ms on the legacy regional mesh - R-0390d
0
rollback incidentsacross the first 90 launch-window days - R-04T+0
6wk
to first matchkickoff to shipping authoritative netcode
The problem
02 / SIGNAL DIAGNOSTIC
The mesh worked in three regions. It would not survive one launch.
A soft launch is forgiving. A worldwide simultaneous release is not — it meant 10× the concurrency, every region failing in its own dialect, and not one place to watch a player’s input actually travel.
Riftborn’s previous architecture stitched together regional brokers with hand-tuned routing. It held for a soft launch in three territories, but the math broke at scale: a 74ms p99 net tick is enough to turn a clean headshot into a support ticket, and the queue formed the moment two regions crested at once.
Worse, every region had its own failure mode and no shared timeline. There was no single view of how a packet propagated from client input to authoritative tick — so every incident opened the same way: an hour of engineers guessing where the signal stalled before anyone could fix why.
- +0msclient input
- +22msregional broker
- +?relay (unwatched)
- +?relay (unwatched)
- 74msauthoritative tick
Two relays added latency no dashboard was watching. The path was a guess, not a readout.
The solution / signal path
One signal axis, predicted forward and reconciled on the crest.
No new regions, no new brokers. We collapsed the patchwork into a single deterministic path, instrumented every hop, and rehearsed the launch until the wavefront held under load on its own.
Mapped the signal path
We traced every packet from client input to authoritative tick and found three relays adding latency no one was watching. The lattice made the propagation legible.
Re-routed the mesh
A deterministic rollback layer replaced the patchwork of regional brokers. Player state now travels one diagonal — predict forward, reconcile on the crest, never on the player.
Shipped under load
We launched into a worldwide simultaneous release with synthetic traffic shadowing real demand. The wavefront held; the queue never formed.
The proof — before / after
The wavefront arrives. The numbers light up with it.
Same title, same launch window, same player demand. One column is the legacy regional mesh on its last good day. The other is the Arc mesh under a worldwide simultaneous release. Watch the signal cross the gutter.
queuesplayers parked behind a spinner at launch
queue+318% concurrent players, nobody waited
Riftborn Games · flagship multiplayer · launch window 2026-03-14 → 2026-06-12 · 2.4M day-one sessions
We watched the wavefront hold under a load we used to fear. Launch night, the dashboards just sat there flat and green — and for the first time in my career, that was the entire point.
- peak concurrency
- 2.4M
- rollbacks
- 0
By the numbers · end to end
The arc, complete.
One signal, propagated from the first packet to the last region. The figures that survived launch night — measured, not promised.
- 2.4M
- 99.99%
- −71%
SIGNAL PROPAGATED — END TO END2.4M · 99.99% · −71%
Your launch, next
See what the Arc mesh does under your peak.
Bring your concurrency targets and your worst launch-night story. We map your signal path on a live mesh and show you the wavefront under synthetic peak — before you commit a single region.
- Session
- 45 min
- Live mesh
- your load
- Deliverable
- signal map