Is Zscaler Cloud down?
Current Zscaler Cloud status is WARN

We checked the official Zscaler Cloud Status Page 49 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Get notified when it's back up with dashboards and notifications

Recent Zscaler Cloud Outages and Issues

Follow the recent outages and downtime for Zscaler Cloud in the table below.

Start Time

Type

Length

Message

Details

March 23, 2024 14:26 UTC

WARN

ongoing

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

See more
Start Time

March 23, 2024 14:26 UTC

Type WARN
Affected Components

zscaler.net - Core Cloud Services - Authentication

zscaler.net - Core Cloud Services - Traffic Forwarding

zscaler.net - Core Cloud Services - Zscaler Client connector

zscaler.net - Core Cloud Services - Zscaler Cloud Connector Portal

zscaler.net - Core Cloud Services - Admin UI

zscaler.net - Core Cloud Services - Partner Admin UI

zscaler.net - Core Cloud Services - Source IP Anchoring (SIPA)

Message

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

Details

EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...

March 23, 2024 09:01 UTC

WARN

about 5 hours

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Zscaler Client connector: Traffic Forwarding Issue, Core Cloud Services - Zscaler Cloud Connector Portal: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Admin UI: Traffic Forwarding Issue, Core Cloud Services - Partner Admin UI: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

See more
Start Time

March 23, 2024 09:01 UTC

Type WARN
Affected Components

zscaler.net - Core Cloud Services - Partner Admin UI

Message

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Zscaler Client connector: Traffic Forwarding Issue, Core Cloud Services - Zscaler Cloud Connector Portal: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Admin UI: Traffic Forwarding Issue, Core Cloud Services - Partner Admin UI: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

Details

EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., Core Cloud Services - Traffic Forwarding: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Zscaler Client connector: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Zscaler Cloud Connector Portal: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Authentication: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Admin UI: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Partner Admin UI: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Source IP Anchoring (SIPA): We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...

March 23, 2024 08:37 UTC

WARN

25 minutes

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Zscaler Client connector: Traffic Forwarding Issue, Core Cloud Services - Zscaler Cloud Connector Portal: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Admin UI: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

See more
Start Time

March 23, 2024 08:37 UTC

Type WARN
Affected Components

zscaler.net - Core Cloud Services - Zscaler Client connector

zscaler.net - Core Cloud Services - Zscaler Cloud Connector Portal

zscaler.net - Core Cloud Services - Admin UI

Message

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Zscaler Client connector: Traffic Forwarding Issue, Core Cloud Services - Zscaler Cloud Connector Portal: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Admin UI: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

Details

EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., Core Cloud Services - Traffic Forwarding: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Zscaler Client connector: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Zscaler Cloud Connector Portal: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Authentication: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Admin UI: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Source IP Anchoring (SIPA): We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...

March 23, 2024 08:16 UTC

WARN

21 minutes

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

See more
Start Time

March 23, 2024 08:16 UTC

Type WARN
Affected Components

zscaler.net - Core Cloud Services - Authentication

zscaler.net - Core Cloud Services - Source IP Anchoring (SIPA)

Message

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

Details

EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., Core Cloud Services - Traffic Forwarding: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Authentication: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Source IP Anchoring (SIPA): We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...

March 23, 2024 07:16 UTC

WARN

about 1 hour

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

See more
Start Time

March 23, 2024 07:16 UTC

Type WARN
Affected Components

zscaler.net - Core Cloud Services - Traffic Forwarding

Message

EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

Details

EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., Core Cloud Services - Traffic Forwarding: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...

2024-03-23 20:35:15 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-03-23 20:35:15 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-03-23 20:35:15 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-03-23 20:35:15 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-03-23 20:35:15 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Zscaler Cloud History

StatusGator has over 4 years of Zscaler Cloud status history.

Zscaler Cloud Components and Services

View details of the current Zscaler Cloud status below.

Name

Status

Details

Core Cloud Services - 3rd Party Integration

UP See more

Core Cloud Services - Admin UI

UP See more

Core Cloud Services - Alerting

UP See more

Core Cloud Services - Alerts

UP See more

Core Cloud Services - App Routing

UP See more

Core Cloud Services - Authentication

UP See more

Core Cloud Services - Client Forwarding

UP See more

Core Cloud Services - Cloud Account Onboarding

UP See more

Core Cloud Services - Cloud Browser Isolation

UP See more

Core Cloud Services - Config Distribution

UP See more

Core Cloud Services - Content Delivery

UP See more

Core Cloud Services - Control

UP See more

Core Cloud Services - Dashboard

UP See more

Core Cloud Services - Dashboards, Reports and UI access

UP See more

Core Cloud Services - Data Ingestion

UP See more

Core Cloud Services - Diagnostics

UP See more

Core Cloud Services - DNS

UP See more

Core Cloud Services - Email Notifications

