FiberComm: PeeringDB fix list
AS54578 · peeringdb.com/net/16215
3 things to fix in FiberComm's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on FiberComm'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 (1)
On the exchange's own member list, but not in FiberComm's PeeringDB record. Add one entry per connection with these values.
-
IPv4 149.112.41.2 IPv6 2001:504:126::2 Speed 10000 Mbps (10G) RS peer Not published
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 IPv6 address missing from PeeringDB none 2001:504:27::d532:0:1 - In the entry with IPv4 206.108.255.78: set IPv6 to 2001:504:27::d532:0:1 (now empty).
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 FiberComm has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.126.235.34 IPv6 – Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/54578/: 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.