W8 Telecom
Cluster stats
| Netblocks | 16 |
| All fragments | 52 blocks across 2 clusters |
| Cluster ID | 193384937 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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
2 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-07-06
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.74.25/32 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 45.68.81.120/32 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 64.191.234.34/32 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 177.52.38.180/32 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 187.16.217.125/32 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 187.16.218.246/32 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 200.219.141.102/32 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 200.219.141.103/32 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:7:0:26:7469:2/128 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::217:125/128 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::218:246/128 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:2::53:120/128 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:5::102/128 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:5::103/128 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:6::26:7469/128 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:9::146:25/128 | W8 Telecom | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
87.5%
of checked blocks have valid RPKI ROA coverage
(14 of 16)
No discrepancies found among checked blocks.
NIC Handles
AS267469