Zscaler AS53813

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks72
Registered in India (24) · Japan (14) · Australia (14) · Singapore (8) · Hong Kong (4) · Taiwan (2)
Cluster ID214582078
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 (72)

showing 50 of 72 — see all⬇ export CSV
CIDR Org name Registry Status Confidence
27.111.228.245/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
27.111.229.97/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
27.111.231.23/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
27.111.231.24/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
36.255.56.9/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
36.255.56.192/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
43.243.21.6/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
43.243.21.116/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.120.248.220/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.120.248.221/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.120.249.12/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.120.249.17/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.120.251.23/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.120.251.24/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.120.251.100/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.120.251.101/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.127.172.14/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.127.172.214/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.127.172.229/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
45.127.173.39/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
101.97.43.31/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
101.97.43.32/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
101.203.89.114/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
101.203.89.221/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
101.203.90.88/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
101.203.90.89/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.16.103.90/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.16.103.91/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.16.103.92/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.16.103.93/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.27.168.133/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.27.168.134/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.27.170.13/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.27.170.18/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.77.108.28/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.77.108.126/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.77.109.26/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.77.109.27/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.77.110.41/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.77.110.42/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.83.68.4/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.83.68.5/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.136.102.57/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.136.102.78/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.228.172.12/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.228.172.13/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.228.174.133/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
103.228.174.134/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
123.255.90.69/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high
123.255.90.70/32 Zscaler AS53813 PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS53813