TCF Telecom

BGP inherited
Cluster stats
Netblocks8
All fragments 20 blocks across 7 clusters
Cluster ID206024620
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-13

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.92.32/32 TCF Telecom PEERINGDB ASSIGNED ● high
187.16.210.224/32 TCF Telecom PEERINGDB ASSIGNED ● high
187.16.216.144/32 TCF Telecom PEERINGDB ASSIGNED ● high
206.82.105.67/32 TCF Telecom PEERINGDB ASSIGNED ● high
2001:504:36:0:4:5d9:0:1/128 TCF Telecom PEERINGDB ASSIGNED ● high
2001:12f8::144/128 TCF Telecom PEERINGDB ASSIGNED ● high
2001:12f8::210:224/128 TCF Telecom PEERINGDB ASSIGNED ● high
2801:81:c0:1:4:5d9:0:1/128 TCF Telecom PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS263641