ixreport

Hyper Group Network Ltd.

AS216324

6Exchanges
6On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
2Using the route servers
9To fix in PeeringDB

This network has no PeeringDB record; it was found on exchanges' own member lists.

Tools: Where can I peer with Hyper Group Network Ltd.? · Where should Hyper Group Network Ltd. peer next? · Compare Hyper Group Network Ltd. with another network

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

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-11-19 12:40 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.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4185.1.125.35
    IPv62001:7f8:d0::3:4d04:1
    SpeedNot published
    RS peerYes
  2. Switzerland FogIXP Avers, Switzerland · PeeringDB 3756From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:ca:1:0:21:6324:1
    Speed1000 Mbps (1G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. United States HOUIX Houston, United States · PeeringDB 2835From its IX-F export and website members list
    IPv4206.83.136.57
    IPv62001:504:9e::57
    Speed1000 Mbps (1G)
    RS peerNot published
  4. Taiwan NRIX Taipei City, Taiwan · PeeringDB 4299From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  5. United States STLIX Saint Louis, MO, United States · PeeringDB 2585From its IX-F export and website members list
    IPv4206.83.12.87
    IPv62001:504:98::87
    Speed1000 Mbps (1G)
    RS peerNot published
  6. Canada UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4192.34.27.127
    IPv6–
    SpeedNot published
    RS peerNot published
    IPv4–
    IPv62602:ffb1:200:0:192:34:27:127
    SpeedNot published
    RS peerNot 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.

  1. ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB185.1.125.35 is AS207705 JK-Network185.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.

  2. United States HOUIX Houston, United States · PeeringDB 2835
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB206.83.136.57 is AS6642 HyperGroup Global Telecommunication206.83.136.57
    Address belongs to another network in PeeringDB2001:504:9e::57 is AS6642 HyperGroup Global Telecommunication2001: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.

  3. United States STLIX Saint Louis, MO, United States · PeeringDB 2585
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB206.83.12.87 is AS6642 HyperGroup Global Telecommunication206.83.12.87
    Address belongs to another network in PeeringDB2001:504:98::87 is AS6642 HyperGroup Global Telecommunication2001: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.

Exchanges over time

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
Oct 30, 20266
Oct 29, 20266
Oct 28, 20266
Oct 27, 20266
Oct 26, 20266
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20266
Oct 19, 20266
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20266
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

Map

Where Hyper Group Network Ltd.'s exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 3G, at the 3 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 185.1.125.35 2001:7f8:d0::3:4d04:1 Yes Not in PeeringDB Address taken
Switzerland FogIXP Avers, Switzerland 2001:7f8:ca:1::21:6324:1 1G Yes Not in PeeringDB
United States HOUIX Houston, United States 206.83.136.57 2001:504:9e::57 1G Not in PeeringDB Address taken
Taiwan NRIX Taipei City, Taiwan Not in PeeringDB
United States STLIX Saint Louis, MO, United States 206.83.12.87 2001:504:98::87 1G Not in PeeringDB Address taken
Canada UNM-Exch Canada-West Vancouver, Canada 192.34.27.127 2602:ffb1:200:0:192:34:27:127 Not in PeeringDB