WN TELECOM
Cluster stats
Netblocks16
All fragments 25 blocks across 3 clusters
Cluster ID193386839
RegistryPEERINGDB
Customersfind 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

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.74.167/32 WN TELECOM PEERINGDB ASSIGNED ● high
45.68.82.96/32 WN TELECOM PEERINGDB ASSIGNED ● high
45.68.92.2/32 WN TELECOM PEERINGDB ASSIGNED ● high
45.184.144.107/32 WN TELECOM PEERINGDB ASSIGNED ● high
64.191.233.2/32 WN TELECOM PEERINGDB ASSIGNED ● high
187.16.210.249/32 WN TELECOM PEERINGDB ASSIGNED ● high
187.16.218.102/32 WN TELECOM PEERINGDB ASSIGNED ● high
200.219.139.33/32 WN TELECOM PEERINGDB ASSIGNED ● high
2001:504:0:7:0:26:8029:1/128 WN TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::210:249/128 WN TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::218:102/128 WN TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:2::54:96/128 WN TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:3::33/128 WN TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::146:167/128 WN TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:13::107/128 WN TELECOM PEERINGDB ASSIGNED ● high
2801:81:c0:1:0:ce66:0:1/128 WN 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 (12 of 16)
No discrepancies found among checked blocks.

NIC Handles

AS52838