UTG: PeeringDB fix list
AS50581 · peeringdb.com/net/7659
6 things to fix in UTG's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct, 2 to check. As of 2026-10-08 21:35 UTC.
Make the changes on UTG's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (2)
On the exchange's own member list, but not in UTG's PeeringDB record. Add one entry per connection with these values.
-
IPv4 178.18.236.234 IPv6 2a03:5f80:4:2::236:234 Speed 100000 Mbps (100G) 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.
-
IPv4 86.104.125.178 IPv6 2001:7f8:64:225:0:5:581:1 Speed 10000 Mbps (10G) 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.
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 Port speed differs 40G 400G - In the entry with IPv4 80.81.196.198: set Speed to 400000 (400G) (now 40000).
-
Problem PeeringDB has The export has Port speed differs 100G 12.5G - In the entry with IPv4 185.0.20.212: set Speed to 12500 (12.5G) (now 100000).
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If UTG has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 80.249.214.160 IPv6 2001:7f8:1::a505:581:1 Speed 20000 Mbps (20G) -
IPv4 185.0.10.33 IPv6 2001:7f8:e2::a505:581:1 Speed 100000 Mbps (100G)
From ixreport.com/net/50581/: 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.