ixreport

IP Telecom (BR)

AS61573 · IP TELECOM

IP Telecom

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

Tools: Where can I peer with IP Telecom (BR)? · Where should IP Telecom (BR) peer next? · Compare IP Telecom (BR) with another network

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

PeeringDB fix list Printable page · CSV

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-11-19 12:40 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)

Exchanges over time

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

Map

Where IP Telecom (BR)'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 377G, at the 11 of 12 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.210.42 2001:7f8:1::a506:1573:1 5G Down Both Speed differs
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.192.232 2001:7f8::f085:0:1 5G Down PeeringDB only
Portugal DE-CIX Lisbon Lisbon, Portugal 185.1.131.101 2001:7f8:d5::f085:0:1 2G Down PeeringDB only
United States FL-IX Miami, United States 206.41.108.116 2001:504:40:108::1:116 10G 69 routes Both
Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil 45.68.72.242 2001:12f8:0:9::242 100G 69 routes Both
Brazil IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil Not in PeeringDB
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.221.27 2001:12f8::221:27 200G 65 routes Both
Brazil IX.br (PTT.br) Teresina Teresina/PI, Brazil 200.219.138.6 2001:12f8:0:29::6 20G 66 routes Both
United Kingdom LINX LON1 London, United Kingdom 195.66.231.249 2001:7f8:4::f085:1 5G Down Both Speed differs
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.80 2001:43f8:6d1::80 10G Yes Not in PeeringDB
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.11.20 2001:43f8:6d0::11:20 10G Yes Not in PeeringDB
United States NYIIX New York New York, United States 198.32.161.36 2001:504:1::a506:1573:1 10G Yes PeeringDB

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

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

Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 Digital Realty Madrid MAD1-2
Switzerland SwissIXZurich, Switzerland 253 Equinix ZH5 - Zurich, South
Spain DE-CIX MadridMadrid, Spain 224 Digital Realty Madrid MAD1-2
Bulgaria NetIXSofia, Bulgaria 204 Digital Realty Madrid MAD1-2; Equinix SP4 - São Paulo; Equinix ZH5 - Zurich, South and 2 more
United States Equinix MiamiMiami, United States 175 Equinix MI3 - Miami, Boca Raton
Brazil Equinix São PauloSão Paulo, Brazil 163 Equinix SP4 - São Paulo
Spain ESpanix Madrid Lower LANMadrid, Spain 161 Digital Realty Madrid MAD1-2
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Equinix ZH5 - Zurich, South
Spain IXPlay Global PeersMadrid, Spain 63 Digital Realty Madrid MAD1-2
Brazil DE-CIX Sao PauloSao Paulo, Brazil 58 Equinix SP4 - São Paulo
Spain ESpanix Madrid Upper LANMadrid, Spain 57 Digital Realty Madrid MAD1-2
Switzerland Equinix ZurichZurich, Switzerland 40 Equinix ZH5 - Zurich, South
Spain 1-ES FREEMadrid, Spain 18 Digital Realty Madrid MAD1-2
United States Global Peer ExchangeWashington, United States 6 Digital Realty Madrid MAD1-2; Equinix SP4 - São Paulo
Australia ixFabricGlobal, Australia 2 Equinix SP4 - São Paulo
Facilities (6)

The buildings IP Telecom (BR) lists in PeeringDB, and how many of the exchanges in each it's on.

Spain Digital Realty Madrid MAD1-2Madrid 0 of 8
Brazil Equinix SP4 - São PauloBarueri 1 of 6
Switzerland Equinix ZH5 - Zurich, SouthZurich 0 of 4
Brazil AngoNAP FortalezaFortaleza 1 of 2
United States Equinix MI3 - Miami, Boca RatonBoca Raton 0 of 2
Panama Telxius Panama CLSPanama No exchange