UP See more

Core Cloud Services - Enrollment

UP See more

Core Cloud Services - Executive Reports

UP See more

Core Cloud Services - IaC Scanning

UP See more

Core Cloud Services - Investigation

UP See more

Core Cloud Services - Nanolog

UP See more

Core Cloud Services - PAC

UP See more

Core Cloud Services - Partner Admin UI

UP See more

Core Cloud Services - Policy Evaluation

UP See more

Core Cloud Services - Scheduled Reports

UP See more

Core Cloud Services - SCIM auto-provisioning

UP See more

Core Cloud Services - Security

UP See more

Core Cloud Services - Source IP Anchoring (SIPA)

UP See more

Core Cloud Services - SSO and User Management

UP See more

Core Cloud Services - Traffic Forwarding

UP See more

Core Cloud Services - Vulnerability Scanning

UP See more

Core Cloud Services - Workload Segmentation Admin Portal

UP See more

Core Cloud Services - Workload Segmentation API Gateway

UP See more

Core Cloud Services - Workload Segmentation Cloud

UP See more

Core Cloud Services - Workload Segmentation Event Exporter

UP See more

Core Cloud Services - Zscaler Client connector

UP See more

Core Cloud Services - Zscaler Client Connector Admin

UP See more

Core Cloud Services - Zscaler Cloud Connector Portal

UP See more

Zscaler Cloud Americas - Atlanta II

UP See more

Zscaler Cloud Americas - Bogota I

UP See more

Zscaler Cloud Americas - Boston I

UP See more

Zscaler Cloud Americas - Buenos Aires I

UP See more

Zscaler Cloud Americas - Chicago

UP See more

Zscaler Cloud Americas - Chicago I

UP See more

Zscaler Cloud Americas - Chicago II

UP See more

Zscaler Cloud Americas - Cleveland II

UP See more

Zscaler Cloud Americas - Dallas I

UP See more

Zscaler Cloud Americas - Denver III

UP See more

Zscaler Cloud Americas - Los Angeles

UP See more

Zscaler Cloud Americas - Los Angeles I

UP See more

Zscaler Cloud Americas - Mexico I

UP See more

Zscaler Cloud Americas - Miami III

UP See more

Zscaler Cloud Americas - Montreal I

UP See more

Zscaler Cloud Americas - New York III

UP See more

Zscaler Cloud Americas - New York IV

UP See more

Zscaler Cloud Americas - Nuevo Laredo I

UP See more

Zscaler Cloud Americas - Oregon II

UP See more

Zscaler Cloud Americas - Portland II

UP See more

Zscaler Cloud Americas - San Francisco IV

UP See more

Zscaler Cloud Americas - Santiago I

UP See more

Zscaler Cloud Americas - Sao Paulo

UP See more

Zscaler Cloud Americas - Sao Paulo II

UP See more

Zscaler Cloud Americas - Sao Paulo IV

UP See more

Zscaler Cloud Americas - Seattle

UP See more

Zscaler Cloud Americas - Toronto III

UP See more

Zscaler Cloud Americas - Vancouver I

UP See more

Zscaler Cloud Americas - Washington DC

UP See more

Zscaler Cloud APAC - Auckland

UP See more

Zscaler Cloud APAC - Auckland II

UP See more

Zscaler Cloud APAC - Beijing

UP See more

Zscaler Cloud APAC - Beijing II

UP See more

Zscaler Cloud APAC - Beijing III

UP See more

Zscaler Cloud APAC - Canberra I

UP See more

Zscaler Cloud APAC - Chennai

UP See more

Zscaler Cloud APAC - Chennai II

UP See more

Zscaler Cloud APAC - Hong Kong III

UP See more

Zscaler Cloud APAC - Hyderabad I

UP See more

Zscaler Cloud APAC - Kuala Lumpur I

UP See more

Zscaler Cloud APAC - Melbourne II

UP See more

Zscaler Cloud APAC - Mumbai IV

UP See more

Zscaler Cloud APAC - Mumbai V

UP See more

Zscaler Cloud APAC - Mumbai VI

UP See more

Zscaler Cloud APAC - New Delhi I

UP See more

Zscaler Cloud APAC - Osaka I

UP See more

Zscaler Cloud APAC - Osaka II

UP See more

Zscaler Cloud APAC - Seoul

UP See more

Zscaler Cloud APAC - Seoul I

UP See more

Zscaler Cloud APAC - Seoul II

UP See more

Zscaler Cloud APAC - Shanghai

UP See more

Zscaler Cloud APAC - Shanghai I

UP See more

Zscaler Cloud APAC - Shanghai II

UP See more

Zscaler Cloud APAC - Shanghai IV

UP See more

Zscaler Cloud APAC - Singapore III

UP See more

Zscaler Cloud APAC - Singapore IV

UP See more

