Last checked from Core Cloud Services - Control official status page 4 min. 30 sec. ago
Core Cloud Services - Control not working for you?
Report an issueThis chart represents Core Cloud Services - Control service health over the last 24 hours, with data points collected every 15 minutes based on issue reports, page visits, and signal strength. Sign up for free to see more Core Cloud Services - Control status data.
View and upvote the most commonly reported issues to help us better indicate the service status.
Have a different problem with Core Cloud Services - Control?
Report an issue
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
Follow the recent outages and downtime for Core Cloud Services - Control in the table below.
| Incident Name | Duration | Started | Severity |
|---|---|---|---|
|
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
|
810d 14h 37m |
Warn
|
|
|
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
|
2d 11h 15m |
Warn
|
|
|
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
|
4h 6m 88d |
Warn
|
|
|
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
|
1d 8h 30m |
Down
|
Stay updated with instant alerts for Core Cloud Services - Control outages by signing up now!
You can also monitor any service or website on your status page
Stay updated with instant alerts for Core Cloud Services - Control outages by signing up now!
Features covering most of your needs in monitoring and communicating outages or downtime.
StatusGator monitors over 4,000 cloud services, hosted applications, and websites. Just add what you need to the list, and we'll automatically aggregate their statuses into a single page. You'll receive notifications for any issues affecting you and your page subscribers.
Start monitoring for free
StatusGator monitors all of your services and websites and sends your team instant notifications when they go down. Stay abreast of issues that affect your team with notifications: in email, Slack, Teams, or wherever your team communicates.
Start monitoring for free
Easily notify your end-users of outages using a customizable status page. Display cloud services or websites, as well as any custom monitors you add manually. Create multiple status pages tailored to different needs, customize them, and embed them for maximum effectiveness.
Start monitoring for freeCore Cloud Services - Control is a Cloud Infrastructure and Security solution that StatusGator has been monitoring since October 2019. Over the past about 5 years, we have collected data on on more than 2,169 outages that affected Core Cloud Services - Control users. When Core Cloud Services - Control publishes downtime on their status page, they do so across 626 components and 14 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 11,600 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.
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.
Stay updated with instant alerts for Core Cloud Services - Control outages by signing up now!
Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!
