CTGNet: PeeringDB fix list
AS23764 · peeringdb.com/net/17755
8 things to fix in CTGNet's PeeringDB record, from what its exchanges publish: 5 to add, 2 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on CTGNet'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 CTGNet's PeeringDB record. Add one entry per connection with these values.
-
IPv4 196.60.58.236 IPv6 2001:43f8:11f0::a502:3764:1 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.
-
IPv4 185.6.36.112 IPv6 2001:7f8:18::112 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.
-
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 website members listThe exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 217.29.68.13 IPv6 2001:7f8:b:100:1d1:a5d2:3764:13 Speed 10000 Mbps (10G) RS peer Yes
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 2G 10G - In the entry with IPv4 194.53.172.73: set Speed to 10000 (10G) (now 2000).
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 30G 100G - In the entry with IPv4 196.60.96.30: set Speed to 100000 (100G) (now 30000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If CTGNet has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 196.60.68.27 IPv6 2001:43f8:c0:1::27 Speed 40000 Mbps (40G)
From ixreport.com/net/23764/: 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.