ixreport

Voxtelesys

AS400011 · 4k11.tel

Voxtelesys LLC

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Network ServicesType
OpenPeering policy
4Using the route servers
3Facilities in PeeringDB

Tools: Where can I peer with Voxtelesys? · Where should Voxtelesys peer next? · Compare Voxtelesys with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list

Nothing to fix: Voxtelesys's PeeringDB record matches the member lists of the 4 exchanges we could compare.

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where Voxtelesys's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 40G across 4 exchanges.

United States MegaIX Ashburn Ashburn, United States 206.53.170.64 2606:a980:0:3::40 10G Yes Both
United States MegaIX Dallas Dallas, United States 206.53.174.26 2606:a980:0:7::1a 10G Yes Both
United States MegaIX Los Angeles Los Angeles, United States 206.53.172.36 2606:a980:0:5::24 10G Yes Both
Canada MegaIX Toronto Toronto, Canada 206.53.203.21 2606:a980:0:8::15 10G Yes Both

Exchanges in its buildings that it isn't on (3)

These exchanges have a switch in a facility where Voxtelesys lists itself in PeeringDB, but don't have Voxtelesys as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

United States PIT-IXPittsburgh, United States 45 DataBank Pittsburgh (PIT1)
United States GraniteIXSalt Lake City, UT, United States 23 DataBank Salt Lake City (SLC2)
United States Mountain West Internet ExchangeSalt Lake City, United States 11 DataBank Salt Lake City (SLC2)
Facilities (3)

The buildings Voxtelesys lists in PeeringDB, and how many of the exchanges in each it's on.

United States DataBank Salt Lake City (SLC2)Bluffdale 0 of 2
United States DataBank Dallas (DFW3)Plano 1 of 1
United States DataBank Pittsburgh (PIT1)Pittsburgh 0 of 1