Infinity Information Technology: PeeringDB fix list
AS214375 · peeringdb.com/net/37068
2 things to fix in Infinity Information Technology's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 21:35 UTC.
Make the changes on Infinity Information Technology'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 (1)
On the exchange's own member list, but not in Infinity Information Technology's PeeringDB record. Add one entry per connection with these values.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members listIPv4 185.1.125.126 IPv6 2001:7f8:d0::3:4567:1 Speed Not published RS peer Yes
Correct these entries (1)
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.125.126 is AS212539 Francesco Masala 185.1.125.126 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.
From ixreport.com/net/214375/: 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.