Locations
EVIX is one switch fabric spread across 7 sites. Terminate your tunnel on whichever is closest to you; you land on the same peering LAN either way. Two of the sites are local-only extensions and do not accept tunnels.
| Site | Tunnels | Route server | Community | Connections |
|---|---|---|---|---|
| Fremont, US | Yes | AS137933 | 65517:1 | 53 |
| Amsterdam, NL | Yes | AS209762 | 65517:2 | 96 |
| Zurich, CH | Yes | — | 65517:5 | 23 |
| Toronto, CA | Yes | — | 65517:7 | 8 |
| New Zealand | Yes | — | 65517:3 | 5 |
| Frankfurt, DE | Local only | — | 65517:6 | 44 |
| Vancouver, CA | Local only | — | 65517:4 | 7 |
Every route the route servers learn is tagged with the community of the site it entered at, so you can tell where a prefix came in. See the community reference.
FMT
Fremont, California
Tunnel server and primary route server
- Tunnel endpoint IPv4
72.52.82.6- Tunnel endpoint IPv6
2602:fed2:fc0:c8::1
Our primary switch location, on the US west coast, with 1 Gbps of connectivity and direct peering to Hurricane Electric. It sits in Hurricane Electric's Fremont 2 facility, where physical cross-connects are possible. This is also where the AS137933 route server runs.
AMS
Amsterdam, Netherlands
Tunnel server and second route server
- Tunnel endpoint IPv4
93.158.213.143- Tunnel endpoint IPv6
2a00:1ca8:2a::75e
Our European hub, in the Kolo Data Centers DC1 facility (formerly Serverius) in Dronten, about 30 km from Amsterdam. The site has a 250 Mbps circuit and good onward peering into the rest of Europe, and hosts the AS209762 route server.
If you have a presence in the Amsterdam area, a local cross-connect is possible instead of a tunnel, including at the Nikhef and Qupra facilities. A VLAN or layer-2 transit hand-off also works. Pick the Local connection type when you apply.
ZUR
Zurich, Switzerland
Tunnel server
- Tunnel endpoint IPv4
193.148.250.34- Tunnel endpoint IPv6
2a0c:9a40:1050::34
Hosted by iFog, who also offer VPSs here that can reach EVIX locally rather than through a tunnel.
Connecting from an iFog VM? Ask iFog to add a dedicated EVIX interface to your VM, and configure your EVIX addresses on that new interface. Do not add EVIX to your existing FogIXP interface: that is iFog's own exchange LAN, and your traffic will never reach us.
TOR
Toronto, Canada
Tunnel server
- Tunnel endpoint IPv4
170.39.230.66- Tunnel endpoint IPv6
2602:fd50:101:74ab:3ece:8d38:ba87:b763
Thanks to Xenyth Cloud / GoCodeIT Inc, we have a site in the Equinix TR2 facility in Toronto. They offer VMs with local connectivity to EVIX as well.
NZ
New Zealand
Tunnel server
- Tunnel endpoint IPv4
163.47.131.155
Serves the Asia-Pacific region, with far better latency for regional peers than tunnelling to the US. A 1 Gbps circuit provides onward connectivity. This site is IPv4-only as a tunnel endpoint; your peering LAN addresses are of course still both IPv4 and IPv6.
FRA
Frankfurt, Germany
Local connections only
No tunnel endpoint here. Frankfurt is a layer-2 extension of our Amsterdam site. Networks with a VM or a port in the facility hand off locally and appear on the peering LAN via Amsterdam. Choose the Local connection type when you apply.
Hosted by iFog. This is our second-busiest site by connection count, almost entirely iFog customers.
Connecting from an iFog VM? Ask iFog to add a dedicated EVIX interface to your VM, and configure your EVIX addresses on that new interface. Adding EVIX to your existing FogIXP interface will silently fail: FogIXP is iFog's own exchange, on a different VLAN, and you will see no ARP or ND replies from us.
VAN
Vancouver, Canada
Local connections only
No tunnel endpoint here. Vancouver is a layer-2 extension of Fremont. Networks with a VM or a port in the facility hand off locally and appear on the peering LAN via Fremont. Choose the Local connection type when you apply.
Vancouver also hosts our core infrastructure: the provisioning database, this website, the helpdesk and the monitoring.