TKT

BGP inherited
Cluster stats
Netblocks10 · 3,162 IPv4 addresses
Registered in Poland (7) · Netherlands (3)
All fragments 31 blocks across 19 clusters
Cluster ID208838398
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-12

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.54.112.0/24 TKT-NET RIPE ASSIGNED PA ● low
178.183.0.224/28 TKT RIPE ASSIGNED PA ● low
178.183.0.240/28 TKT RIPE ASSIGNED PA ● low
195.116.195.0/24 TKT-NET RIPE ASSIGNED PA ● low
195.136.200.0/24 TKT-NET RIPE ASSIGNED PA ● low
195.136.224.0/21 TKT-NET RIPE ASSIGNED PA ● low
212.153.182.192/27 TKT RIPE ASSIGNED PA ● low
212.153.183.0/27 TKT RIPE ASSIGNED PA ● low
212.244.115.0/24 TKT-NET RIPE ASSIGNED PA ● low
213.34.140.36/30 TKT RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

Network trust

what's this?
RPKI hygiene: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (8 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS12912-AUX-MNT DUMY-RIPE DUMY-RIPE MNT-EXATEL NLNET-MNT TNF-MNT TPNET