We know every cable.
Single floor, single peering room, single change calendar. When something breaks at 02:00, we don't escalate to a different timezone - we walk into the room.
Network
One floor, one rack room,
zero excuses.
We host out of a single Tier III facility in San Diego. That isn't a limitation - it's the whole point. We know every cable in the room, every transit provider on the door, every disk that holds your world. Have a look.
- powered & active
- cold spare, ready to provision
- network & transit
- power, cooling, BMC
01 / Philosophy
Why one region, on purpose.
Latency where it matters.
San Diego sits in the carrier-rich LA basin. Sub-10 ms to LA, ~25 ms to Seattle, ~65 ms to NYC. Most US-West players never feel a hop.
Capex into the box, not the map.
Two regions means half the budget per region. We'd rather put Gen4 NVMe in your rack than thumbtacks on a globe.
EU-West when - not if.
We'll open a second region the day the first one stops getting better. An Amsterdam pop is scoped on the roadmap.
02 / Latency
What the wire actually looks like.
Median RTT from san-1 to popular destinations, measured every 60 s from our edge probes. Updated nightly.
City
p50
p95
Los Angeles · US
5 ms
9 ms
Las Vegas · US
12 ms
18 ms
Seattle · US
25 ms
33 ms
Dallas · US
38 ms
46 ms
Chicago · US
52 ms
61 ms
New York · US
65 ms
74 ms
Mexico City · MX
58 ms
68 ms
Tokyo · JP
108 ms
122 ms
London · UK
142 ms
158 ms
> your location
--
--
Numbers above are RTT to san-1's edge, not in-game latency - your in-game tick budget is whatever the client adds on top.
03 / Transit & peering
The carriers on our door.
Blended IP transit plus selective peering at LAIX and Equinix LA1. If a path goes brown, we fail off it without your players noticing.
- Hurricane ElectricIPv4/IPv6 transit
- CogentIPv4 transit
- GTTIPv4 transit
- LumenIPv4/IPv6 transit
- LAIXpeering fabric
- Equinix LA1peering fabric
Your world belongs in this room.
Deploy on san-1 in under a minute - and watch it show up on the map.