EASTON-NET-HK
Data as of 2026-07-26
BGP inherited
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 2 |
| IPv6 | 1 prefix (largest 2a0e:aa06:542::/48) |
| Cluster ID | 216293022 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 210.176.208.184/29 | EASTON-HK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 2a0e:aa06:542::/48 | EASTON-NET-HK | RIPE | ASSIGNED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a0e:aa06:542::/48 |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
RPKI-inferred operator
YANG MAN
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
BNA2-AP
DUMY-RIPE
DUMY-RIPE
EASTON-NET-MNT
MAINT-HK-PCCW-BIA-CS
TA66-AP