LONAP Route Servers: PeeringDB fix list
AS8550 · peeringdb.com/net/12363
One thing to fix in LONAP Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on LONAP Route Servers'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 5.57.80.1 5.57.80.2 5.57.80.1 5.57.80.2 5.57.80.3 5.57.80.81 IPv6 address missing from PeeringDB 2001:7f8:17::1 2001:7f8:17::2 2001:7f8:17::1 2001:7f8:17::2 2001:7f8:17::3 2001:7f8:17::81 Port speed differs 2 × 10G 2 × 10G + 1G - Add an entry: IPv4 5.57.80.3, IPv6 2001:7f8:17::3, speed 1000 (1G), RS peer no.
- Add an entry: IPv4 5.57.80.81, IPv6 2001:7f8:17::81, speed 1000 (1G), RS peer no.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/8550/: 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.