Global Secure Layer
Cluster stats
Netblocks152
All fragments 5,232 blocks across 739 clusters
Cluster ID193381643
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 (152)

showing 50 of 152 — see all⬇ export CSV
CIDR Org name Registry Status Confidence
5.57.81.11/32 Global Secure Layer PEERINGDB ASSIGNED ● high
27.106.192.137/32 Global Secure Layer PEERINGDB ASSIGNED ● high
27.111.229.213/32 Global Secure Layer PEERINGDB ASSIGNED ● high
31.44.187.33/32 Global Secure Layer PEERINGDB ASSIGNED ● high
36.255.57.100/32 Global Secure Layer PEERINGDB ASSIGNED ● high
43.243.21.82/32 Global Secure Layer PEERINGDB ASSIGNED ● high
45.127.172.130/32 Global Secure Layer PEERINGDB ASSIGNED ● high
64.191.234.85/32 Global Secure Layer PEERINGDB ASSIGNED ● high
80.81.197.29/32 Global Secure Layer PEERINGDB ASSIGNED ● high
80.249.214.204/32 Global Secure Layer PEERINGDB ASSIGNED ● high
101.97.43.7/32 Global Secure Layer PEERINGDB ASSIGNED ● high
101.203.74.78/32 Global Secure Layer PEERINGDB ASSIGNED ● high
101.203.89.127/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.16.102.165/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.94.93.19/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.94.95.25/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.136.101.14/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.136.102.44/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.136.103.19/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.158.187.146/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.180.190.6/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.203.158.178/32 Global Secure Layer PEERINGDB ASSIGNED ● high
103.231.152.170/32 Global Secure Layer PEERINGDB ASSIGNED ● high
109.239.136.115/32 Global Secure Layer PEERINGDB ASSIGNED ● high
139.150.100.140/32 Global Secure Layer PEERINGDB ASSIGNED ● high
149.112.11.59/32 Global Secure Layer PEERINGDB ASSIGNED ● high
149.112.27.1/32 Global Secure Layer PEERINGDB ASSIGNED ● high
183.177.61.55/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.0.14.74/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.14.161/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.22.14/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.32.72/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.47.74/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.86.21/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.102.150/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.104.144/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.106.69/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.112.124/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.153.62/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.160.191/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.171.28/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.191.16/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.192.77/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.208.232/32 Global Secure Layer PEERINGDB ASSIGNED ● high
185.1.210.227/32 Global Secure Layer PEERINGDB ASSIGNED ● high
193.27.37.176/32 Global Secure Layer PEERINGDB ASSIGNED ● high
193.110.224.138/32 Global Secure Layer PEERINGDB ASSIGNED ● high
193.169.199.91/32 Global Secure Layer PEERINGDB ASSIGNED ● high
193.239.117.133/32 Global Secure Layer PEERINGDB ASSIGNED ● high
195.42.145.40/32 Global Secure Layer PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS137409