TY/CXIX Route Server: PeeringDB fix list
AS402298 · peeringdb.com/net/41860
2 things to fix in TY/CXIX Route Server's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 22:13 UTC.
Make the changes on TY/CXIX Route Server's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (1)
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 2 × 20G 100G + 40G - In the entry with IPv4 33.0.0.1: set Speed to 100000 (100G) (now 20000).
- In the entry with IPv4 33.0.0.65: set Speed to 40000 (40G) (now 20000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 23.154.164.193 IPv6 2602:f429:32::1 Speed 100000 Mbps (100G)
From ixreport.com/net/402298/: 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.