ORG-AA1656-RIPE
BGP inherited
Cluster stats
| Netblocks | 7 · 825 IPv4 addresses |
| Cluster ID | 210689534 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-19
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.190.101.0/25 | ORG-AA1656-RIPE | RIPE | ASSIGNED PA | ● low |
| 5.190.103.0/25 | ORG-AA1656-RIPE | RIPE | ASSIGNED PA | ● low |
| 5.190.103.128/27 | ORG-AA1656-RIPE | RIPE | ASSIGNED PA | ● low |
| 5.190.103.160 – 5.190.103.223 | ORG-AA1656-RIPE | RIPE | ASSIGNED PA | ● low |
| 5.190.103.224/27 | ORG-AA1656-RIPE | RIPE | ASSIGNED PA | ● low |
| 5.190.131.64 – 5.190.131.255 | ORG-AA1656-RIPE | RIPE | ASSIGNED PA | ● low |
| 5.190.218.0/24 | ORG-AA1656-RIPE | 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
(7 of 7)
Possible discrepancies (1)
These blocks are registered to ORG-AA1656-RIPE 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.
| 5.190.218.0/24 /24 | authorized for AS58224 — Iran Telecommunication Company PJS |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-TCF
TCI-RIPE-MNT