Web Werks DataCenter: PeeringDB fix list
AS133296 · peeringdb.com/net/10681
2 things to fix in Web Werks DataCenter's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on Web Werks DataCenter'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 (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 10G 2 × 10G -
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 103.27.170.25 103.27.170.119 103.27.170.120 103.27.170.25 IPv6 address in PeeringDB, not in the export 2401:7500:fff6::25 2401:7500:fff6::272 2401:7500:fff6::273 2401:7500:fff6::25 Port speed differs 2 × 100G + 40G 40G + 1G - The entry with IPv4 103.27.170.119, IPv6 2401:7500:fff6::273 isn't in the export: delete it if that connection is gone.
- The entry with IPv4 103.27.170.120, IPv6 2401:7500:fff6::272 isn't in the export: delete it if that connection is gone.
From ixreport.com/net/133296/: 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.