Quickline AG: PeeringDB fix list
AS15600 · peeringdb.com/net/186
2 things to fix in Quickline AG's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Quickline AG'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 (2)
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 80.249.208.128 80.249.208.128 80.249.210.193 IPv6 address missing from PeeringDB 2001:7f8:1::a501:5600:1 2001:7f8:1::a501:5600:1 2001:7f8:1::a501:5600:2 Port speed differs 30G 100G + 30G - Add an entry: IPv4 80.249.210.193, IPv6 2001:7f8:1::a501:5600:2, speed 100000 (100G), 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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 80.81.195.28 is AS140443 Herza Cloud 80.81.195.28 IPv6 address missing from PeeringDB 2001:7f8::3cf0:0:1 2001:7f8::3cf0:0:1 2001:7f8::3cf0:0:2 Port speed differs 100G 200G + 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 2001:7f8::3cf0:0:2, speed 200000 (200G), RS peer yes.
From ixreport.com/net/15600/: 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.