NAP
BGP inherited
Cluster stats
| Netblocks | 5 |
| All fragments | 80 blocks across 7 clusters |
| Cluster ID | 191867101 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 61.152.246.0/24 | NAP | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 83.167.220.184/29 | NAP | RIPE | ASSIGNED PA | ● low |
| 87.204.164.64/30 | NAP | RIPE | ASSIGNED PA | ● low |
| 93.117.196.112/28 | NAP | RIPE | ASSIGNED PA | ● low |
| 93.117.232.192/29 | NAP | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
Possible discrepancies (1)
These blocks are registered to NAP but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 61.152.246.0/24 /24 | authorized for AS4811 — China Telecom (Group) |
NIC Handles
DUMY-RIPE
DUMY-RIPE
HY174-AP
MAINT-CHINANET-SH
NETIA-MNT
TNF-MNT
XCM3-AP