AXNETS_US
Data as of 2026-08-23
BGP inherited
Cluster stats
| Netblocks | 4 |
| IPv6 | 4 prefixes (largest 2a06:a004:f300::/44) |
| Cluster ID | 228032808 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a06:a004:f300::/44 | AXNETS_US | RIPE | ASSIGNED | ● low |
| 2a14:7580:fa50::/44 | AXNETS_US | RIPE | ASSIGNED | ● low |
| 2a14:7580:faf3::/48 | AXNETS_US | RIPE | ASSIGNED | ● low |
| 2a14:7580:ff45::/48 | AXNETS_US | RIPE | ASSIGNED | ● low |
IPv6 ranges (4)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
RPKI-inferred operator
Hanxun Xu
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
AXW-MNT
DUMY-RIPE
DUMY-RIPE