RUDAKI

BGP inherited
Cluster stats
Netblocks9
All fragments 17 blocks across 6 clusters
Cluster ID211749350
RegistryPEERINGDB
Customersfind customers using 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

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ 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
2a0a:2c0:11::/48 RUDAKI RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RUDAKI” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: F how networks compare →
11.1% of checked blocks have valid RPKI ROA coverage (1 of 9)
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