Is Core Cloud Services - Control down?
Current Core Cloud Services - Control status is UP

We checked the official Core Cloud Services - Control Status Page 52 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Core Cloud Services - Control Outages and Issues

Follow the recent outages and downtime for Core Cloud Services - Control in the table below.

Start Time

Type

Length

Message

Details

September 02, 2022 06:16 UTC

WARN

ongoing

Africa - Capetown: Capetown Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Asia - Taipei: Taipei Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Africa - Capetown: Capetown Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, and Europe - Moscow III: Moscow III Datacenter Issue

See more
Start Time

September 02, 2022 06:16 UTC

Type WARN
Affected Components

zdxcloud.net - Core Cloud Services - Control

Message

Africa - Capetown: Capetown Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Asia - Taipei: Taipei Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Africa - Capetown: Capetown Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, and Europe - Moscow III: Moscow III Datacenter Issue

Details

Africa - Capetown: We are investigating an issue with our Capetown datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ..., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available. Update - Fri, 08 Jul 2022 ..., Asia - Kuala Lumpur I: We are investigating an issue with our Kuala Lumpur I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out to ..., Asia - Taipei: We are investigating an issue with our Taipei datacenter. We are investigating periods of slowness and/or increased latency. For additional information please reach out to Zscaler Support referencing this incident, ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available. Update - Fri, 08 Jul 2022 ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Africa - Capetown: We are investigating an issue with our Capetown datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available. Update - Fri, 08 Jul 2022 ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out to ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available. Update - Fri, 08 Jul 2022 ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., and Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory.

August 30, 2022 19:01 UTC

WARN

2 days

Africa - Capetown: Capetown Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Asia - Taipei: Taipei Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Africa - Capetown: Capetown Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, and Core Cloud Services - Control: Administration UI Issue

See more
Start Time

August 30, 2022 19:01 UTC

Type WARN
Affected Components

zdxcloud.net - Core Cloud Services - Control

Message

Africa - Capetown: Capetown Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Asia - Taipei: Taipei Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Africa - Capetown: Capetown Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, and Core Cloud Services - Control: Administration UI Issue

Details

Africa - Capetown: We are investigating an issue with our Capetown datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ..., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available. Update - Fri, 08 Jul 2022 ..., Asia - Kuala Lumpur I: We are investigating an issue with our Kuala Lumpur I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out to ..., Asia - Taipei: We are investigating an issue with our Taipei datacenter. We are investigating periods of slowness and/or increased latency. For additional information please reach out to Zscaler Support referencing this incident, ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available. Update - Fri, 08 Jul 2022 ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Africa - Capetown: We are investigating an issue with our Capetown datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available. Update - Fri, 08 Jul 2022 ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For additional information please reach out to ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available. Update - Fri, 08 Jul 2022 ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., and Core Cloud Services - Control: We are investigating an issue with the new probe configurations on our zdxcloud.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be ...

June 02, 2022 17:56 UTC

WARN

3 months

Asia - Beijing: Issue accessing Microsoft Teams, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Core Cloud Services - Admin UI: Administration UI Issue, Core Cloud Services - Admin UI: Reporting Issue in Admin UI, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Chennai II: Chennai II Traffic Rerouted, Asia - Mumbai VI: Mumbai VI Traffic Rerouted, and Europe - Moscow III: Moscow III Datacenter Issue

See more
Start Time

June 02, 2022 17:56 UTC

Type WARN
Affected Components

zdxcloud.net - Core Cloud Services - Content Delivery

zdxcloud.net - Core Cloud Services - Control

zdxcloud.net - Core Cloud Services - Zscaler Client connector

zdxcloud.net - Core Cloud Services - Authentication

zdxcloud.net - Core Cloud Services - Alerting

zdxcloud.net - Core Cloud Services - DNS

Message

Asia - Beijing: Issue accessing Microsoft Teams, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Core Cloud Services - Admin UI: Administration UI Issue, Core Cloud Services - Admin UI: Reporting Issue in Admin UI, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Chennai II: Chennai II Traffic Rerouted, Asia - Mumbai VI: Mumbai VI Traffic Rerouted, and Europe - Moscow III: Moscow III Datacenter Issue

