INFOBIP: PeeringDB fix list
AS43009 · peeringdb.com/net/15093
3 things to fix in INFOBIP's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on INFOBIP'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 IPv4 address missing from PeeringDB 185.1.87.68 185.1.87.68 185.1.87.130 Port speed differs 1G 2 × 10G - In the entry with IPv4 185.1.87.68: set Speed to 10000 (10G) (now 1000).
- Add an entry: IPv4 185.1.87.130, IPv6 –, speed 10000 (10G), RS peer yes.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:8:20:0:a801:0:1 2001:7f8:8:20:0:a801:0:2 - In the entry with IPv4 62.69.146.80: set IPv6 to 2001:7f8:8:20:0:a801:0:1 (now empty).
- In the entry with IPv4 62.69.146.84: set IPv6 to 2001:7f8:8:20:0:a801:0:2 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2606:a980:0:2::14 - In the entry with IPv4 206.53.173.20: set IPv6 to 2606:a980:0:2::14 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
From ixreport.com/net/43009/: 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.