EDGENET: PeeringDB fix list
AS210481
3 things to fix in EDGENET's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 20:58 UTC.
AS210481 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (3)
On the exchange's own member list, but not in EDGENET'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 – IPv6 2001:7f8:d0::3:3631:1 Speed Not published RS peer Yes -
IPv4 193.189.83.244 IPv6 2001:7f8:33::a121:481:1 Speed 100 Mbps (100M) 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.
-
UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452From its IX-F export and website members list2 connections, so 2 entries:
IPv4 192.34.27.78 IPv6 – Speed Not published RS peer Not published IPv4 – IPv6 2602:ffb1:200:0:192:34:27:78 Speed Not published RS peer Not published PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/210481/: 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.