Ivanov Ruslan Mikhailovich

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks4
IPv6 4 prefixes (largest 2a11:9644::/32)
Record ID247041934
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a0a:8f80:4210::/48 Ivanov Ruslan Mikhailovich RIPE ASSIGNED ● low
2a11:9644::/32 Ivanov Ruslan Mikhailovich RIPE AGGREGATED-BY-LIR ● low
2a11:eac5::/32 Ivanov Ruslan Mikhailovich RIPE AGGREGATED-BY-LIR ● low
2a12:f982::/32 Ivanov Ruslan Mikhailovich RIPE AGGREGATED-BY-LIR ● low

IPv6 ranges (4)

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 (3)

These blocks are registered to Ivanov Ruslan Mikhailovich 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.

2a11:9644::/32 /32 authorized for AS218636 — IP-RIPE
2a11:eac5::/32 /32 authorized for AS218636 — IP-RIPE
2a12:f982::/32 /32 authorized for AS218636 — IP-RIPE

NIC Handles

DUMY-RIPE DUMY-RIPE IP-RIPE ORG-IRM1-RIPE