AERO UUDS
BGP inherited
Cluster stats
| Netblocks | 4 |
| Cluster ID | 210819461 |
| 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 | |
Footprint over time
2 weekly snapshots · JSON
10
0 netblocks since 2026-07-13
2026-07-13
peak 10
2026-07-19
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 57.130.22.128/27 | AERO UUDS | RIPE | LEGACY | ● high |
| 57.130.23.228/30 | AERO UUDS | RIPE | LEGACY | ● high |
| 217.19.181.88/29 | Aero-NET2 | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:3bf4::/48 | AERO-TEC | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to AERO UUDS 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.
| 2a00:2381:3bf4::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
ORG-AU86-RIPE
OVH-MNT
WITCOM-MNT