NEGU: PeeringDB fix list
AS54309 · peeringdb.com/net/33915
3 things to fix in NEGU's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on NEGU'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 (3)
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.192.107 is AS202829 Wifi Sancti Petri 185.1.192.107 IPv6 address missing from PeeringDB 2001:7f8:a0::d425:0:1 2001:7f8:a0::d425:0:1 2001:7f8:a0::d425:0:2 Port speed differs 1G 100G + 20G 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.
- In the entry with IPv4 185.1.193.9: set Speed to 20000 (20G) (now 1000).
- Add an entry: IPv4 –, IPv6 2001:7f8:a0::d425:0:2, speed 100000 (100G), RS peer yes.
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 206.82.105.116: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 1G 2G - In the entry with IPv4 195.66.231.110: set Speed to 2000 (2G) (now 1000).
From ixreport.com/net/54309/: 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.