March 18, 2024 13:41 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 - 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 - 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 - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
See more
Start Time
March 18, 2024 13:41 UTC
|
Type
WARN
|
Affected Components
zscaler.net - APAC - Chennai II
zscaler.net - APAC - Mumbai VI
|
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 - 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 - 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 - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, 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 - 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 - 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 - 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 ..., 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 15, 2024 09:46 UTC
|
WARN
|
3 days
|
APAC - Chennai II: Chennai II Datacenter Issue, APAC - Mumbai VI: Mumbai VI Datacenter Issue, APAC - Singapore IV: Singapore IV 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 - 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 - 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 - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
See more
Start Time
March 15, 2024 09:46 UTC
|
Type
WARN
|
Affected Components
zscaler.net - APAC - Mumbai VI
|
Message
APAC - Chennai II: Chennai II Datacenter Issue, APAC - Mumbai VI: Mumbai VI Datacenter Issue, APAC - Singapore IV: Singapore IV 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 - 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 - 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 - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
Details
APAC - Chennai II: Zscaler has detected an issue with our Chennai II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For more information, please check our ..., APAC - Mumbai VI: Zscaler has detected an issue with our Mumbai VI datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., APAC - Singapore IV: We are investigating an issue with our Singapore IV datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or ..., 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 - 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 - 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 - 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 ..., 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 ...
|
|
February 16, 2024 07:06 UTC
|
WARN
|
3 days
|
APAC - Chennai II: Chennai II, Mumbai VI Datacenter Issue and APAC - Mumbai VI: Chennai II, Mumbai VI Datacenter Issue
|
See more
Start Time
February 16, 2024 07:06 UTC
|
Type
WARN
|
Affected Components
zscaler.net - APAC - Chennai II
zscaler.net - APAC - Mumbai VI
|
Message
APAC - Chennai II: Chennai II, Mumbai VI Datacenter Issue and APAC - Mumbai VI: Chennai II, Mumbai VI Datacenter Issue
|
Details
APAC - Chennai II: Zscaler is investigating reports of an issue with our Chennai II, Mumbai VI datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. ... and APAC - Mumbai VI: Zscaler is investigating reports of an issue with our Chennai II, Mumbai VI datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. ...
|
|
December 06, 2023 16:56 UTC
|
WARN
|
2 months
|
APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, and Core Cloud Services - Content Delivery: Call Quality Monitoring Issue
|
See more
Start Time
December 06, 2023 16:56 UTC
|
Type
WARN
|
Affected Components
private.zscaler.com - APAC - Mumbai V
private.zscaler.com - APAC - Mumbai VI
private.zscaler.com - APAC - Chennai II
|
Message
APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, and Core Cloud Services - Content Delivery: Call Quality Monitoring Issue
|
Details
APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., and Core Cloud Services - Content Delivery: We are investigating an issue with Zoom Call Quality Monitoring on our Zscaler Digital Experience cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ...
|
|
December 04, 2023 15:01 UTC
|
WARN
|
2 days
|
APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Chennai II: Chennai II, Mumbai V, Mumbai VI Datacenter Issue, APAC - Mumbai V: Chennai II, Mumbai V, Mumbai VI Datacenter Issue, APAC - Mumbai VI: Chennai II, Mumbai V, Mumbai VI Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, Core Cloud Services - Content Delivery: Call Quality Monitoring Issue, and Core Cloud Services - Dashboards, Reports and UI access: Zscaler Posture Control Issue
|
See more
Start Time
December 04, 2023 15:01 UTC
|
Type
WARN
|
Affected Components
private.zscaler.com - APAC - Mumbai VI
private.zscaler.com - APAC - Chennai II
private.zscaler.com - APAC - Mumbai V
|
Message
APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, APAC - Chennai II: Chennai II, Mumbai V, Mumbai VI Datacenter Issue, APAC - Mumbai V: Chennai II, Mumbai V, Mumbai VI Datacenter Issue, APAC - Mumbai VI: Chennai II, Mumbai V, Mumbai VI Datacenter Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, Core Cloud Services - Content Delivery: Call Quality Monitoring Issue, and Core Cloud Services - Dashboards, Reports and UI access: Zscaler Posture Control Issue
|
Details
APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., APAC - Chennai II: Zscaler is investigating reports of an issue with our Chennai II, Mumbai V, Mumbai VI datacenter. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., APAC - Mumbai V: Zscaler is investigating reports of an issue with our Chennai II, Mumbai V, Mumbai VI datacenter. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., APAC - Mumbai VI: Zscaler is investigating reports of an issue with our Chennai II, Mumbai V, Mumbai VI datacenter. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., Core Cloud Services - Content Delivery: We are investigating an issue with Zoom Call Quality Monitoring on our Zscaler Digital Experience cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., and Core Cloud Services - Dashboards, Reports and UI access: We are currently investigating an issue with Zscaler Posture Control on zpccloud.net Dashboards, Reports and UI access. For additional information please reach out to Zscaler Support referencing this incident, status ...
|
|
2024-04-11 09:54:57 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-11 09:54:57 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-11 09:54:57 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-11 09:54:57 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-11 09:54:57 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|