Hyper Group Global Communication

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks10
IPv6 9 prefixes (largest 2001:7f8:17::3:4d04:1/128)
Record ID245800023
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.57.82.137/32 Hyper Group Global Communication PEERINGDB ASSIGNED ● high
2001:7f8:17::3:4d04:1/128 Hyper Group Global Communication PEERINGDB ASSIGNED ● high
2001:7f8:d0::3:4d04:1/128 Hyper Group Global Communication PEERINGDB ASSIGNED ● high
2406:840:1f:1000:0:21:6324:1/128 Hyper Group Global Communication PEERINGDB ASSIGNED ● high
2602:f9f6:7f0:5:0:21:6324:1/128 Hyper Group Global Communication PEERINGDB ASSIGNED ● high
2a05:dfc1:7810::7/128 Hyper Group Global Communication PEERINGDB ASSIGNED ● high
2a0f:85c1:363:1::666/128 Hyper Group Global Communication PEERINGDB ASSIGNED ● high
2a0f:85c1:363:1:21:6324:0:1/128 Hyper Group Global Communication PEERINGDB ASSIGNED ● high
2a0f:85c1:363:1:21:6324:0:2/128 Hyper Group Global Communication PEERINGDB ASSIGNED ● high
2a0f:85c1:363:1:21:6324:0:3/128 Hyper Group Global Communication PEERINGDB ASSIGNED ● high

IPv6 ranges (9)

Footprint over time

15 weekly snapshots · JSON
10 -2 netblocks since 2026-07-05
2026-07-05 peak 12 2026-10-04

Network trust

what's this?
RPKI hygiene: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (8 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS216324