March 23, 2024 14: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
March 23, 2024 14:26 UTC
|
Type
WARN
|
Affected Components
zscaler.net - Core Cloud Services - Authentication
zscaler.net - Core Cloud Services - Traffic Forwarding
zscaler.net - Core Cloud Services - Zscaler Client connector
zscaler.net - Core Cloud Services - Zscaler Cloud Connector Portal
zscaler.net - Core Cloud Services - Admin UI
zscaler.net - Core Cloud Services - Partner Admin UI
zscaler.net - Core Cloud Services - Source IP Anchoring (SIPA)
|
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 ...
|
|
March 23, 2024 08:16 UTC
|
WARN
|
about 6 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, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding 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 - 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
March 23, 2024 08:16 UTC
|
Type
WARN
|
Affected Components
zscaler.net - Core Cloud Services - Authentication
zscaler.net - Core Cloud Services - Source IP Anchoring (SIPA)
|
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, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding 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 - 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 ..., Core Cloud Services - Traffic Forwarding: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Authentication: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Source IP Anchoring (SIPA): We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., 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 ...
|
|
March 07, 2024 07:56 UTC
|
WARN
|
about 3 hours
|
Core Cloud Services - Zscaler Client connector: Administration UI and User Authentication Issues, Core Cloud Services - Zscaler Cloud Connector Portal: Administration UI and User Authentication Issues, Core Cloud Services - Authentication: Administration UI and User Authentication Issues, Core Cloud Services - Admin UI: Administration UI and User Authentication Issues, Core Cloud Services - Partner Admin UI: Administration UI and User Authentication Issues, and Core Cloud Services - Source IP Anchoring (SIPA): Administration UI and User Authentication Issues
|
See more
Start Time
March 07, 2024 07:56 UTC
|
Type
WARN
|
Affected Components
zscaler.net - Core Cloud Services - Zscaler Client connector
zscaler.net - Core Cloud Services - Zscaler Cloud Connector Portal
zscaler.net - Core Cloud Services - Authentication
zscaler.net - Core Cloud Services - Admin UI
zscaler.net - Core Cloud Services - Partner Admin UI
zscaler.net - Core Cloud Services - Source IP Anchoring (SIPA)
|
Message
Core Cloud Services - Zscaler Client connector: Administration UI and User Authentication Issues, Core Cloud Services - Zscaler Cloud Connector Portal: Administration UI and User Authentication Issues, Core Cloud Services - Authentication: Administration UI and User Authentication Issues, Core Cloud Services - Admin UI: Administration UI and User Authentication Issues, Core Cloud Services - Partner Admin UI: Administration UI and User Authentication Issues, and Core Cloud Services - Source IP Anchoring (SIPA): Administration UI and User Authentication Issues
|
Details
Core Cloud Services - Zscaler Client connector: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., Core Cloud Services - Zscaler Cloud Connector Portal: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., Core Cloud Services - Authentication: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., Core Cloud Services - Admin UI: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., Core Cloud Services - Partner Admin UI: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., and Core Cloud Services - Source IP Anchoring (SIPA): We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ...
|
|
February 11, 2024 11:26 UTC
|
WARN
|
25 days
|
Core Cloud Services - Traffic Forwarding: Issue with SSL Policies with destination IP Groups, APAC - Sydney III: Sydney III Datacenter IPSec Issue, Core Cloud Services - Alerting: Reporting and Logging Issue, and Core Cloud Services - Content Delivery: Reporting and Logging Issue
|
See more
Start Time
February 11, 2024 11:26 UTC
|
Type
WARN
|
Affected Components
zscaler.net - Core Cloud Services - Source IP Anchoring (SIPA)
|
Message
Core Cloud Services - Traffic Forwarding: Issue with SSL Policies with destination IP Groups, APAC - Sydney III: Sydney III Datacenter IPSec Issue, Core Cloud Services - Alerting: Reporting and Logging Issue, and Core Cloud Services - Content Delivery: Reporting and Logging Issue
|
Details
Core Cloud Services - Traffic Forwarding: We are investigating an issue with on our Zscaler.net cloud. SSL policies using destination IP groups may not get work intermittently. Zscaler team has identified the root cause and working ..., APAC - Sydney III: We are investigating intermittent connection timeouts on IPSec tunnels with our Sydney III datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with ..., Core Cloud Services - Alerting: We are investigating an issue with Reporting and Logging on our zdxcloud.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated ..., and Core Cloud Services - Content Delivery: We are investigating an issue with Reporting and Logging on our zdxcloud.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated ...
|
|
February 10, 2024 10:06 UTC
|
WARN
|
1 day
|
Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding using SIPA, APAC - Sydney III: Sydney III Datacenter IPSec Issue, Core Cloud Services - Alerting: Reporting and Logging Issue, and Core Cloud Services - Content Delivery: Reporting and Logging Issue
|
See more
Start Time
February 10, 2024 10:06 UTC
|
Type
WARN
|
Affected Components
zscaler.net - Core Cloud Services - Source IP Anchoring (SIPA)
|
Message
Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding using SIPA, APAC - Sydney III: Sydney III Datacenter IPSec Issue, Core Cloud Services - Alerting: Reporting and Logging Issue, and Core Cloud Services - Content Delivery: Reporting and Logging Issue
|
Details
Core Cloud Services - Source IP Anchoring (SIPA): We are investigating an issue with on our Zscaler.net cloud for SIPA traffic. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated ..., APAC - Sydney III: We are investigating intermittent connection timeouts on IPSec tunnels with our Sydney III datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with ..., Core Cloud Services - Alerting: We are investigating an issue with Reporting and Logging on our zdxcloud.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated ..., and Core Cloud Services - Content Delivery: We are investigating an issue with Reporting and Logging on our zdxcloud.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated ...
|
|
2024-04-29 02:05:31 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-29 02:05:31 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-29 02:05:31 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-29 02:05:31 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|
2024-04-29 02:05:31 UTC UTC
|
STATUS
|
? minutes
|
Sign in to view more status history.
|
See more
|