NAM-DC-SUBNET-240
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 4 blocks across 4 clusters |
| Cluster ID | 210789352 |
| 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 | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.241.240.0/24 | NAM-DC-SUBNET-240 | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “NAM DC SUBNET” — 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.
- NAM-DC-SUBNET-241 1 blocks
- NAM-DC-SUBNET-242 1 blocks
- NAM-DC-SUBNET-243 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.
- ISIS-SCREENED-SUBNET via Vodafone GmbH sub-allocation
- WATER-RC-SUBNET1 sub-allocation
- WATER-RC-SUBNET sub-allocation
- Hobbynet Basd Subnet via BIT BV sub-allocation
- Subnet Axiome sub-allocation
- Plumettaz Subnet sub-allocation
- Subnet Logidys sub-allocation
- Ssa Subnet sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
cz-nam-1-mnt