|
August 22, 2023 04:16 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, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Core Cloud Services - Alerting: Reporting and Logging Issue, and Core Cloud Services - Content Delivery: Reporting and Logging Issue
|
See more
Start Time
August 22, 2023 04:16 UTC
|
|
Type
WARN
|
Affected Components
zscalertwo.net - Americas - Chicago
|
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 - Alerting: Reporting and Logging Issue, and Core Cloud Services - Content Delivery: Reporting and Logging 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 - Alerting: We are investigating an issue with our zdxcloud.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ..., and Core Cloud Services - Content Delivery: We are investigating an issue with our zdxcloud.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ...
|
|
|
August 21, 2023 16:46 UTC
|
WARN
|
about 12 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, Americas - Chicago: Chicago 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 - Alerting: Reporting and Logging Issue, and Core Cloud Services - Content Delivery: Reporting and Logging Issue
|
See more
Start Time
August 21, 2023 16:46 UTC
|
|
Type
WARN
|
Affected Components
zscalertwo.net - Americas - Chicago
|
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, Americas - Chicago: Chicago 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 - Alerting: Reporting and Logging Issue, and Core Cloud Services - Content Delivery: Reporting and Logging 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 ..., Americas - Chicago: Zscaler has detected an issue with our Chicago datacenter. We are investigating periods of slowness and/or increased latency. For additional information please reach out to Zscaler Support referencing this incident, ..., 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 - Alerting: We are investigating an issue with our zdxcloud.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ..., and Core Cloud Services - Content Delivery: We are investigating an issue with our zdxcloud.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ...
|
|
|
July 13, 2023 18:11 UTC
|
WARN
|
about 1 month
|
EMEA - Johannesburg II: Johannesburg II Datacenter Issue, APAC - Mumbai IV: Mumbai IV Datacenter Issue, and EMEA - Johannesburg II: Johannesburg II Datacenter Issue
|
See more
Start Time
July 13, 2023 18:11 UTC
|
|
Type
WARN
|
Affected Components
zscalerthree.net - Americas - Boston I
zscalerthree.net - Americas - Miami III
zscalerthree.net - Americas - New York III
zscalerthree.net - Americas - Vancouver I
zscalerthree.net - Americas - Washington DC
zscalerthree.net - Americas - Toronto III
zscalerthree.net - Americas - Atlanta II
zscalerthree.net - Americas - Chicago
|
Message
EMEA - Johannesburg II: Johannesburg II Datacenter Issue, APAC - Mumbai IV: Mumbai IV Datacenter Issue, and EMEA - Johannesburg II: Johannesburg II Datacenter Issue
|
Details
EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out ..., APAC - Mumbai IV: We are investigating an issue with our Mumbai IV datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out ..., and EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out ...
|
|
|
July 13, 2023 17:56 UTC
|
WARN
|
15 minutes
|
EMEA - Johannesburg II: Johannesburg II Datacenter Issue, Americas - Atlanta II: User Authentication Issues, Americas - Boston I: User Authentication Issues, Americas - Chicago: User Authentication Issues, Americas - Miami III: User Authentication Issues, Americas - New York III: User Authentication Issues, Americas - Toronto III: User Authentication Issues, Americas - Vancouver I: User Authentication Issues, Americas - Washington DC: User Authentication Issues, APAC - Mumbai IV: Mumbai IV Datacenter Issue, and EMEA - Johannesburg II: Johannesburg II Datacenter Issue
|
See more
Start Time
July 13, 2023 17:56 UTC
|
|
Type
WARN
|
Affected Components
zscalerthree.net - Americas - Miami III
zscalerthree.net - Americas - Toronto III
zscalerthree.net - Americas - Atlanta II
zscalerthree.net - Americas - Chicago
zscalerthree.net - Americas - Boston I
zscalerthree.net - Americas - New York III
zscalerthree.net - Americas - Vancouver I
zscalerthree.net - Americas - Washington DC
|
Message
EMEA - Johannesburg II: Johannesburg II Datacenter Issue, Americas - Atlanta II: User Authentication Issues, Americas - Boston I: User Authentication Issues, Americas - Chicago: User Authentication Issues, Americas - Miami III: User Authentication Issues, Americas - New York III: User Authentication Issues, Americas - Toronto III: User Authentication Issues, Americas - Vancouver I: User Authentication Issues, Americas - Washington DC: User Authentication Issues, APAC - Mumbai IV: Mumbai IV Datacenter Issue, and EMEA - Johannesburg II: Johannesburg II Datacenter Issue
|
Details
EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out ..., Americas - Atlanta II: We are investigating user authentication issues with our Atlanta II, Boston I, Chicago, Miami III, New York III, Toronto III, Vancouver I, Washington DC datacenters. For additional information please reach out to ..., Americas - Boston I: We are investigating user authentication issues with our Atlanta II, Boston I, Chicago, Miami III, New York III, Toronto III, Vancouver I, Washington DC datacenters. For additional information please reach out to ..., Americas - Chicago: We are investigating user authentication issues with our Atlanta II, Boston I, Chicago, Miami III, New York III, Toronto III, Vancouver I, Washington DC datacenters. For additional information please reach out to ..., Americas - Miami III: We are investigating user authentication issues with our Atlanta II, Boston I, Chicago, Miami III, New York III, Toronto III, Vancouver I, Washington DC datacenters. For additional information please reach out to ..., Americas - New York III: We are investigating user authentication issues with our Atlanta II, Boston I, Chicago, Miami III, New York III, Toronto III, Vancouver I, Washington DC datacenters. For additional information please reach out to ..., Americas - Toronto III: We are investigating user authentication issues with our Atlanta II, Boston I, Chicago, Miami III, New York III, Toronto III, Vancouver I, Washington DC datacenters. For additional information please reach out to ..., Americas - Vancouver I: We are investigating user authentication issues with our Atlanta II, Boston I, Chicago, Miami III, New York III, Toronto III, Vancouver I, Washington DC datacenters. For additional information please reach out to ..., Americas - Washington DC: We are investigating user authentication issues with our Atlanta II, Boston I, Chicago, Miami III, New York III, Toronto III, Vancouver I, Washington DC datacenters. For additional information please reach out to ..., APAC - Mumbai IV: We are investigating an issue with our Mumbai IV datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out ..., and EMEA - Johannesburg II: Zscaler has detected an issue with our Johannesburg II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out ...
|
|
