RUDAKI

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks10
IPv6 7 prefixes (largest 2a0a:2c0:11::/48)
Also registered under this name 18 netblocks across 6 separate records
Record ID242166755
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.134.43/32 RUDAKI PEERINGDB ASSIGNED ● high
185.1.225.13/32 RUDAKI PEERINGDB ASSIGNED ● high
185.1.238.20/32 RUDAKI PEERINGDB ASSIGNED ● high
2001:7f8:d0::3:3a35:1/128 RUDAKI PEERINGDB ASSIGNED ● high
2001:7f8:d8::211:509/128 RUDAKI PEERINGDB ASSIGNED ● high
2001:7f8:11f:1:0:211:509:1/128 RUDAKI PEERINGDB ASSIGNED ● high
2001:7f8:11f:be00::100/128 RUDAKI PEERINGDB ASSIGNED ● high
2001:7f8:128::20/128 RUDAKI PEERINGDB ASSIGNED ● high
2602:fed2:fff:ffff:6::11/128 RUDAKI PEERINGDB ASSIGNED ● high
2a0a:2c0:11::/48 RUDAKI RIPE ASSIGNED ● low

IPv6 ranges (7)

Footprint over time

12 weekly snapshots · JSON
10 +1 netblocks since 2026-07-05
2026-07-05 peak 10 2026-09-13

Network trust

what's this?
RPKI hygiene: F how networks compare →
10.0% of checked blocks have valid RPKI ROA coverage (1 of 10)
RPKI-inferred operator Rudakov Ihor
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

AS211509 DUMY-RIPE DUMY-RIPE K-Link-MNT RUDAKI-MNT