April 11, 2024 02:51 UTC
|
WARN
|
ongoing
|
EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs
|
See more
Start Time
April 11, 2024 02:51 UTC
|
Type
WARN
|
Affected Components
private.zscaler.com - APAC - Osaka I
|
Message
EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs
|
Details
EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., and EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ...
|
|
April 10, 2024 03:41 UTC
|
WARN
|
about 23 hours
|
EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and APAC - Osaka I: Osaka I Datacenter Issue
|
See more
Start Time
April 10, 2024 03:41 UTC
|
Type
WARN
|
Affected Components
private.zscaler.com - APAC - Osaka I
|
Message
EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and APAC - Osaka I: Osaka I Datacenter Issue
|
Details
EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., and APAC - Osaka I: Zscaler has detected an issue with our Osaka I datacenter. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If you need further assistance, contact Zscaler ...
|
|
August 29, 2023 02:36 UTC
|
WARN
|
8 months
|
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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) datacenter issue, and EMEA - Marseille I: Marseille I (MRS1) datacenter issue
|
See more
Start Time
August 29, 2023 02:36 UTC
|
Type
WARN
|
Affected Components
zscloud.net - APAC - Osaka I
|
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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) datacenter issue, and EMEA - Marseille I: Marseille I (MRS1) 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 - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ..., 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 - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ..., 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 - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ..., 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 - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ..., and EMEA - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ...
|
|
August 29, 2023 01:36 UTC
|
WARN
|
about 1 hour
|
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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) datacenter issue, APAC - Osaka I: Osaka I 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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) datacenter issue, and EMEA - Marseille I: Marseille I (MRS1) datacenter issue
|
See more
Start Time
August 29, 2023 01:36 UTC
|
Type
WARN
|
Affected Components
zscloud.net - APAC - Osaka I
|
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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) datacenter issue, APAC - Osaka I: Osaka I 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 - Marseille I: Marseille I (MRS1) 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 - Marseille I: Marseille I (MRS1) datacenter issue, and EMEA - Marseille I: Marseille I (MRS1) 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 - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ..., 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 - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ..., APAC - Osaka I: Zscaler has detected an issue with our Osaka I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they ..., 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 - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ..., 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 - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ..., and EMEA - Marseille I: Zscaler is aware of a fibercut event in the area of Marseille. There is no expected service impacts to Zscaler services in Marseille I (MRS1) datacenter. Zscaler is working with ...
|
|
April 13, 2023 01:01 UTC
|
WARN
|
less than a minute
|
APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue
|
See more
Start Time
April 13, 2023 01:01 UTC
|
Type
WARN
|
Affected Components
zscaler.net - APAC - Osaka I
zscalertwo.net - APAC - Osaka I
zscalerthree.net - APAC - Osaka I
zscloud.net - APAC - Osaka I
|
Message
APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue
|
Details
APAC - Beijing III: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - 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.
|
|
2024-04-25 23:32:53 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-25 23:32:53 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-25 23:32:53 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-25 23:32:53 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-25 23:32:53 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|