Zscaler Cloud APAC - Sydney III

UP See more

Zscaler Cloud APAC - Sydney IV

UP See more

Zscaler Cloud APAC - Taipei

UP See more

Zscaler Cloud APAC - Taipei II

UP See more

Zscaler Cloud APAC - Tianjin

UP See more

Zscaler Cloud APAC - Tokyo III

UP See more

Zscaler Cloud APAC - Tokyo IV

UP See more

Zscaler Cloud EMEA - Amsterdam II

UP See more

Zscaler Cloud EMEA - Brussels II

UP See more

Zscaler Cloud EMEA - Capetown

WARN See more

Zscaler Cloud EMEA - Cape Town III

UP See more

Zscaler Cloud EMEA - Capetown IV

UP See more

Zscaler Cloud EMEA - Copenhagen II

UP See more

Zscaler Cloud EMEA - Dublin II

UP See more

Zscaler Cloud EMEA - Dusseldorf I

UP See more

Zscaler Cloud EMEA - Frankfurt IV

UP See more

Zscaler Cloud EMEA - Frankfurt V

UP See more

Zscaler Cloud EMEA - Frankfurt VI

UP See more

Zscaler Cloud EMEA - Helsinki I

UP See more

Zscaler Cloud EMEA - Ireland

UP See more

Zscaler Cloud EMEA - Johannesburg II

WARN See more

Zscaler Cloud EMEA - Johannesburg III

WARN See more

Zscaler Cloud EMEA - Lagos

UP See more

Zscaler Cloud EMEA - Lagos II

UP See more

Zscaler Cloud EMEA - London III

UP See more

Zscaler Cloud EMEA - London IV

UP See more

Zscaler Cloud EMEA - London V

UP See more

Zscaler Cloud EMEA - Madrid III

UP See more

Zscaler Cloud EMEA - Manchester I

WARN See more

Zscaler Cloud EMEA - Marseille I

UP See more

Zscaler Cloud EMEA - Milan III

UP See more

Zscaler Cloud EMEA - Moscow III

UP See more

Zscaler Cloud EMEA - Munich I

UP See more

Zscaler Cloud EMEA - Oslo III

UP See more

Zscaler Cloud EMEA - Paris II

UP See more

Zscaler Cloud EMEA - Rouen I

UP See more

Zscaler Cloud EMEA - Stockholm III

WARN See more

Zscaler Cloud EMEA - Stockholm IV

UP See more

Zscaler Cloud EMEA - Tel Aviv

UP See more

Zscaler Cloud EMEA - Tel Aviv I

UP See more

Zscaler Cloud EMEA - Vienna I

UP See more

Zscaler Cloud EMEA - Warsaw II

UP See more

Zscaler Cloud EMEA - Zurich

UP See more

Zscaler Cloud EMEA - Zurich I

UP See more

Zscaler Cloud Middle East - Dubai I

UP See more

5 status changes in the last 24 hours

Zscaler Cloud status, last 24 hours:

9:00 PM
3:00 AM
9:00 AM
3:00 PM
9:00 PM
9:00 PM
9:00 AM
9:00 PM
  • Up: 11 hours

  • Warn: 13 hours

  • Down: 0 minutes

  • Maintenance: 0 minutes

Zscaler Cloud Outage and Status History

We've been monitoring Zscaler Cloud outages since October 7, 2019.
Here's the history of service outages we've observed from the Zscaler Cloud Status Page:

  • Up

  • Warn

  • Down

  • Maintenance

Instant enriched data from
3,570 status pages

About Our Zscaler Cloud Status Page Integration

Zscaler Cloud is a Cloud Infrastructure and Security solution that StatusGator has been monitoring since October 2019. Over the past over 4 years, we have collected data on on more than 1,750 outages that affected Zscaler Cloud users. When Zscaler Cloud publishes downtime on their status page, they do so across 513 components and 11 groups using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.

More than 200 StatusGator users monitor Zscaler Cloud to get notified when it's down, is under maintenance, or has an outage. This makes it one of the most popular cloud infrastructure services monitored on our platform. We've sent more than 6,400 notifications to our users about Zscaler Cloud incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Zscaler Cloud is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Zscaler Cloud is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Zscaler Cloud posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Zscaler Cloud enters a pre-planned maintenance window, keeping you up to date.

Zscaler Cloud does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate Zscaler Cloud maintenance events into your unified calendar.

When Zscaler Cloud posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Zscaler Cloud has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Zscaler Cloud has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Zscaler Cloud Down?

Are you experiencing issues with Zscaler Cloud? Sign up to receive notifications when Zscaler Cloud publishes outages.

Zscaler Cloud Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,570 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Zscaler Cloud?

Sign up for StatusGator and see all historical information about Zscaler Cloud outages and performance issues. Get free, instant notifications when Zscaler Cloud goes down.