The Tahoe Internet Exchange is a cooperative effort to foster community and regional routing. TahoeIX is the first exchange in Northern Nevada. Our mission is to make a positive impact on our local internetworking community. We help keep traffic local.
Follow us on Twitter @TahoeIX
- Welcome to our newest peer: Internet Systems Consortium AS395217
Why Join TahoeIX?
The Tahoe Internet Exchange connects participants to increase performance, enhance reliability, and keep traffic local to Northern Nevada.
- Adds routing diversity and lowers latency.
- Access to critical infrastructure (i.e. anycast DNS).
- Access to content (i.e. CDN and colocation peers).
- Access to consumers (i.e. internet service providers).
- Reduces dependence on transit "internet" ports.
- Keeps local traffic local without depending on out of state networks.
- Good neighbor services (i.e. the AS112 Project).
As TahoeIX grows the stronger our Northern Nevada internet community becomes. All types and sizes of peers are welcome to join.
Thank you to our supporters and advisors:
- The group of inital network operators that made starting an exchange possible.
- Matt at SFMIX for advice to help us get started (and ongoing), the domain names, and a Cisco 3750G-12S for the core peering fabric.
- Seth at Roller Network for kickstarting the IX with funding and resources.
- Roller Network for donating a Xen VM, mail and DNS services, plus sponsoring infrastructure resources.
- Akamai Technologies for reaching out to us to place CDN nodes, our first major content peer.
- Packet Clearing House and Cisco for donating a Nexus 3548P-10G.
- SFMIX for donating a Nexus 3548P-10G for an extension location (in planning).
We would like to extend a special thanks to the following participants since you can't start an exchange without anyone to exchange with.
- Roller Network (AS11170) Since October 2014
- High Desert Internet Services (AS32614) Since October 2014
- Packet Clearing House (AS42 and AS3856) Since February 2015
- Akamai Technologies (AS20940) Since June 2015
- Avant Wireless (AS22415) Pending
- June 2016
- Internet Systems Consortium joins peering with F-Root AS395217
- Peering traffic peaks just shy of 300Mbps for the first time
- September 2015
- RIPE joins peering with K-Root AS25152
- July 2015
- Akamai starts passing traffic; daily traffic peaks reach 100Mbps.
- June 2015
- Akamai AS20940 establishes peering.
- April 2015
- An AS112 Project server establishes peering.
- Added prefixes for L-Root AS20144 via Roller Network AS11170.
- March 2015
- Verisign AS26415 establishes peering.
- February 2015
- Packet Clearing House AS42 and AS3856 establishes peering.
- January 2015
- Started graphing summary traffic data.
- Started graphing IPv4 and IPv6 networks on the exchange.
- October 2014
- First two peers (Roller Network AS11170 and High Desert Internet AS32614) establish BGP sessions.
- Traffic is exchanged through TahoeIX!
- September 2014
- ARIN assigns AS63212, 184.108.40.206/24, and 2001:504:3F::/48 to TahoeIX.
- TahoeIX is founded.
Participants are encouraged to use the route server to openly peer with all participants - which is core of joining an exchange. Participants may still choose to peer bilaterally with important peers. The value of the exchange is greatly enhanced with open peering. TahoeIX should not be used for a participant's internal traffic.
Anyone is welcome to join the TahoeIX and participate in peering. There is no minimum prefix size on the exchange, although individual peers may have a minimum prefix length at their discretion. Both IPv4 and IPv6 is supported. TahoeIX does not have a membership fee. The exchange is supported by sponsors and donations.
- Peering is bilateral with the exception of route servers. There is no MLPA.
- BGP4 (or its successor) is used for peering and peers must set NEXT_HOP_SELF if advertising routes from other TahoeIX participants.
- Participants may not point default or statically route.
- Participants may not use another participant's resources without permission.
- Broadcast traffic may not be delivered to the exchange except as needed for normal operation and troubleshooting.
- Participants may not sniff traffic between other participants.
- Participants may only utilize a single layer-2 MAC address to place a single layer-3 router per port allocated from the TahoeIX switch fabric unless by prior agreement.
- Participants must make valid contact information and relevant documentation available at all times.
- No exchange participant may harm the exchange or other participants.
Participants are encouraged to create a PeeringDB entry for their AS if they don't already have one, however it is not mandatory for peering. Some participating peers may require a PeeringDB entry.
Because we are a small regional IX, closed or selective peering policies with minimum requirements are not recommended. We ask that peers with such policies at larger exchanges to make an exception at TahoeIX.
A BGP session to Route Server #1 is required for the looking glass. If you do not wish to use route servers for peering please tag your routes with the appropriate community. A connection to Route Server #2 is optional.
The following communities are processed by the route server, but are not propagated to peers.
|Standard Community||Extended Community|
|0:peer-as||So:0:peer-as||Do not advertise to peer-as|
|63212:peer-as||So:63212:peer-as||Advertise to peer-as|
|0:63212||So:0:63212||Do not advertise to any peer|
The default behavior is to advertise to all peers.
How to Join TahoeIX
To join TahoeIX please send the following information to info < at > tahoeix < dot > org :
Public Information (for the website) AS Number: Organization Name: Organization URL: Description: Private Information (for provisioning and contact) Router MAC Address: Tech Name: Tech Email: Tech Phone: NOC Phone: NOC Email: Peering Email: IPv6: yes/no
- Description should be brief like "Internet Service Provider" or "Global Registry Services".
- IP addresses will be assigned to you and added to the website.
- Private information will only be available to TahoeIX and other peers.
- MAC address will not be shared with other peers.
Several regional and national carriers can provide transport services to the IX fabric with infrastructure present at our locations. Transport may also be available through other TahoeIX participants. This list is for informational purposes only - TahoeIX does not endorse any particular option.
- Level 3
- Verizon Business
- Spectrum Business (formerly Charter Communications)
|Peer or Name||AS||IPv4||IPv6||Notes|
|TahoeIX Route Server #1||63212||220.127.116.11||2001:504:3F::2/64||Required, see "notes" below.|
|TahoeIX Route Server #2||63212||18.104.22.168||2001:504:3F::3/64||Optional, but recommended.|
|Roller Network||11170||22.214.171.124||2001:504:3F::2BA2/64||Colocation Datacenter|
|High Desert Internet Services||32614||126.96.36.199||2001:504:3F::7F66/64||Internet Service Provider|
|Verisign||26415||188.8.131.52||2001:504:3F::672F/64||Global Registry ServicesJ-Root Operator, .COM/.NET Resolution|
|Packet Clearing House||3856||184.108.40.206||2001:504:3F::F10/64||PCH Research|
|WoodyNet||42||220.127.116.11||2001:504:3F::2A/64||PCH DNS Anycast|
|Akamai Technologies||20940||18.104.22.168||2001:504:3F::51CC/64||Content Delivery Network|
|RIPE NCC||25152||22.214.171.124||2001:504:3F::6240/64||K-Root Operator|
|Internet Systems Consortium||395217||126.96.36.199||2001:504:3F::6:7D1/64||F-Root, Anycast Services|
Route server #1 is required because it doubles as the looking glass. If your AS doesn't participate on route servers please tag your announcement to the route server/looking glass on AS63212 appropriately (see BGP communities below) or we can configure a filter on request.
Prefixes for L-Root AS20144 are available to IX participants through AS11170.
|Peer or Name||AS||IPv4||IPv6||Notes|
|Avant Wireless||22415||188.8.131.52||Internet Service Provider|
DNS Geolocation Note
Some peers will use DNS geolocation to determine if their content will be served from peered resources on TahoeIX. Your DNS resolver will need to geolocate to the Reno/Sparks/Carson City and nearby areas for best results.
IPv4 Networks (RS1)
IPv6 Networks (RS1)
Daily Traffic Summary (every 5 minutes)
Weekly Traffic Summary (30 Minute Average)
Monthly Traffic Summary (2 Hour Average)
Yearly Traffic Summary (1 Day Average)
Green/Blue: Incoming/Outgoing Traffic Dark Green/Magenta: Maximal 5 Minute Incoming/Outgoing Traffic
info < at > tahoeix < dot > org
+1 775 525 2539 (voicemail only)
We will be notified of your message and return your call as soon as possible.
Postal and Shipping
Tahoe Internet ExchangeC/O Roller Network LLC3545 Airway Dr. Suite 114Reno, NV 89511
Please contact us first before shipping hardware.
TahoeIX currently consists of two core switches: a Cisco 3750G-12S and a Nexus 3548P-10G connected with a 1Gbps inter-switch link. We are slowly migrating peers off of the 3750G (our first switch) and onto the 3548P donated by PCH. Once complete, the 3750G will be removed from service at the core.
Two route servers are avaiable: Route Server #1 is a virtual machine and Route Server #2 is a physical server.
Extensions are managed by TahoeIX, but may run oversubscribed transport links back to the TahoeIX core depending on their physical location and may have a cost to connect. Contact us for more information.