Unet Communication: PeeringDB fix list
AS42518 · peeringdb.com/net/18633
3 things to fix in Unet Communication's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Unet Communication'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 IPv6 address missing from PeeringDB none 2a03:5f80:4::224:7 - In the entry with IPv4 178.18.224.7: set IPv6 to 2a03:5f80:4::224:7 (now empty).
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 IPv4 address missing from PeeringDB 194.226.102.123 194.226.100.123 194.226.102.123 - Add an entry: IPv4 194.226.100.123, IPv6 –, RS peer yes.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Unet Communication has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.208.209.223 IPv6 – Speed 10000 Mbps (10G)
From ixreport.com/net/42518/: 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.