ixreport

Vtal 8167

AS8167 · BrasilTelecom/Telemar/Pegasus/Vtal

Vtal

6Exchanges
3On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
3Using the route servers
3To fix in PeeringDB
2Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

3 things to fix in Vtal 8167's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-11-19 12:40 UTC.

Make the changes on Vtal 8167'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 (3)

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

  1. Brazil IX.br (PTT.br) Londrina Londrina/PR, Brazil · PeeringDB 314From its IX-F export

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

  2. Brazil IX.br (PTT.br) Manaus Manaus/AM, Brazil · PeeringDB 707From 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.

  3. 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

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

Map

Where Vtal 8167'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

Brazil IX.br (PTT.br) Brasília Brasília/DF, Brazil 45.184.144.181 2001:12f8:0:13::181 Up, 0 routes Both
Brazil IX.br (PTT.br) Curitiba Curitiba, Brazil 45.184.146.28 2001:12f8:0:4::28 Up, 0 routes Both
Brazil IX.br (PTT.br) Londrina Londrina/PR, Brazil Not in PeeringDB
Brazil IX.br (PTT.br) Manaus Manaus/AM, Brazil Not in PeeringDB
Brazil IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil 177.52.38.6 2001:12f8:0:6::8167 Up, 0 routes Both
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil Not in PeeringDB

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

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

Bulgaria NetIXSofia, Bulgaria 204 BR.Digital Curitiba (CTA1)
Facilities (2)

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

Brazil BR.Digital Curitiba (CTA1)Curitiba 1 of 2
Brazil BR.Digital Porto Alegre (PAE1)Porto Alegre 1 of 1