Details

Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available., Asia - Kuala Lumpur I: We are investigating an issue with our Kuala Lumpur I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Core Cloud Services - Admin UI: We are investigating an issue with the administration UI on our zscaler.net Cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated ..., Core Cloud Services - Admin UI: We are investigating an issue with reporting for Executive Insights Email Report in the Administration UI of our Zscalerone.Net cloud. For additional information please reach out to Zscaler Support referencing ..., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Asia - Chennai II: We are investigating an issue with our Chennai II datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For additional information please reach out to Zscaler ..., Asia - Mumbai VI: We are investigating an issue with our Mumbai VI datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. We will post additional information on this incident ..., and Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory.

June 01, 2022 09:26 UTC

DOWN

1 day

Asia - Beijing: Issue accessing Microsoft Teams, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Core Cloud Services - Admin UI: Reporting Issue in Admin UI, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, US & Canada - Atlanta II: Device registration and portal failure for Zscaler Client Connector, US & Canada - Boston I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Chicago I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Cleveland II: Device registration and portal failure for Zscaler Client Connector, US & Canada - Dallas I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Denver III: Device registration and portal failure for Zscaler Client Connector, US & Canada - Los Angeles I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Mexico I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Miami III: Device registration and portal failure for Zscaler Client Connector, US & Canada - Montreal I: Device registration and portal failure for Zscaler Client Connector, US & Canada - New York III: Device registration and portal failure for Zscaler Client Connector, US & Canada - Portland II: Device registration and portal failure for Zscaler Client Connector, US & Canada - San Francisco IV: Device registration and portal failure for Zscaler Client Connector, US & Canada - Seattle: Device registration and portal failure for Zscaler Client Connector, US & Canada - Toronto III: Device registration and portal failure for Zscaler Client Connector, US & Canada - Vancouver I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Washington DC: Device registration and portal failure for Zscaler Client Connector, Latin America - Sao Paulo IV: Device registration and portal failure for Zscaler Client Connector, Latin America - Sao Paulo II: Device registration and portal failure for Zscaler Client Connector, Middle East - Dubai I: Device registration and portal failure for Zscaler Client Connector, Africa - Cape Town III: Device registration and portal failure for Zscaler Client Connector, Africa - Johannesburg III: Device registration and portal failure for Zscaler Client Connector, Asia - Seoul I: Device registration and portal failure for Zscaler Client Connector, Asia - Auckland: Device registration and portal failure for Zscaler Client Connector, Asia - Osaka I: Device registration and portal failure for Zscaler Client Connector, Asia - Beijing: Device registration and portal failure for Zscaler Client Connector, Asia - Beijing II: Device registration and portal failure for Zscaler Client Connector, Asia - Chennai II: Device registration and portal failure for Zscaler Client Connector, Asia - Hong Kong III: Device registration and portal failure for Zscaler Client Connector, Asia - Melbourne II: Device registration and portal failure for Zscaler Client Connector, Asia - Mumbai V: Device registration and portal failure for Zscaler Client Connector, Asia - Mumbai VI: Device registration and portal failure for Zscaler Client Connector, Asia - New Delhi I: Device registration and portal failure for Zscaler Client Connector, Asia - Seoul: Device registration and portal failure for Zscaler Client Connector, Asia - Seoul II: Device registration and portal failure for Zscaler Client Connector, Asia - Shanghai I: Device registration and portal failure for Zscaler Client Connector, Asia - Shanghai II: Device registration and portal failure for Zscaler Client Connector, Asia - Singapore III: Device registration and portal failure for Zscaler Client Connector, Asia - Singapore IV: Device registration and portal failure for Zscaler Client Connector, Asia - Sydney III: Device registration and portal failure for Zscaler Client Connector, Asia - Sydney IV: Device registration and portal failure for Zscaler Client Connector, Asia - Tokyo IV: Device registration and portal failure for Zscaler Client Connector, Europe - Marseille I: Device registration and portal failure for Zscaler Client Connector, Europe - Amsterdam II: Device registration and portal failure for Zscaler Client Connector, Europe - Brussels II: Device registration and portal failure for Zscaler Client Connector, Europe - Dublin II: Device registration and portal failure for Zscaler Client Connector, Europe - Frankfurt IV: Device registration and portal failure for Zscaler Client Connector, Europe - Frankfurt V: Device registration and portal failure for Zscaler Client Connector, Europe - Ireland: Device registration and portal failure for Zscaler Client Connector, Europe - London III: Device registration and portal failure for Zscaler Client Connector, Europe - Madrid III: Device registration and portal failure for Zscaler Client Connector, Europe - Manchester I: Device registration and portal failure for Zscaler Client Connector, Europe - Milan III: Device registration and portal failure for Zscaler Client Connector, Europe - Moscow III: Device registration and portal failure for Zscaler Client Connector, Europe - Munich I: Device registration and portal failure for Zscaler Client Connector, Europe - Paris II: Device registration and portal failure for Zscaler Client Connector, Europe - Stockholm III: Device registration and portal failure for Zscaler Client Connector, Europe - Stockholm IV: Device registration and portal failure for Zscaler Client Connector, Europe - Tel Aviv I: Device registration and portal failure for Zscaler Client Connector, Europe - Warsaw II: Device registration and portal failure for Zscaler Client Connector, Europe - Zurich I: Device registration and portal failure for Zscaler Client Connector, Core Cloud Services - Alerting: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, Core Cloud Services - Content Delivery: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, Core Cloud Services - Control: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, Core Cloud Services - Zscaler Client connector: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, Core Cloud Services - Authentication: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, and Core Cloud Services - DNS: Zscaler Digital Experience Monitoring issue - ZDX for ZPA

