|
August 17, 2023 13:41 UTC
|
WARN
|
ongoing
|
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, and EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue
|
See more
Start Time
August 17, 2023 13:41 UTC
|
|
Type
WARN
|
Affected Components
zpccloud.net - Core Cloud Services - IaC Scanning
|
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, and EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown 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 ..., and 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 ...
|
|
|
August 17, 2023 12:16 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 - 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, and Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue
|
See more
Start Time
August 17, 2023 12:16 UTC
|
|
Type
WARN
|
Affected Components
eu.zpccloud.net - Core Cloud Services - IaC Scanning
|
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, and Core Cloud Services - IaC Scanning: Zscaler Posture Control 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 ..., and Core Cloud Services - IaC Scanning: We are currently investigating an issue with Zscaler Posture Control on zpccloud.net Vulnerability Scanning for Azure workloads is not working as expected currently, team is working with Microsoft to fix ...
|
|
|
August 16, 2023 18:57 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, Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue, and Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue
|
See more
Start Time
August 16, 2023 18:57 UTC
|
|
Type
WARN
|
Affected Components
zpccloud.net - Core Cloud Services - IaC Scanning
eu.zpccloud.net - Core Cloud Services - IaC Scanning
|
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, Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue, and Core Cloud Services - IaC Scanning: Zscaler Posture Control 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 ..., Core Cloud Services - IaC Scanning: We are currently investigating an issue with Zscaler Posture Control on zpccloud.net Vulnerability Scanning for Azure workloads is not working as expected currently, team is working with Microsoft to fix ..., and Core Cloud Services - IaC Scanning: We are investigating an issue with Zscaler Posture Control on our eu.zpccloud.net Cloud. Vulnerability Scanning for Azure workloads is not working as expected currently, team is working with Microsoft to ...
|
|
|
August 16, 2023 18:57 UTC
|
WARN
|
about 17 hours
|
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, Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue, and Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue
|
See more
Start Time
August 16, 2023 18:57 UTC
|
|
Type
WARN
|
Affected Components
zpccloud.net - Core Cloud Services - IaC Scanning
eu.zpccloud.net - Core Cloud Services - IaC Scanning
|
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, Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue, and Core Cloud Services - IaC Scanning: Zscaler Posture Control 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 ..., Core Cloud Services - IaC Scanning: We are currently investigating an issue with Zscaler Posture Control on zpccloud.net Vulnerability Scanning for Azure workloads is not working as expected currently, team is working with Microsoft to fix ..., and Core Cloud Services - IaC Scanning: We are investigating an issue with Zscaler Posture Control on our eu.zpccloud.net Cloud. Vulnerability Scanning for Azure workloads is not working as expected currently, team is working with Microsoft to ...
|
|
|
February 28, 2023 06:27 UTC
|
WARN
|
6 months
|
Africa - Capetown: Capetown Datacenter Issue, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, Africa - Capetown: Capetown Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, US & Canada - Seattle: Seattle Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, and Core Cloud Services - Workload Segmentation Cloud: Zscaler Workload Segmentation Issue
|
See more
Start Time
February 28, 2023 06:27 UTC
|
|
Type
WARN
|
Affected Components
zpccloud.net - Core Cloud Services - IaC Scanning
|
Message
Africa - Capetown: Capetown Datacenter Issue, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, Africa - Capetown: Capetown Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, US & Canada - Seattle: Seattle Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, and Core Cloud Services - Workload Segmentation Cloud: Zscaler Workload Segmentation Issue
|
Details
Africa - Capetown: We are investigating an issue with our Capetown datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ..., Asia - 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 ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Europe - Frankfurt VI: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Dusseldorf I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Frankfurt IV: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - 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., Europe - Munich I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Vienna I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Core Cloud Services - Traffic Forwarding: We are aware of submarine cable fault that has impacted SINGTEL. As a result of this, customers having traffic from US to Asia or vice-versa via SINGTEL Singapore may experience ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Europe - Frankfurt VI: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Dusseldorf I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Frankfurt IV: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - 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., Europe - Munich I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Vienna I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Core Cloud Services - Traffic Forwarding: We are aware of submarine cable fault that has impacted SINGTEL. As a result of this, customers having traffic from US to Asia or vice-versa via SINGTEL Singapore may experience ..., Africa - Capetown: We are investigating an issue with our Capetown datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Europe - Frankfurt VI: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Dusseldorf I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Frankfurt IV: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - 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., Europe - Munich I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Vienna I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Core Cloud Services - Traffic Forwarding: We are aware of submarine cable fault that has impacted SINGTEL. As a result of this, customers having traffic from US to Asia or vice-versa via SINGTEL Singapore may experience ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Europe - Frankfurt VI: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Dusseldorf I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Frankfurt IV: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - 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., Europe - Munich I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - Vienna I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Core Cloud Services - Traffic Forwarding: We are aware of submarine cable fault that has impacted SINGTEL. As a result of this, customers having traffic from US to Asia or vice-versa via SINGTEL Singapore may experience ..., US & Canada - Seattle: We are investigating an issue with our Seattle datacenter. We are investigating periods of slowness and/or increased latency. For additional information please reach out to Zscaler Support referencing this incident, ..., Europe - Frankfurt IV: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., Europe - 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., Europe - Munich I: We are investigating an issue with our Dusseldorf I, Frankfurt IV, Munich I, Vienna I, Frankfurt VI datacenters. We are investigating periods of slowness and/or increased latency. For additional information ..., and Core Cloud Services - Workload Segmentation Cloud: We are working on an issue with the audit event pipeline. Audit events may appear delayed. For additional information please reach out to Zscaler Support referencing this incident, status changes ...
|
|
|
2024-04-27 03:23:02 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
|
2024-04-27 03:23:02 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
|
2024-04-27 03:23:02 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
|
2024-04-27 03:23:02 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
|
2024-04-27 03:23:02 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
