HYPER TELECOM

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks8 · 2,049 IPv4 addresses
IPv6 2 prefixes (largest 2804:8f0::/32)
Record ID245697221
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.184.144.106/32 HYPER TELECOM PEERINGDB ASSIGNED ● high
132.255.180.0/24 HYPER TELECOM BGP ANNOUNCED ● high
132.255.180.0/22 UNKNOWN LACNIC allocated ● high
177.129.144.0/23 HYPER TELECOM BGP ANNOUNCED ● high
177.129.144.0/22 HYPER TELECOM BGP ANNOUNCED ● high
177.129.147.0/24 HYPER TELECOM BGP ANNOUNCED ● high
2001:12f8:0:13::106/128 HYPER TELECOM PEERINGDB ASSIGNED ● high
2804:8f0::/32 UNKNOWN LACNIC allocated ● high

IPv6 ranges (2)

CIDR
2804:8f0::/32
2001:12f8:0:13::106/128

Footprint over time

7 weekly snapshots · JSON
13 +5 netblocks since 2026-07-05
2026-07-05 peak 13 2026-10-04

Network trust

what's this?
RPKI hygiene: F how networks compare →
15.4% of checked blocks have valid RPKI ROA coverage (2 of 13)
No discrepancies found among checked blocks.

NIC Handles

10377783000180 AS263040 AS263040 JCSDI3 JCSDI3 PJJ5