PASHA-DI-ORSRL

BGP inherited
Cluster stats
Netblocks8
All fragments 16 blocks across 2 clusters
Cluster ID208967326
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.19.174.88/29 PASHA-DI-ORSRL RIPE ASSIGNED PA ● low
80.20.101.120/29 PASHA-DI-ORSRL RIPE ASSIGNED PA ● low
80.20.101.144/29 PASHA-DI-ORSRL RIPE ASSIGNED PA ● low
80.20.102.208/29 PASHA-DI-ORSRL RIPE ASSIGNED PA ● low
80.20.169.192/29 PASHA-DI-ORSRL RIPE ASSIGNED PA ● low
80.22.89.104/29 PASHA-DI-ORSRL RIPE ASSIGNED PA ● low
80.23.103.48/29 PASHA-DI-ORSRL RIPE ASSIGNED PA ● low
80.23.158.0/29 PASHA-DI-ORSRL RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PASHA DI” — 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.

NIC Handles

DUMY-RIPE DUMY-RIPE INTERB-MNT