ixreport

IP Telecom (BR): PeeringDB fix list

AS61573 · peeringdb.com/net/9559

PeeringDB

7 things to fix in IP Telecom (BR)'s PeeringDB record, from what its exchanges publish: 3 to add, 2 to correct, 2 to check. As of 2026-10-08 18:53 UTC.

Make the changes on IP Telecom (BR)'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 IP Telecom (BR)'s PeeringDB record. Add one entry per connection with these values.

  1. Brazil IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil · PeeringDB 177From 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. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597From its IX-F export
    IPv4196.60.70.80
    IPv62001:43f8:6d1::80
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its IX-F export and website members list
    IPv4196.60.11.20
    IPv62001:43f8:6d0::11:20
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Correct these entries (2)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs5G500M
    • In the entry with IPv4 80.249.210.42: set Speed to 500 (500M) (now 5000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs5G500M
    • In the entry with IPv4 195.66.231.249: set Speed to 500 (500M) (now 5000).

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If IP Telecom (BR) has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31Not on its IX-F export or website members list
    IPv480.81.192.232
    IPv62001:7f8::f085:0:1
    Speed5000 Mbps (5G)
  2. Portugal DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531Not on its IX-F export or website members list
    IPv4185.1.131.101
    IPv62001:7f8:d5::f085:0:1
    Speed2000 Mbps (2G)

From ixreport.com/net/61573/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.