Tencent-CN
Handle
Cluster stats
| Netblocks | 16 |
| Cluster ID | 208802298 |
| 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 | |
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 43.249.135.50/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 43.249.135.54/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.40.222.82/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.40.222.86/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.154.40.40/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.154.40.41/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.168.98.1/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.168.98.2/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.183.26.17/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.183.26.18/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.216.40.16/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 103.216.40.18/32 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 2400:5f60:0:8::17/128 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 2400:5f60:0:8::18/128 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 2404:e780:f872:a:1:0:b022:1/128 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
| 2404:e780:f872:a:1:0:b022:3/128 | Tencent-CN | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
62.5%
of checked blocks have valid RPKI ROA coverage
(10 of 16)
No discrepancies found among checked blocks.
NIC Handles
AS45090