TBTNET TELEKOM LTD. STI.

TBTNET-TELEKOM
BGP inherited
Cluster stats
Netblocks8 · 2,040 IPv4 addresses
All fragments 51 blocks across 6 clusters
Cluster ID210716204
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
185.194.172.0/24 TBTNET-TELEKOM RIPE ASSIGNED PA ● medium
185.194.173.0/24 TBTNET-TELEKOM RIPE ASSIGNED PA ● medium
185.194.174.0/24 TBTNET-TELEKOM RIPE ASSIGNED PA ● medium
185.194.175.0/24 TBTNET-TELEKOM RIPE ASSIGNED PA ● medium
194.156.236.0/24 TBTNET-TELEKOM RIPE ASSIGNED PA ● medium
194.156.237.0/24 TBTNET-TELEKOM RIPE ASSIGNED PA ● medium
194.156.238.0/24 TBTNET-TELEKOM RIPE ASSIGNED PA ● medium
194.156.239.0/24 TBTNET-TELEKOM RIPE ASSIGNED PA ● medium

Possibly related to this organisation

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

DUMY-RIPE DUMY-RIPE MNT-TBTNET tr-taskaya41-1-mnt