StatusGator
StatusGator
Sign In Sign Up
Sign In Sign Up

Is Zscaler Cloud Americas - Seattle down?
Current Zscaler Cloud Americas - Seattle status is UP

We checked the official Zscaler Cloud Americas - Seattle Status Page 4 min. 6 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Start a Free Trial

Recent Zscaler Cloud Americas - Seattle Outages and Issues

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

Start Time

Type

Length

Message

Details

September 08, 2023 22:36 UTC

WARN

less than a minute

EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue

 See more
Start Time

September 08, 2023 22:36 UTC

Type WARN
Affected Components

zscaler.net - Americas - Seattle

zscalertwo.net - Americas - Seattle

zscloud.net - Americas - Seattle

zscalerthree.net - Americas - Seattle
Message

EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue
Details

EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Boston I: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Cleveland II: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Seattle: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Toronto III: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Washington DC: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., and APAC - Sydney IV: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ...

September 08, 2023 22:36 UTC

WARN

2 days

EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue

 See more
Start Time

September 08, 2023 22:36 UTC

Type WARN
Affected Components

zscaler.net - Americas - Seattle

zscalertwo.net - Americas - Seattle

zscloud.net - Americas - Seattle

zscalerthree.net - Americas - Seattle
Message

EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue
Details

EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Boston I: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Cleveland II: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Seattle: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Toronto III: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Washington DC: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., and APAC - Sydney IV: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ...

September 08, 2023 22:31 UTC

WARN

less than a minute

Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue

 See more
Start Time

September 08, 2023 22:31 UTC

Type WARN
Affected Components

zscaler.net - Americas - Seattle

zscalertwo.net - Americas - Seattle

zscloud.net - Americas - Seattle
Message

Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue
Details

Americas - Seattle: We are investigating an issue with our Seattle datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Seattle: We are investigating an issue with our Seattle datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Seattle: We are investigating an issue with our Seattle datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Seattle: We are investigating an issue with our Seattle datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Boston I: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Cleveland II: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Seattle: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Toronto III: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Washington DC: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., and APAC - Sydney IV: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ...

September 08, 2023 22:31 UTC

WARN

5 minutes

Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue

 See more
Start Time

September 08, 2023 22:31 UTC

Type WARN
Affected Components

zscaler.net - Americas - Seattle

zscalertwo.net - Americas - Seattle

zscloud.net - Americas - Seattle
Message

Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue
Details

Americas - Seattle: We are investigating an issue with our Seattle datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Seattle: We are investigating an issue with our Seattle datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Seattle: We are investigating an issue with our Seattle datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Seattle: We are investigating an issue with our Seattle datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Boston I: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Cleveland II: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Seattle: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Toronto III: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Washington DC: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., and APAC - Sydney IV: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ...

September 08, 2023 22:16 UTC

WARN

less than a minute

EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue

 See more
Start Time

September 08, 2023 22:16 UTC

Type WARN
Affected Components

zscaler.net - Americas - Seattle

zscalertwo.net - Americas - Seattle
Message

EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Seattle: Seattle Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Americas - Boston I: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Cleveland II: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Seattle: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Toronto III: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, Americas - Washington DC: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue, and APAC - Sydney IV: Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC Datacenter Issue
Details

EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Seattle: We are investigating an issue with our Seattle datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., EMEA - Capetown IV: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Johannesburg II , Johannesburg III , Capetown and Capetown IV  datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Americas - Boston I: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Cleveland II: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Seattle: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Toronto III: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., Americas - Washington DC: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ..., and APAC - Sydney IV: Zscaler is investigating reports of an issue with our Sydney IV, Boston I, Cleveland II, Seattle, Toronto III, Washington DC datacenter. We are investigating intermittent connection timeouts. For additional information ...

2024-04-11 09:58:32 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

2024-04-11 09:58:32 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

2024-04-11 09:58:32 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

2024-04-11 09:58:32 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

2024-04-11 09:58:32 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

Sign Up for More Zscaler Cloud Americas - Seattle History

StatusGator has over 4 years of Zscaler Cloud Americas - Seattle status history.

Sign Up

No outages or status changes in the last 24 hours

Zscaler Cloud Americas - Seattle status, last 24 hours:

10:00 AM
4:00 PM
10:00 PM
4:00 AM
10:00 AM
10:00 AM
10:00 PM
10:00 AM

  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

  • Maintenance: 0 minutes

Zscaler Cloud Americas - Seattle Outage and Status History

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

April 2024

March 2024

February 2024

  • Up

  • Warn

  • Down

  • Maintenance

Solutions for Everyone
Education
  • Keep students and staff informed
  • Reduce ticket volume
  • Essential for remote learning

Learn more

DevOps
  • Shorten incident downtime
  • Unify maintenance schedules
  • Integrates with incident tools

Learn more

IT Teams
  • Reduce ticket volumes
  • Improve transparency
  • Shorten resolution times

Learn more

Instant enriched data from
3,580 status pages

About Our Zscaler Cloud Americas - Seattle Status Page Integration

Zscaler Cloud Americas - Seattle 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,805 outages that affected Zscaler Cloud Americas - Seattle users. When Zscaler Cloud Americas - Seattle publishes downtime on their status page, they do so across 518 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 Americas - Seattle 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,800 notifications to our users about Zscaler Cloud Americas - Seattle incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Zscaler Cloud Americas - Seattle 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 Americas - Seattle 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 Americas - Seattle posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Zscaler Cloud Americas - Seattle enters a pre-planned maintenance window, keeping you up to date.

Zscaler Cloud Americas - Seattle 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 Americas - Seattle maintenance events into your unified calendar.

When Zscaler Cloud Americas - Seattle 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 Americas - Seattle 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 Americas - Seattle 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 Americas - Seattle Down?

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

Sign Up

Zscaler Cloud Americas - Seattle 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,580 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 Americas - Seattle?

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