RIPE-ATLAS
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 18 blocks across 13 clusters |
| Cluster ID | 194104180 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 77.73.151.8/29 | RIPE-ATLAS | RIPE | ASSIGNED PA | ● low |
| 89.251.238.64/29 | RIPE_ATLAS | RIPE | ASSIGNED PA | ● low |
| 2001:40b8:200:2010::/64 | RIPE-ATLAS-NET | RIPE | ASSIGNED | ● low |
| 2a07:a40:fffe::/48 | RIPE-ATLAS | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
Possible discrepancies (1)
These blocks are registered to RIPE-ATLAS 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.
| 2a07:a40:fffe::/48 /48 | authorized for AS48821 — Mauve Mailorder Software Verwaltung GmbH |
NIC Handles
DUMY-RIPE
DUMY-RIPE
GLOBVILL-MNT
SARGASSO-MNT
T-Systems-Eltec
de-mauve-1-mnt