ixreport

HyperGroup Global Telecommunication

AS6642 · HN Network

Hyper Group Network

5Exchanges
1On an exchange's list, not in PeeringDB
2In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
5Using the route servers
5To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with HyperGroup Global Telecommunication? · Where should HyperGroup Global Telecommunication peer next? · Compare HyperGroup Global Telecommunication with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

5 things to fix in HyperGroup Global Telecommunication's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct, 2 to check. As of 2026-11-19 12:40 UTC.

Make the changes on HyperGroup Global Telecommunication'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 HyperGroup Global Telecommunication's PeeringDB record. Add one entry per connection with these values.

  1. Taiwan STUIX Taipei City, Taiwan · PeeringDB 3352From its IX-F export
    IPv4103.158.187.130
    IPv62a0f:5707:ffe3::130
    Speed10000 Mbps (10G)
    RS peerYes

    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.

  1. United States F4IX MCI Kansas City, United States · PeeringDB 4378
    ProblemPeeringDB hasThe export has
    Port speed differs500M + 100M2 × 100M
    • In the entry with IPv6 2602:fa3d:f4:1::b5: set Speed to 100 (100M) (now 500).

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

  2. United States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 206.51.7.237: set Speed to 1000 (1G) (now 10000).

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If HyperGroup Global Telecommunication has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United States HOUIX Houston, United States · PeeringDB 2835Not on its IX-F export or website members list
    IPv4206.83.136.57
    IPv62001:504:9e::57
    Speed10000 Mbps (10G)
  2. United States STLIX Saint Louis, MO, United States · PeeringDB 2585Not on its IX-F export or website members list
    IPv4206.83.12.87
    IPv62001:504:98::87
    Speed10000 Mbps (10G)

Exchanges over time

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

Map

Where HyperGroup Global Telecommunication'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 40.6G across 5 exchanges.

United States F4IX MCI Kansas City, United States 2602:fa3d:f4:1::a2
2602:fa3d:f4:1::b5
500M + 100M Yes Both Speed differs
United States HOUIX Houston, United States 206.83.136.57 2001:504:9e::57 10G Yes PeeringDB only
United States KCIX Kansas City, United States 206.51.7.237 2001:504:1b:1::237 10G Yes Both Speed differs
United States STLIX Saint Louis, MO, United States 206.83.12.87 2001:504:98::87 10G Yes PeeringDB only
Taiwan STUIX Taipei City, Taiwan 103.158.187.130 2a0f:5707:ffe3::130 10G Yes Not in PeeringDB

Exchanges in its buildings that it isn't on (12)

These exchanges have a switch in a facility where HyperGroup Global Telecommunication lists itself in PeeringDB, but don't have HyperGroup Global Telecommunication as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

United States SIX SeattleSeattle, United States 372 1530 SWIFT - NOCIX
United States MICEMinneapolis, MN, United States 157 1530 SWIFT - NOCIX
United States IX-DenverDenver, United States 96 1530 SWIFT - NOCIX
United States SIX Seattle (Jumbo)Seattle, United States 69 1530 SWIFT - NOCIX
Hong Kong ixFabric - Hong KongHong Kong, Hong Kong 50 iTech Towers 2
Hong Kong Hong Kong Global Internet ExchangeHong Kong, Hong Kong 33 iTech Towers 2
Hong Kong DataSphere Internet Exchange (Hong Kong)Hong Kong, Hong Kong 29 iTech Towers 2
United States HN Internet Exchange (Main)North Kansas City, United States 27 1530 SWIFT - NOCIX
United States SpringIXSpringfield, MO, United States 22 1530 SWIFT - NOCIX
United States DesMoinesIXDes Moines, United States 11 1530 SWIFT - NOCIX
United States SIOUIXSioux City, United States 4 1530 SWIFT - NOCIX
United States MOCIXKansas City, United States 3 1530 SWIFT - NOCIX
Facilities (2)

The buildings HyperGroup Global Telecommunication lists in PeeringDB, and how many of the exchanges in each it's on.

United States 1530 SWIFT - NOCIXNorth Kansas City 4 of 13
Hong Kong iTech Towers 2New Territories 0 of 3