Horizon Scope: PeeringDB fix list
AS212250 · peeringdb.com/net/29314
One thing to fix in Horizon Scope's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 21:35 UTC.
Make the changes on Horizon Scope'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 Address belongs to another network in PeeringDB 185.1.8.6 is AS6412 Zajil International Telecom Company K.S.C.C 185.1.8.6 Address belongs to another network in PeeringDB 2001:7f8:73::190c:0:1 is AS6412 Zajil International Telecom Company K.S.C.C 2001:7f8:73::190c:0:1 Port speed differs 100G 2 × 100G An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- Add an entry: IPv4 –, IPv6 –, speed 100000 (100G), RS peer yes.
From ixreport.com/net/212250/: 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.