HELLONET
Handle
Cluster stats
| Netblocks | 6 |
| All fragments | 7 blocks across 2 clusters |
| Cluster ID | 213184693 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| 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 | |
Footprint over time
5 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-19
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 139.150.100.77/32 | HELLONET | PEERINGDB | ASSIGNED | ● high |
| 139.150.100.78/32 | HELLONET | PEERINGDB | ASSIGNED | ● high |
| 203.255.114.11/32 | HELLONET | PEERINGDB | ASSIGNED | ● high |
| 203.255.115.11/32 | HELLONET | PEERINGDB | ASSIGNED | ● high |
| 2001:3a8:7000:0:114:3:8091:11/128 | HELLONET | PEERINGDB | ASSIGNED | ● high |
| 2001:3a8:7000:0:115:3:8091:11/128 | HELLONET | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “HELLONET” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- HELLONET-ID 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- HELLONET-ID sub-allocation
NIC Handles
AS38091