April 03, 2024 05:26 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, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
See more
Start Time
April 03, 2024 05:26 UTC
|
Type
WARN
|
Affected Components
private.zscaler.com - Americas - Mexico 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 EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
Details
EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - 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 EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...
|
|
April 02, 2024 22:41 UTC
|
WARN
|
less than a minute
|
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, Americas - Mexico I: Mexico I Traffic Rerouted, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
See more
Start Time
April 02, 2024 22:41 UTC
|
Type
WARN
|
Affected Components
zscalerthree.net - Americas - Mexico I
zscaler.net - Americas - Mexico I
zscalertwo.net - Americas - Mexico 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, Americas - Mexico I: Mexico I Traffic Rerouted, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
Details
EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - 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 ..., Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...
|
|
April 02, 2024 22:41 UTC
|
WARN
|
about 7 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, Americas - Mexico I: Mexico I Traffic Rerouted, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
See more
Start Time
April 02, 2024 22:41 UTC
|
Type
WARN
|
Affected Components
zscalerthree.net - Americas - Mexico I
zscaler.net - Americas - Mexico I
zscalertwo.net - Americas - Mexico 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, Americas - Mexico I: Mexico I Traffic Rerouted, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
Details
EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - 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 ..., Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...
|
|
April 02, 2024 22:36 UTC
|
WARN
|
less than a minute
|
Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I Traffic Rerouted, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
See more
Start Time
April 02, 2024 22:36 UTC
|
Type
WARN
|
Affected Components
zscalerthree.net - Americas - Mexico I
zscaler.net - Americas - Mexico I
zscalertwo.net - Americas - Mexico I
|
Message
Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I Traffic Rerouted, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
Details
Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. ..., 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 ..., Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. ..., 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 ..., Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. ..., 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 ..., Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...
|
|
April 02, 2024 22:36 UTC
|
WARN
|
5 minutes
|
Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I Traffic Rerouted, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
See more
Start Time
April 02, 2024 22:36 UTC
|
Type
WARN
|
Affected Components
zscalerthree.net - Americas - Mexico I
zscaler.net - Americas - Mexico I
zscalertwo.net - Americas - Mexico I
|
Message
Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I 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, Americas - Mexico I: Mexico I Traffic Rerouted, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
Details
Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. ..., 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 ..., Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. ..., 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 ..., Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. ..., 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 ..., Americas - Mexico I: Zscaler has detected an issue with our Mexico I datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...
|
|
2024-04-25 20:16:56 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-25 20:16:56 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-25 20:16:56 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-25 20:16:56 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-25 20:16:56 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|