See more
Start Time

June 01, 2022 09:26 UTC

Type DOWN
Affected Components

zdxcloud.net - Core Cloud Services - Zscaler Client connector

zdxcloud.net - Core Cloud Services - Authentication

zdxcloud.net - Core Cloud Services - Control

zdxcloud.net - Core Cloud Services - Content Delivery

zdxcloud.net - Core Cloud Services - Alerting

zdxcloud.net - Core Cloud Services - DNS

Message

Asia - Beijing: Issue accessing Microsoft Teams, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Core Cloud Services - Admin UI: Reporting Issue in Admin UI, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Asia - Beijing: Issue accessing Microsoft Teams, Europe - Moscow III: Moscow III Datacenter Issue, US & Canada - Atlanta II: Device registration and portal failure for Zscaler Client Connector, US & Canada - Boston I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Chicago I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Cleveland II: Device registration and portal failure for Zscaler Client Connector, US & Canada - Dallas I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Denver III: Device registration and portal failure for Zscaler Client Connector, US & Canada - Los Angeles I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Mexico I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Miami III: Device registration and portal failure for Zscaler Client Connector, US & Canada - Montreal I: Device registration and portal failure for Zscaler Client Connector, US & Canada - New York III: Device registration and portal failure for Zscaler Client Connector, US & Canada - Portland II: Device registration and portal failure for Zscaler Client Connector, US & Canada - San Francisco IV: Device registration and portal failure for Zscaler Client Connector, US & Canada - Seattle: Device registration and portal failure for Zscaler Client Connector, US & Canada - Toronto III: Device registration and portal failure for Zscaler Client Connector, US & Canada - Vancouver I: Device registration and portal failure for Zscaler Client Connector, US & Canada - Washington DC: Device registration and portal failure for Zscaler Client Connector, Latin America - Sao Paulo IV: Device registration and portal failure for Zscaler Client Connector, Latin America - Sao Paulo II: Device registration and portal failure for Zscaler Client Connector, Middle East - Dubai I: Device registration and portal failure for Zscaler Client Connector, Africa - Cape Town III: Device registration and portal failure for Zscaler Client Connector, Africa - Johannesburg III: Device registration and portal failure for Zscaler Client Connector, Asia - Seoul I: Device registration and portal failure for Zscaler Client Connector, Asia - Auckland: Device registration and portal failure for Zscaler Client Connector, Asia - Osaka I: Device registration and portal failure for Zscaler Client Connector, Asia - Beijing: Device registration and portal failure for Zscaler Client Connector, Asia - Beijing II: Device registration and portal failure for Zscaler Client Connector, Asia - Chennai II: Device registration and portal failure for Zscaler Client Connector, Asia - Hong Kong III: Device registration and portal failure for Zscaler Client Connector, Asia - Melbourne II: Device registration and portal failure for Zscaler Client Connector, Asia - Mumbai V: Device registration and portal failure for Zscaler Client Connector, Asia - Mumbai VI: Device registration and portal failure for Zscaler Client Connector, Asia - New Delhi I: Device registration and portal failure for Zscaler Client Connector, Asia - Seoul: Device registration and portal failure for Zscaler Client Connector, Asia - Seoul II: Device registration and portal failure for Zscaler Client Connector, Asia - Shanghai I: Device registration and portal failure for Zscaler Client Connector, Asia - Shanghai II: Device registration and portal failure for Zscaler Client Connector, Asia - Singapore III: Device registration and portal failure for Zscaler Client Connector, Asia - Singapore IV: Device registration and portal failure for Zscaler Client Connector, Asia - Sydney III: Device registration and portal failure for Zscaler Client Connector, Asia - Sydney IV: Device registration and portal failure for Zscaler Client Connector, Asia - Tokyo IV: Device registration and portal failure for Zscaler Client Connector, Europe - Marseille I: Device registration and portal failure for Zscaler Client Connector, Europe - Amsterdam II: Device registration and portal failure for Zscaler Client Connector, Europe - Brussels II: Device registration and portal failure for Zscaler Client Connector, Europe - Dublin II: Device registration and portal failure for Zscaler Client Connector, Europe - Frankfurt IV: Device registration and portal failure for Zscaler Client Connector, Europe - Frankfurt V: Device registration and portal failure for Zscaler Client Connector, Europe - Ireland: Device registration and portal failure for Zscaler Client Connector, Europe - London III: Device registration and portal failure for Zscaler Client Connector, Europe - Madrid III: Device registration and portal failure for Zscaler Client Connector, Europe - Manchester I: Device registration and portal failure for Zscaler Client Connector, Europe - Milan III: Device registration and portal failure for Zscaler Client Connector, Europe - Moscow III: Device registration and portal failure for Zscaler Client Connector, Europe - Munich I: Device registration and portal failure for Zscaler Client Connector, Europe - Paris II: Device registration and portal failure for Zscaler Client Connector, Europe - Stockholm III: Device registration and portal failure for Zscaler Client Connector, Europe - Stockholm IV: Device registration and portal failure for Zscaler Client Connector, Europe - Tel Aviv I: Device registration and portal failure for Zscaler Client Connector, Europe - Warsaw II: Device registration and portal failure for Zscaler Client Connector, Europe - Zurich I: Device registration and portal failure for Zscaler Client Connector, Core Cloud Services - Alerting: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, Core Cloud Services - Content Delivery: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, Core Cloud Services - Control: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, Core Cloud Services - Zscaler Client connector: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, Core Cloud Services - Authentication: Zscaler Digital Experience Monitoring issue - ZDX for ZPA, and Core Cloud Services - DNS: Zscaler Digital Experience Monitoring issue - ZDX for ZPA

