Neolog Online Services: PeeringDB fix list
AS141834 · peeringdb.com/net/27908
2 things to fix in Neolog Online Services's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Neolog Online Services'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 IPv6 address missing from PeeringDB none 2401:7500:fff6::a6 - In the entry with IPv4 103.27.170.74: set IPv6 to 2401:7500:fff6::a6 (now empty).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Neolog Online Services has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 103.184.198.19 IPv6 – Speed 10000 Mbps (10G)
From ixreport.com/net/141834/: 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.