Claro
AS4230 · Claro S.A.
Embratel
Tools: Where can I peer with Claro? · Where should Claro peer next? · Compare Claro with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in Claro's PeeringDB record, from what its exchanges publish: 4 to add, 4 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Claro'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 (4)
On the exchange's own member list, but not in Claro'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.
-
IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil · PeeringDB 173From 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.
-
IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil · PeeringDB 177From 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.
-
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.
Correct these entries (4)
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 50G 100G - In the entry with IPv4 206.53.202.47: set Speed to 100000 (100G) (now 50000).
-
Problem PeeringDB has The export has Port speed differs 60G 100G - In the entry with IPv4 80.81.195.51: set Speed to 100000 (100G) (now 60000).
-
Problem PeeringDB has The export has Port speed differs 60G 100G - In the entry with IPv4 185.1.192.237: set Speed to 100000 (100G) (now 60000).
-
Problem PeeringDB has The export has Port speed differs 40G 100G - In the entry with IPv4 206.82.104.219: set Speed to 100000 (100G) (now 40000).
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 15 |
| Nov 18, 2026 | 15 |
| Nov 17, 2026 | 15 |
| Nov 16, 2026 | 15 |
| Nov 15, 2026 | 15 |
| Nov 14, 2026 | 15 |
| Nov 13, 2026 | 15 |
| Nov 12, 2026 | 15 |
| Nov 11, 2026 | 15 |
| Nov 10, 2026 | 15 |
| Nov 9, 2026 | 15 |
| Nov 8, 2026 | 15 |
| Nov 7, 2026 | 15 |
| Nov 6, 2026 | 15 |
| Nov 5, 2026 | 15 |
| Nov 4, 2026 | 15 |
| Nov 3, 2026 | 15 |
| Nov 2, 2026 | 15 |
| Nov 1, 2026 | 15 |
| Oct 31, 2026 | 15 |
| Oct 30, 2026 | 15 |
| Oct 29, 2026 | 15 |
| Oct 28, 2026 | 15 |
| Oct 27, 2026 | 15 |
| Oct 26, 2026 | 15 |
| Oct 25, 2026 | 15 |
| Oct 24, 2026 | 15 |
| Oct 23, 2026 | 15 |
| Oct 22, 2026 | 15 |
| Oct 21, 2026 | 15 |
| Oct 20, 2026 | 15 |
| Oct 19, 2026 | 15 |
| Oct 18, 2026 | 15 |
| Oct 17, 2026 | 15 |
| Oct 16, 2026 | 15 |
| Oct 15, 2026 | 15 |
| Oct 14, 2026 | 15 |
| Oct 13, 2026 | 15 |
| Oct 12, 2026 | 15 |
| Oct 11, 2026 | 15 |
| Oct 10, 2026 | 15 |
| Oct 9, 2026 | 15 |
| Oct 8, 2026 | 15 |
| Oct 7, 2026 | 15 |
| Oct 6, 2026 | 15 |
| Oct 5, 2026 | 15 |
| Oct 4, 2026 | 15 |
| Oct 3, 2026 | 15 |
Map
Where Claro'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 | 20G | Both | |
| DE-CIX Dallas Dallas, United States | 50G | Both Speed differs | |
| DE-CIX Frankfurt Frankfurt, Germany | 60G | Both Speed differs | |
| DE-CIX Madrid Madrid, Spain | 60G | Both Speed differs | |
| DE-CIX New York New York, United States | 40G | Both Speed differs | |
| Digital Realty Atlanta Atlanta, United States | 100G | PeeringDB | |
| Digital Realty New York New York/New Jersey, United States | 20G | PeeringDB | |
| Equinix Ashburn Ashburn, United States | 100G | PeeringDB | |
| Equinix Miami Miami, United States | 30G | PeeringDB | |
| FL-IX Miami, United States | 100G | Both | |
| IX.br (PTT.br) Campinas Campinas/SP, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil | Not in PeeringDB | ||
| 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 | Not in PeeringDB | ||
| NYIIX New York New York, United States | 100G | PeeringDB |
These exchanges have a switch in a facility where Claro lists itself in PeeringDB, but don't have Claro 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.
| NetIXSofia, Bulgaria | 204 | |
| CIX-ATLAtlanta, United States | 121 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX New YorkNew York, United States | 22 | |
| MegaIX AtlantaAtlanta, United States | 11 | |
| MegaIX MiamiMiami, United States | 10 | |
| Global Peer ExchangeWashington, United States | 6 | |
| PIT - LATAM InterconnectMiami, United States | 5 | |
| GNM-IX USNew York, United States | 4 | |
| Any2FloridaMiami/Orlando, United States | 2 |
Facilities (3)
The buildings Claro lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix MI1 - Miami, NOTAMiami | 2 of 9 | |
| Digital Realty NYC (60 Hudson)New York | 3 of 7 | |
| Digital Realty ATL13 - AtlantaAtlanta | 1 of 4 |