Tci-Yasuj

BGP inherited
Cluster stats
Netblocks8 · 368 IPv4 addresses
All fragments 10 blocks across 2 clusters
Cluster ID209534932
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 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
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
78.39.114.32/27 Tci-Yasuj RIPE ASSIGNED PA ● low
78.39.115.80 – 78.39.115.127 Tci-Yasuj RIPE ASSIGNED PA ● low
85.185.190.128/26 TCI-YASUJ RIPE ASSIGNED PA ● low
217.219.20.112/28 TCI-YASUJ RIPE ASSIGNED PA ● low
217.219.21.32/29 Tci-Yasuj RIPE ASSIGNED PA ● low
217.219.21.192/28 Tci-Yasuj RIPE ASSIGNED PA ● low
217.219.23.0/25 Tci-Yasuj RIPE ASSIGNED PA ● low
217.219.23.192/26 Tci-Yasuj RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

AS12880-MNT DUMY-RIPE DUMY-RIPE