Telxius Cable: PeeringDB fix list
AS12956 · peeringdb.com/net/620
9 things to fix in Telxius Cable's PeeringDB record, from what its exchanges publish: 5 to add, 3 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Telxius Cable'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 (5)
On the exchange's own member list, but not in Telxius Cable's PeeringDB record. Add one entry per connection with these values.
-
ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789From its IX-F export and website members listIPv4 185.1.240.208 IPv6 2001:7f8:12a::208 Speed 100000 Mbps (100G) 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.
-
The exchange's 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 listThe 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.
-
The exchange's 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 (3)
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 10G 2 × 100G + 3 × 10G 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 IPv6 address missing from PeeringDB none 2001:7f8:a0::329c:0:1 - In the entry with IPv4 185.1.192.21: set IPv6 to 2001:7f8:a0::329c:0:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:36::329c:0:1 - In the entry with IPv4 185.1.47.40: set IPv6 to 2001:7f8:36::329c:0:1 (now empty).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Telxius Cable has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.53.202.0 IPv6 – Speed 100000 Mbps (100G)
From ixreport.com/net/12956/: 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.