TADIRAN

BGP inherited
Cluster stats
Netblocks10
All fragments 23 blocks across 10 clusters
Cluster ID208871572
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.219.244.104/29 TADIRAN-LTD RIPE ASSIGNED PA ● low
80.179.107.152/30 TADIRAN_COMMUNICATIONS RIPE ASSIGNED PA ● low
82.80.33.184/29 TADIRAN RIPE ASSIGNED PA ● low
82.80.88.136/29 TADIRAN-LTD RIPE ASSIGNED PA ● low
192.116.242.72/29 TADIRAN RIPE ASSIGNED PA ● low
212.143.168.112/28 NV-Tadiran RIPE ASSIGNED PA ● low
212.179.19.96/29 TADIRAN-COMMUNICATIONS-LTD RIPE ASSIGNED PA ● low
212.179.22.8/30 TADIRAN-COMMUNICATIONS-LTD RIPE ASSIGNED PA ● low
212.179.39.64/28 TADIRAN-LTD RIPE ASSIGNED PA ● low
213.8.94.24/29 TADIRAN RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “TADIRAN” — 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.
Combined view of all 10 name-family clusters →
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS5486-MNT AS8551-MNT AS9116-MNT DUMY-RIPE DUMY-RIPE NV-MNT-RIPE