TCLNET
Data as of 2026-08-30
Handle
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 |
| IPv6 | 2 prefixes (largest 2001:7f8:33::a120:3900:1/128) |
| Cluster ID | 233787214 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| 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 · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.189.83.54/32 | TCLNET | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:33::a120:3900:1/128 | TCLNET | PEERINGDB | ASSIGNED | ● high |
| 2602:fed2:fff:ffff:6::2d/128 | TCLNET | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(1 of 3)
No discrepancies found among checked blocks.
NIC Handles
AS203900