Abuse IO
AbuseIO
Registry
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.
Cluster stats
| Netblocks | 3 |
| Cluster ID | 194199271 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| 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 | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 213.136.29.184/29 | AbuseIO | RIPE | ASSIGNED PA | ● low |
| 213.154.230.96/28 | AbuseIO | RIPE | ASSIGNED PA | ● low |
| 2001:7b8:63a::/48 | AbuseIO | RIPE | ALLOCATED-BY-LIR | ● low |
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 AbuseIO 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.
| 2001:7b8:63a::/48 /48 | authorized for AS12859 — BIT BV |
NIC Handles
BIT-MNT
DUMY-RIPE
DUMY-RIPE
ORG-AF120-RIPE