September 08, 2023 15:11 UTC
|
WARN
|
3 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 15:11 UTC
|
Type
WARN
|
Affected Components
private.zscaler.com - Americas - Boston I
private.zscaler.com - Americas - Cleveland II
private.zscaler.com - Americas - Seattle
private.zscaler.com - Americas - Toronto III
private.zscaler.com - Americas - Washington DC
private.zscaler.com - APAC - Sydney IV
|
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 ...
|
|
May 31, 2023 20:06 UTC
|
WARN
|
3 months
|
APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Shanghai II: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue
|
See more
Start Time
May 31, 2023 20:06 UTC
|
Type
WARN
|
Affected Components
private.zscaler.com - Americas - Cleveland II
|
Message
APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Shanghai II: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue
|
Details
APAC - Kuala Lumpur I: We are investigating an issue with our Kuala Lumpur I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Shanghai II: We are investigating user authentication issue with our Shanghai II datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Beijing III: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai I: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., EMEA - Johannesburg III: We are investigating an issue with our Johannesburg III datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they ..., and EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory.
|
|
May 31, 2023 15:01 UTC
|
WARN
|
about 5 hours
|
APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Shanghai II: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, Americas - Cleveland II: Cleveland II Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue
|
See more
Start Time
May 31, 2023 15:01 UTC
|
Type
WARN
|
Affected Components
private.zscaler.com - Americas - Cleveland II
|
Message
APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Shanghai II: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, Americas - Cleveland II: Cleveland II Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue
|
Details
APAC - Kuala Lumpur I: We are investigating an issue with our Kuala Lumpur I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Shanghai II: We are investigating user authentication issue with our Shanghai II datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Americas - Cleveland II: We are investigating an issue with our Cleveland II datacenter. We are investigating intermittent connection timeouts. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., APAC - Beijing III: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai I: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., EMEA - Johannesburg III: We are investigating an issue with our Johannesburg III datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they ..., and EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory.
|
|