April 15, 2024 00:11 UTC
|
WARN
|
less than a minute
|
EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs
|
See more
Start Time
April 15, 2024 00:11 UTC
|
Type
WARN
|
Affected Components
zscalerone.net - EMEA - Capetown
zscalerone.net - EMEA - Johannesburg II
zscalertwo.net - EMEA - Capetown
zscalertwo.net - EMEA - Johannesburg II
zscalertwo.net - EMEA - Johannesburg III
zscloud.net - EMEA - Capetown
zscloud.net - EMEA - Johannesburg II
zscalerthree.net - EMEA - Johannesburg II
zscalerthree.net - EMEA - Johannesburg III
zscaler.net - EMEA - Capetown
zscaler.net - EMEA - Johannesburg II
zscaler.net - EMEA - Johannesburg III
zscloud.net - EMEA - Johannesburg III
|
Message
EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs
|
Details
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 - 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 - 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 - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ...
|
|
April 15, 2024 00:11 UTC
|
WARN
|
ongoing
|
EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs
|
See more
Start Time
April 15, 2024 00:11 UTC
|
Type
WARN
|
Affected Components
zscalerone.net - EMEA - Capetown
zscalerone.net - EMEA - Johannesburg II
zscalertwo.net - EMEA - Capetown
zscalertwo.net - EMEA - Johannesburg II
zscalertwo.net - EMEA - Johannesburg III
zscloud.net - EMEA - Capetown
zscloud.net - EMEA - Johannesburg II
zscalerthree.net - EMEA - Johannesburg II
zscalerthree.net - EMEA - Johannesburg III
zscaler.net - EMEA - Capetown
zscaler.net - EMEA - Johannesburg II
zscaler.net - EMEA - Johannesburg III
zscloud.net - EMEA - Johannesburg III
|
Message
EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs
|
Details
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 - 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 - 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 - 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 ...
|
|
March 15, 2024 08:56 UTC
|
WARN
|
less than a minute
|
APAC - Chennai II: Chennai II Datacenter Issue, APAC - Singapore IV: Singapore IV Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
See more
Start Time
March 15, 2024 08:56 UTC
|
Type
WARN
|
Affected Components
zscaler.net - EMEA - Johannesburg III
zscalertwo.net - EMEA - Johannesburg III
zscalerthree.net - EMEA - Johannesburg III
zscloud.net - EMEA - Johannesburg III
|
Message
APAC - Chennai II: Chennai II Datacenter Issue, APAC - Singapore IV: Singapore IV Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
Details
APAC - Chennai II: Zscaler has detected an issue with our Chennai II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For more information, please check our ..., APAC - Singapore IV: We are investigating an issue with our Singapore IV datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...
|
|
March 15, 2024 08:56 UTC
|
WARN
|
about 1 month
|
APAC - Chennai II: Chennai II Datacenter Issue, APAC - Singapore IV: Singapore IV Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
See more
Start Time
March 15, 2024 08:56 UTC
|
Type
WARN
|
Affected Components
zscaler.net - EMEA - Johannesburg III
zscalertwo.net - EMEA - Johannesburg III
zscalerthree.net - EMEA - Johannesburg III
zscloud.net - EMEA - Johannesburg III
|
Message
APAC - Chennai II: Chennai II Datacenter Issue, APAC - Singapore IV: Singapore IV Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted
|
Details
APAC - Chennai II: Zscaler has detected an issue with our Chennai II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For more information, please check our ..., APAC - Singapore IV: We are investigating an issue with our Singapore IV datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...
|
|
December 22, 2023 06:16 UTC
|
WARN
|
less than a minute
|
APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, and APAC - Shanghai II: Shanghai II Datacenter Issue
|
See more
Start Time
December 22, 2023 06:16 UTC
|
Type
WARN
|
Affected Components
zscalertwo.net - EMEA - Johannesburg III
zscloud.net - EMEA - Johannesburg III
zscaler.net - EMEA - Capetown IV
zscaler.net - EMEA - Johannesburg III
zscalertwo.net - EMEA - Capetown IV
zscloud.net - EMEA - Capetown IV
zscalerthree.net - EMEA - Capetown IV
zscalerthree.net - EMEA - Johannesburg III
|
Message
APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, and APAC - Shanghai II: Shanghai II Datacenter Issue
|
Details
APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., EMEA - London V: We are currently investigating an issue that seems to be related to a Microsoft Geolocation Issue that may be impacting Azure , Office and other Microsoft login services that have ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., EMEA - London V: We are currently investigating an issue that seems to be related to a Microsoft Geolocation Issue that may be impacting Azure , Office and other Microsoft login services that have ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., EMEA - London V: We are currently investigating an issue that seems to be related to a Microsoft Geolocation Issue that may be impacting Azure , Office and other Microsoft login services that have ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., EMEA - London V: We are currently investigating an issue that seems to be related to a Microsoft Geolocation Issue that may be impacting Azure , Office and other Microsoft login services that have ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., and APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ...
|
|
2024-04-15 04:49:45 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-15 04:49:45 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-15 04:49:45 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-15 04:49:45 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-15 04:49:45 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|