Details

Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available., Asia - Kuala Lumpur I: We are investigating an issue with our Kuala Lumpur I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Core Cloud Services - Admin UI: We are investigating an issue with reporting for Executive Insights Email Report in the Administration UI of our Zscalerone.Net cloud. For additional information please reach out to Zscaler Support referencing ..., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available., Asia - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., Asia - Beijing: We are investigating an issue with Microsoft team on our Beijing datacenter. We will post additional information on this incident as it is available., Europe - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., US & Canada - Atlanta II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Boston I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Chicago I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Cleveland II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Dallas I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Denver III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Los Angeles I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Mexico I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Miami III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Montreal I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - New York III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Portland II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - San Francisco IV: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Seattle: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Toronto III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Vancouver I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., US & Canada - Washington DC: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Latin America - Sao Paulo IV: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Latin America - Sao Paulo II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Middle East - Dubai I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Africa - Cape Town III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Africa - Johannesburg III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Seoul I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Auckland: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Osaka I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Beijing: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Beijing II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Chennai II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Hong Kong III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Melbourne II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Mumbai V: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Mumbai VI: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - New Delhi I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Seoul: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Seoul II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Shanghai I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Shanghai II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Singapore III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Singapore IV: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Sydney III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Sydney IV: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Asia - Tokyo IV: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Marseille I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Amsterdam II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Brussels II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Dublin II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Frankfurt IV: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Frankfurt V: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Ireland: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - London III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Madrid III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Manchester I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Milan III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Moscow III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Munich I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Paris II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Stockholm III: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Stockholm IV: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Tel Aviv I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Warsaw II: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ..., Europe - Zurich I: We are investigating a global issue affecting the ability to register ZCC to the ZPA cloud. 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 Zscaler Digital Experience Monitoring (ZDX) for Zscaler Private Access (ZPA). At the moment the ZDX probes for ZPA are unavailable. For additional information please ..., Core Cloud Services - Content Delivery: We are investigating an issue with our Zscaler Digital Experience Monitoring (ZDX) for Zscaler Private Access (ZPA). At the moment the ZDX probes for ZPA are unavailable. For additional information please ..., Core Cloud Services - Control: We are investigating an issue with our Zscaler Digital Experience Monitoring (ZDX) for Zscaler Private Access (ZPA). At the moment the ZDX probes for ZPA are unavailable. For additional information please ..., Core Cloud Services - Zscaler Client connector: We are investigating an issue with our Zscaler Digital Experience Monitoring (ZDX) for Zscaler Private Access (ZPA). At the moment the ZDX probes for ZPA are unavailable. For additional information please ..., Core Cloud Services - Authentication: We are investigating an issue with our Zscaler Digital Experience Monitoring (ZDX) for Zscaler Private Access (ZPA). At the moment the ZDX probes for ZPA are unavailable. For additional information please ..., and Core Cloud Services - DNS: We are investigating an issue with our Zscaler Digital Experience Monitoring (ZDX) for Zscaler Private Access (ZPA). At the moment the ZDX probes for ZPA are unavailable. For additional information please ...

