An IX (Internet Exchange) allows networks to interconnect on an open-access ethernet fabric -- providing low-latency, high-bandwidth, cost-effectively, in a locale.
What is a Virtual Internet Exchange
A Virtual Internet Exchange simulates a real Internet Exchange Point using tunnels and virtulized switches. It has the advantage of allowing remote users with public resources to peer in a more automated manner.
Note that while traditional Internet Exchanges generally decrease latency and increase bandwidth, EVIX makes no such guarentee. In fact, EVIX may potentially increase latency (for example if 2 people on the East Coast need to send traffic to each other via our West Coast switch).
EVIX's primary purpose is for research and education, and should not be expected to increase Internet performance.
How is traffic exchanged?
EVIX uses OpenVPN, EoIP, ZeroTier or VXLAN tunnels to establish layer 2 connectivity and exchange IP and IPv6 data. As with any Internet Exchange peers use BGP to send routes to each other.
Where is EVIX?
Right now we have three POPs; our primary switch is in Fremont, California and we have extension switches in the Netherlands and New Zealand. We are planning additional sites to further reduce latency.
CIRALabs for the excellent IXP-Website template which is used as a base for this site.
Fremont, CA, US
Our primary virtual switch location is in Fremont, California on the US West Coast. This site has 1gbps of connectivity and direct peering to Hurricane Electric. The physical datacenter it is located in is Hurricane Electric's Fremont 2 DC
Location IP Address: 18.104.22.168
EVIX Fremont Daily Traffic Graph
Amsterdam, The Netherlands
We have an extension switch in the Serverius DC1 datacenter located in Dronten, about 30KM away from Amsterdam, in The Netherlands. This site is fed with a 250mbps circuit and has excellent peering into the rest of Europe.
Location IP Address: 22.214.171.124 (NL1)
EVIX Dronten Daily Traffic Graph
The Asia-Pacfic region is served by an EVIX extension switch in New Zealand, offering much better latency to regional peers then tunneling through the US. COnnectivity is provided by a 1gbps circuit to the Internet at large.
Location IP Address: 126.96.36.199
EVIX Auckland Daily Traffic Graph
Anyone is welcome to join EVIX. to start the process, please review our rules: FAQ and then fill out the contact form below (unless noted, all fields are required):
Once your application has been receivied, it will be evaluated and processed by one of our volunteer staff. When your application has been approved, you will be contacted by email to establish a peering session. Please whitelist 'email@example.com' in your mail client to avoid missing these important instructions.
If you need to contact us directly, please reach out to:
EVIX does not charge for participation as we believe in providing a low barrier of entry for any holders of public resources to participate in BGP. While we do not charge for participation, we do accept donations to cover the costs associated with running EVIX's infrastructure.
How do we donate to EVIX?
EVIX was built upon donations. We are very interested in receiving donations of VPS' to further extend the reach of our network. If you would be interested in donating resources to EVIX, please contact us by email:firstname.lastname@example.org We also accept monetary donations to our PayPal email address: email@example.com
What Technology is Used to Connect Peers?
EVIX has two types of peers - local and remote. Local peers have a Free Range Cloud VPS and have requested a complimentary cross connect to the EVIX switch.
Remote peers use a layer2 tunneling protocol to connect to the EVIX switch without a physical presence. Supported tunneling protocols are EoIP, OpenVPN, VXLAN and ZeroTier (Experimental).
All peers, local and remote, use BGP to exchange routing information with each other, and optionally, the EVIX route server.
Are there any rules?
The internet exchange switch is a fabric shared by all peers.
Peers must avoid doing anything which might overload the fabric,
mis-direct traffic, or otherwise cause harm to any other peers. If
a peer shows a willful disregard for others, they will be
disconnected by the operators.
Additionally, peers are requested to only send traffic
to destinations advertised by BGP.
Do not point default routes and do not point static routes
to other operators.
Peers are required to maintain their connection to the IXP and allow ICMP PING, additionally operators are required to maintain a peering session to the primary route server. Operators who do not maintain their tunnel, or who block ICMP PING will be automatically de-peered.
While not a rule, we request that peers register themselves
with http://peeringdb.com, because
visibility there will encourage other networks to join as well,
bringing more benefit to all.
What operating systems are supported?
Technically any OS that supports VPN tunneling (current protocols include OpenVPN, ZeroTier or VXLAN) and BGP or any version of Mikrotik RouterOS can be used. We have officially tested on Debian, VyOS 1.18 and RouterOS 6
Are there any example configurations?
Yes! We have example configuration instructions available at: example-config.pdf Send us an email if you would like to add to this document!
What Subnets do you use?
Our IPv6 subnet is 2602:fed2:fff:ffff::/64 which has been donated by 10VPN Hosting, while our IPv4 subnet is 188.8.131.52/24 and has been acquired directly from ARIN
What is the process for getting connected?
Please fill out the peering request form on our contact page and one of our staff will get in touch.