Hyper Group Network Ltd.: PeeringDB fix list
AS216324
9 things to fix in Hyper Group Network Ltd.'s PeeringDB record, from what its exchanges publish: 6 to add, 3 to correct. As of 2026-10-08 22:13 UTC.
AS216324 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (6)
On the exchange's own member list, but not in Hyper Group Network Ltd.'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.35 IPv6 2001:7f8:d0::3:4d04:1 Speed Not published RS peer Yes -
IPv4 – IPv6 2001:7f8:ca:1:0:21:6324:1 Speed 1000 Mbps (1G) 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 206.83.136.57 IPv6 2001:504:9e::57 Speed 1000 Mbps (1G) RS peer Not published -
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 206.83.12.87 IPv6 2001:504:98::87 Speed 1000 Mbps (1G) RS peer Not published -
UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452From its IX-F export and website members list2 connections, so 2 entries:
IPv4 192.34.27.127 IPv6 – Speed Not published RS peer Not published IPv4 – IPv6 2602:ffb1:200:0:192:34:27:127 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.
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 Address belongs to another network in PeeringDB 185.1.125.35 is AS207705 JK-Network 185.1.125.35 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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 206.83.136.57 is AS6642 HyperGroup Global Telecommunication 206.83.136.57 Address belongs to another network in PeeringDB 2001:504:9e::57 is AS6642 HyperGroup Global Telecommunication 2001:504:9e::57 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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 206.83.12.87 is AS6642 HyperGroup Global Telecommunication 206.83.12.87 Address belongs to another network in PeeringDB 2001:504:98::87 is AS6642 HyperGroup Global Telecommunication 2001:504:98::87 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/216324/: 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.