Network
Twelve locations,
Twelve locations,
one hostname each.
Every edge node is addressable on its own hostname under vimovox.com. Zones normally resolve through anycast, but a per-node hostname is there when you need to pin, test or debug a single location.
| Node hostname | Location | Region | Uplink | State |
|---|---|---|---|---|
| lax1.vimovox.com | Los Angeles | US West | 10 Gbps | operational |
| sjc1.vimovox.com | San Jose | US West | 10 Gbps | operational |
| dfw1.vimovox.com | Dallas | US Central | 10 Gbps | operational |
| iad1.vimovox.com | Ashburn | US East | 10 Gbps | operational |
| ord1.vimovox.com | Chicago | US Central | 10 Gbps | operational |
| mia1.vimovox.com | Miami | US East | 10 Gbps | operational |
| lhr1.vimovox.com | London | Europe | 10 Gbps | operational |
| fra1.vimovox.com | Frankfurt | Europe | 10 Gbps | operational |
| ams1.vimovox.com | Amsterdam | Europe | 10 Gbps | operational |
| sin1.vimovox.com | Singapore | Asia Pacific | 10 Gbps | operational |
| nrt1.vimovox.com | Tokyo | Asia Pacific | 10 Gbps | operational |
| syd1.vimovox.com | Sydney | Asia Pacific | 10 Gbps | operational |
Why per-node hostnames
Anycast is convenient until something is wrong in exactly one city. A stable hostname per node lets you reproduce a problem from a specific location, warm a cache before a launch, or route a private origin pull deliberately.
Capacity and growth
Nodes are added by region as sustained traffic justifies them. New hostnames follow the same pattern, so an existing integration picks them up without a code change.