Network · SEA1 · AS13725
Every hop to your server.
Published.
Tier-1 carriers into Lumen Seattle 1, a redundant 40G spine, and 10G uplinks to every node we own. We run AS13725 and we draw the route.
AS13725Our autonomous system, listed on PeeringDB
SEA1Lumen Seattle 1, 1000 Denny Way
40GRedundant spine between the carriers and your node
10GUplinks to every node
2023Owned racks in the Pacific Northwest since then
The route
From a visitor's router to your server, over a 40G spine.
Direct Tier-1 peering, a redundant spine, and racks we own end to end. No mystery hops. Built for Pacific Northwest latency.
Peering and transit
Lumen and Zayo carry it in. We take it from there.
Two carriers, one exchange in the same building, and a spine with no single point of failure.
- TransitDirect peering with Lumen, and Zayo transit. Two independent ways out of the building.
- ExchangeThe facility has 100G into the Seattle Internet Exchange, so regional traffic has a local path.
- SpineA redundant 40G spine, with 10G uplinks to every node.
- Power behind itA+B feeds and N+1 UPS behind every rack. The datacenter page has the facility numbers.
- RegistryAS13725 on PeeringDB, the public record of our network.
Check it
Run the test from your own server.
Three commands, no account needed. The numbers you get are the numbers we publish.
- The path
traceroute your.server.ipfrom your side. You will see your provider, a Tier-1 carrier, then our spine and your node. - Throughput
curl -sL https://yabs.sh | bashon the server runs iperf3 to public endpoints in both directions. The YABS guide reads the output with you. - Headroom
vmstat 1 10shows steal time in the last column. Single digits under load means the 60% cap is holding. - StatusLive status and incident history at status.nobullnetworks.com. Credits for a miss are on Receipts.
