TAGADAB

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.172.255.64/29 TAGADAB-LTD RIPE ASSIGNED PA ● low
79.123.98.184/29 TAGADAB RIPE ASSIGNED PA ● low
79.123.98.192/29 TAGADAB RIPE ASSIGNED PA ● low
80.241.49.128/29 TAGADAB RIPE ASSIGNED PA ● low
94.102.159.56/29 TAGADAB-LTD RIPE ASSIGNED PA ● low
212.188.166.104/29 TAGADAB RIPE ASSIGNED PA ● low
212.188.166.120/29 TAGADAB RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “TAGADAB” — 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 21 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: C how networks compare →
57.1% of checked blocks have valid RPKI ROA coverage (4 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS8426-MNT DUMY-RIPE DUMY-RIPE MNT-TAGADAB