The real backbone behind GoTokens' Low-Latency Cloud — which nodes carry compute, which carry bandwidth, which are joined by dedicated lines, and how they connect across the globe.
Coverage note. Node inventory and dedicated-line topology are drawn from live order records and internal network diagrams. Rack-space (colocation) capability and a handful of planned-but-unconfirmed routes are not yet reflected — they'll be added as that data is finalized.
Toggle a capability to highlight nodes that support it. Hover any node for details — labeled dots are regional hubs by connection count.
Computed live over the current dedicated-line network with Dijkstra's shortest-path algorithm — the same links listed below, chained end to end. When a segment has multiple measured values, the best one is used.
A curated set of distinctive end-to-end routes — some single-hop, some composed across the backbone.
Search a city to see every dedicated-line route through it. Multiple figures on one route reflect multiple physical circuits.
| From | To | Latency (ms) |
|---|
Drawn from live order records. A node can support any combination of compute, bandwidth and dedicated-line connectivity.
| Node | VM | IPT | Dedicated Line | Connections |
|---|