No outages or status changes in the last 24 hours

Core Cloud Services - Control status, last 24 hours:

10:00 AM
4:00 PM
10:00 PM
4:00 AM
10:00 AM
10:00 AM
10:00 PM
10:00 AM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

  • Maintenance: 0 minutes

Core Cloud Services - Control Outage and Status History

We've been monitoring Core Cloud Services - Control outages since October 7, 2019.
Here's the history of service outages we've observed from the Core Cloud Services - Control Status Page:

April 2024

March 2024

February 2024

  • Up

  • Warn

  • Down

  • Maintenance

Instant enriched data from
3,580 status pages

About Our Core Cloud Services - Control Status Page Integration

Core Cloud Services - Control is a Cloud Infrastructure and Security solution that StatusGator has been monitoring since October 2019. Over the past over 4 years, we have collected data on on more than 1,805 outages that affected Core Cloud Services - Control users. When Core Cloud Services - Control publishes downtime on their status page, they do so across 518 components and 11 groups using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.

More than 200 StatusGator users monitor Core Cloud Services - Control to get notified when it's down, is under maintenance, or has an outage. This makes it one of the most popular cloud infrastructure services monitored on our platform. We've sent more than 6,800 notifications to our users about Core Cloud Services - Control incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Core Cloud Services - Control is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Core Cloud Services - Control is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Core Cloud Services - Control posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Core Cloud Services - Control enters a pre-planned maintenance window, keeping you up to date.

Core Cloud Services - Control does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate Core Cloud Services - Control maintenance events into your unified calendar.

When Core Cloud Services - Control posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Core Cloud Services - Control has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Core Cloud Services - Control has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Core Cloud Services - Control Down?

Are you experiencing issues with Core Cloud Services - Control? Sign up to receive notifications when Core Cloud Services - Control publishes outages.

Core Cloud Services - Control Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,580 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Core Cloud Services - Control?

Sign up for StatusGator and see all historical information about Core Cloud Services - Control outages and performance issues. Get free, instant notifications when Core Cloud Services - Control goes down.