TahoeIX - Tahoe Internet Exchange - AS63212

The Tahoe Internet Exchange is a cooperative effort to foster community and regional cooperation. TahoeIX is the first exchange in Northern Nevada. Our mission is to make a positive impact on our local (and regional) internetworking community. We keep traffic local.


Follow us on Twitter @TahoeIX

Why Join TahoeIX?

The Tahoe Internet Exchange connects participants to increase performance, enhance reliability, and keep traffic local to Northern Nevada.

As more networks join TahoeIX the stronger our Northern Nevada internet community becomes. All types and sizes of peers are welcome.

If you'd like to join TahoeIX please email: info < at > tahoeix < dot > org

Thank you to our supporters and advisors:

We would like to extend a special thanks to the following participants since you can't start an exchange without anyone to exchange with.


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.

  1. Peering is bilateral with the exception of route servers. There is no MLPA.
  2. BGP4 (or its successor) is used for peering and peers must set NEXT_HOP_SELF if advertising routes from other TahoeIX participants.
  3. Participants may not point default or statically route.
  4. Participants may not use another participant's resources without permission.
  5. Broadcast traffic may not be delivered to the exchange except as needed for normal operation and troubleshooting.
  6. Participants may not sniff traffic between other participants.
  7. 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.
  8. Participants must make valid contact information and relevant documentation available at all times.
  9. 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 particpating peers may require a PeeringDB entry.

How to Join TahoeIX

Joining TahoeIX and participating in regional peering is easy! Since we're a small, close-knit region we encourage using the TahoeIX route server to get started quickly. If there are any extra-valuable peers on the IX fabric you should contact them directly to establish a direct peering in addition to the route servers. However, some large peers only support peering through the route servers to reduce their admin overhead. The TahoeIX route servers also handle looking glass duties: RS1 is required while RS2 is optional but highly recommended for diversity.

First, review the rules and contact if us if you have questions. Second, you'll need to arrange a transport connection. The TahoeIX switch is in a neutral location next to fiber from AT&T, Verizon Business, and Charter Communications. Transport may also be available through other TahoeIX participants via cross connects (see the "connect" tab for a list). TahoeIX itself is currently supported by donations and sponsors without connection fees.

Once you have your transport contact us at info < at > tahoeix < dot > org for IP address assignments on the peering fabric. We'll need your AS number and points of contact. We also need to know what handoff your transport provider will be delivering: copper, multimode fiber, or singlemode fiber. If you can donate a Cisco SFP or fiber jumper to help build your connection we do appreciate it.

Important (after Dec 2015): Cross connects to the MMR may only be available as single-mode fiber. Copper cross connects may be available as EoMPLS from a participating peer.

Next we'll build your port, configure the route servers, and add you to the website. Once your transport is delivered we'll cross connect you to the TahoeIX fabric switch. The route server sessions are required since they double as our looking glass, but BGP communities are available if there's someone you really need to suppress route announcements to (but we encourage you to advertise to all).

Once you turn up your BGP to the route servers other participants will see your routes and peering traffic will begin to flow. The looking glass can be used to troubleshoot. Welcome to TahoeIX!

If you'd like to join TahoeIX please email: info < at > tahoeix < dot > org

To join TahoeIX you will need a BGP-capable router, an autonomous system number, and a connection to the peering fabric. Any carrier present in the TahoeIX MMR can connect you to the peering fabric. Network operators of all sizes are welcome. If you don't currently run BGP please contact us to see if we can help.

We are using BIRD for our BGP route servers. Looking glass: tahoeix.org/lg

Peer or Name AS IPv4 IPv6 Notes
TahoeIX Route Server #1 63212 2001:504:3F::2/64 Required, see "notes" below.
TahoeIX Route Server #2 63212 2001:504:3F::3/64 Optional, but recommended.
Roller Network 11170 2001:504:3F::2BA2/64 Colocation Datacenter
High Desert Internet Services 32614 2001:504:3F::7F66/64 Internet Service Provider
Verisign 26415 2001:504:3F::672F/64 Global Registry Services
J-Root Operator, .COM/.NET Resolution
Packet Clearing House 3856 2001:504:3F::F10/64 PCH Research
WoodyNet 42 2001:504:3F::2A/64 PCH DNS Anycast
Akamai Technologies 20940 2001:504:3F::51CC/64 Content Delivery Network
AS112 Project 112 2001:504:3F::70/64 as112.rollernet.us
RIPE NCC 25152 2001:504:3F::6240/64 K-Root Operator
Internet Systems Consortium 395217 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.

Prefixes for L-Root AS20144 are available to IX participants through AS11170.

In Provisioning

Peer or Name AS IPv4 IPv6 Notes
Avant Wireless 22415   Internet Service Provider
Washoe County 15304   Government

BGP Communities

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. Peers that do not wish to participate on the route servers are still required to use the looking glass function, but should tag their routes appropriately.

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)
IPv4 Month

IPv6 Networks (RS1)
IPv6 Month

Daily Traffic Summary (every 5 minutes)
Traffic Day

Weekly Traffic Summary (30 Minute Average)
Traffic Week

Monthly Traffic Summary (2 Hour Average)
Traffic Month

Yearly Traffic Summary (1 Day Average)
Traffic Year

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)

Postal and Shipping

Tahoe Internet Exchange
C/O Roller Network LLC
3545 Airway Dr. Suite 114
Reno, NV 89511

Please contact us first before shipping hardware.