Level3 Carrier: PeeringDB fix list
AS58682 · peeringdb.com/net/6531
One thing to fix in Level3 Carrier's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Level3 Carrier'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 IPv4 address missing from PeeringDB 103.27.171.184 103.27.170.38 103.27.171.184 IPv6 address missing from PeeringDB 2401:7500:fff6::12d 2401:7500:fff6::c 2401:7500:fff6::12d Port speed differs 100G 100G + 40G + 9.999G - In the entry with IPv4 103.27.171.184: set Speed to 40000 (40G) (now 100000).
- Add an entry: IPv4 103.27.170.38, IPv6 2401:7500:fff6::c, speed 9999 (9.999G), RS peer yes.
From ixreport.com/net/58682/: 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.