ixreport

Vox Telecom

AS11845 · Vox

7Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
6Using the route servers
1To fix in PeeringDB
5Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Vox Telecom's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on Vox Telecom's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Vox Telecom's PeeringDB record. Add one entry per connection with these values.

  1. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From its IX-F export and website members list

    The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

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

Map

Where Vox Telecom'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 1.2T, at the 6 of 7 exchanges with a speed in PeeringDB or the exchange's IX-F export.

South Africa CINX Cape Town, South Africa 196.223.22.21 2001:43f8:1f1::21 20G 123 routes Both
South Africa DINX Durban, South Africa 196.223.30.21 2001:43f8:1f2::21 10G 162 routes Both
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil Down Not in PeeringDB
South Africa JINX Johannesburg, South Africa 196.60.96.20
196.60.96.21
2001:43f8:1f0::20
2001:43f8:1f0::21
2 × 100G 508 routes Both
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.17
196.60.70.69
2001:43f8:6d1::17
2001:43f8:6d1::69
2 × 200G 512 routes Both
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.78
196.10.141.82
2001:43f8:6d2::78
2001:43f8:6d2::82
2 × 100G 322 routes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.146
196.60.8.214
2001:43f8:6d0::e
2001:43f8:6d0::214
2 × 200G 508 routes Both

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

These exchanges have a switch in a facility where Vox Telecom lists itself in PeeringDB, but don't have Vox Telecom 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.

Facilities (5)

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