IP Telecom (BR)
AS61573 · IP TELECOM
IP Telecom
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.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 196.60.70.80 IPv6 2001:43f8:6d1::80 Speed 10000 Mbps (10G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its IX-F export and website members list
IPv4 196.60.11.20 IPv6 2001:43f8:6d0::11:20 Speed 10000 Mbps (10G) RS peer Yes 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.
-
Problem PeeringDB has The export has Port speed differs 5G 500M - 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.
-
Problem PeeringDB has The export has Port speed differs 5G 500M - 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.
-
IPv4 80.81.192.232 IPv6 2001:7f8::f085:0:1 Speed 5000 Mbps (5G) -
IPv4 185.1.131.101 IPv6 2001:7f8:d5::f085:0:1 Speed 2000 Mbps (2G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 12 |
| Nov 18, 2026 | 12 |
| Nov 17, 2026 | 12 |
| Nov 16, 2026 | 12 |
| Nov 15, 2026 | 12 |
| Nov 14, 2026 | 12 |
| Nov 13, 2026 | 12 |
| Nov 12, 2026 | 12 |
| Nov 11, 2026 | 12 |
| Nov 10, 2026 | 12 |
| Nov 9, 2026 | 12 |
| Nov 8, 2026 | 12 |
| Nov 7, 2026 | 12 |
| Nov 6, 2026 | 12 |
| Nov 5, 2026 | 12 |
| Nov 4, 2026 | 12 |
| Nov 3, 2026 | 12 |
| Nov 2, 2026 | 12 |
| Nov 1, 2026 | 12 |
| Oct 31, 2026 | 12 |
| Oct 30, 2026 | 12 |
| Oct 29, 2026 | 12 |
| Oct 28, 2026 | 12 |
| Oct 27, 2026 | 12 |
| Oct 26, 2026 | 12 |
| Oct 25, 2026 | 12 |
| Oct 24, 2026 | 12 |
| Oct 23, 2026 | 12 |
| Oct 22, 2026 | 12 |
| Oct 21, 2026 | 12 |
| Oct 20, 2026 | 12 |
| Oct 19, 2026 | 12 |
| Oct 18, 2026 | 12 |
| Oct 17, 2026 | 12 |
| Oct 16, 2026 | 12 |
| Oct 15, 2026 | 12 |
| Oct 14, 2026 | 12 |
| Oct 13, 2026 | 12 |
| Oct 12, 2026 | 12 |
| Oct 11, 2026 | 12 |
| Oct 10, 2026 | 12 |
| Oct 9, 2026 | 12 |
| Oct 8, 2026 | 12 |
| Oct 7, 2026 | 12 |
| Oct 6, 2026 | 12 |
| Oct 5, 2026 | 12 |
| Oct 4, 2026 | 12 |
| Oct 3, 2026 | 12 |
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.
| AMS-IX Amsterdam, Netherlands | 5G | Both Speed differs | |
| DE-CIX Frankfurt Frankfurt, Germany | 5G | PeeringDB only | |
| DE-CIX Lisbon Lisbon, Portugal | 2G | PeeringDB only | |
| FL-IX Miami, United States | 10G | Both | |
| IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil | 100G | Both | |
| IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 200G | Both | |
| IX.br (PTT.br) Teresina Teresina/PI, Brazil | 20G | Both | |
| LINX LON1 London, United Kingdom | 5G | Both Speed differs | |
| NAPAfrica IX Cape Town Cape Town, South Africa | 10G | Not in PeeringDB | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 10G | Not in PeeringDB | |
| NYIIX New York New York, United States | 10G | PeeringDB |
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.
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| SwissIXZurich, Switzerland | 253 | |
| DE-CIX MadridMadrid, Spain | 224 | |
| NetIXSofia, Bulgaria | 204 | |
| Equinix MiamiMiami, United States | 175 | |
| Equinix São PauloSão Paulo, Brazil | 163 | |
| ESpanix Madrid Lower LANMadrid, Spain | 161 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| IXPlay Global PeersMadrid, Spain | 63 | |
| DE-CIX Sao PauloSao Paulo, Brazil | 58 | |
| ESpanix Madrid Upper LANMadrid, Spain | 57 | |
| Equinix ZurichZurich, Switzerland | 40 | |
| 1-ES FREEMadrid, Spain | 18 | |
| Global Peer ExchangeWashington, United States | 6 | |
| ixFabricGlobal, Australia | 2 |
Facilities (6)
The buildings IP Telecom (BR) lists in PeeringDB, and how many of the exchanges in each it's on.
| Digital Realty Madrid MAD1-2Madrid | 0 of 8 | |
| Equinix SP4 - São PauloBarueri | 1 of 6 | |
| Equinix ZH5 - Zurich, SouthZurich | 0 of 4 | |
| AngoNAP FortalezaFortaleza | 1 of 2 | |
| Equinix MI3 - Miami, Boca RatonBoca Raton | 0 of 2 | |
| Telxius Panama CLSPanama | No exchange |