WOBCOM: PeeringDB fix list
AS9136 · peeringdb.com/net/18489
3 things to fix in WOBCOM's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on WOBCOM'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 100G 30G - In the entry with IPv4 193.178.185.123: set Speed to 30000 (30G) (now 100000).
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 100G 12.5G - In the entry with IPv4 185.0.20.127: set Speed to 12500 (12.5G) (now 100000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If WOBCOM has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 185.1.74.45 IPv6 2001:7f8:a5::9136:1 Speed 40000 Mbps (40G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/9136/: 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.