NA5
Data as of 2026-09-06
BGP inherited
Limited data: only 3 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.
This organisation
| Netblocks | 3 |
| IPv6 | 1 prefix (largest 2a10:1fc0:1::/48) |
| Record ID | 236149247 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 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 (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 159.100.96.184/30 | NA5 | RIPE | LEGACY | ● low |
| 159.100.101.28/30 | NA5 | RIPE | LEGACY | ● low |
| 2a10:1fc0:1::/48 | BV-NA5 | RIPE | AGGREGATED-BY-LIR | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a10:1fc0:1::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to NA5 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.
| 2a10:1fc0:1::/48 /48 | authorized for AS62005 — BlueVPS OU |
NIC Handles
DUMY-RIPE
DUMY-RIPE
TNF-MNT
mnt-ee-bluevps-1