Last checked from Core Cloud Services - Control official status page 2 min. 48 sec. ago
Core Cloud Services - Control Status
Is Core Cloud Services - Control down?
Core Cloud Services - Control is up
Zero trust cybersecurity for fast, secure digital transformation.
Not working for you?
StatusGator reports that Zscaler Cloud is currently experiencing a partial outage. There are confirmed issues with zdxcloud.net - Core Cloud Services - Content Delivery, but all other components are operational. Core Cloud Services - Content Delivery: ZDX Admin Portal – Reporting and Logging Delay
Core Cloud Services - Control service health
This 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.
24 hrs ending
Top reported issues
View and upvote the most commonly reported Core Cloud Services - Control issues to help us better indicate the service status.
- Connectivity issue
- Error message
- Server not responding
- Sign in problem
- Service down
- Slow performance
- Unable to download
- App not loading
- Other
Have a different problem with Core Cloud Services - Control?
Recent outage reports
See recent outage reports from real Core Cloud Services - Control users
133 outage reports in the last 24 hours
Missouri, United States
Connectivity issue
6 days ago
6 days ago
Maharashtra, India
Service down
8 days ago
8 days ago
Pennsylvania, United States
Connectivity issue
10 days ago
10 days ago
Georgia, United States
Connectivity issue
10 days ago
10 days ago
Colorado, United States
"ZPA intermittent issues "
10 days ago
10 days ago
Maharashtra, India
"APAC region facing issues to connect Zscaler Client Connector. Incident started from 15:52 PM IST and not yet resolved"
about 1 month ago
about 1 month ago
Texas, United States
"It isn't connecting. Stating a tunneling issue or an issue with antivirus programming."
about 1 month ago
about 1 month ago
Texas, United States
Connectivity issue
about 2 months ago
about 2 months ago
North Carolina, United States
"App not loading, outage for Charlotte mecklenberg schools"
2 months ago
2 months ago
Illinois, United States
"latency with O365"
2 months ago
2 months ago
Core Cloud Services - Control outage map
Explore our interactive Core Cloud Services - Control outage map to monitor real-time incidents and service issues across the globe. This dynamic map highlights regions around the world affected by recent Zscaler Cloud outages, giving you a clear view of performance and downtime trends.
Recently detected Zscaler Cloud outages
| Incident description | Duration | StatusGator detected | Officially acknowledged |
|---|---|---|---|
| Intermittent internet access issues with ZScaler. | 1h 20m |
Never acknowledged
|
Looking to track Core Cloud Services - Control downtime and outages?
- Receive real-time status updates
- Show current status on private or public status page
- Be the first to know if service is down
- Keep your team informed
- Monitor alongside other services and websites
Recent Core Cloud Services - Control outages and issues
| 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
|
1380d 10h 54m |
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
|
88d 4h 6m |
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
|
Get notified about Core Cloud Services - Control outages
Stay updated with instant alerts for Core Cloud Services - Control outages by signing up now!
See Core Cloud Services - Control status on your status page
You can also monitor any service or website on your status page
Get notified about Core Cloud Services - Control outages
Stay updated with instant alerts for Core Cloud Services - Control outages by signing up now!
One App that has it all
With features designed to cover all your needs for monitoring and communicating outages or downtime, StatusGator keeps your team connected and informed. Stay updated on Core Cloud Services - Control outages, potential problems, and its current status in real-time, ensuring you're always prepared to act.
Monitor Core Cloud Services - Control along with other services and websites
StatusGator monitors over 8,850 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.
Get notified on Core Cloud Services - Control status change
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.
Show Core Cloud Services - Control on your status page
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.
Users who monitor Core Cloud Services - Control status also follow these services
About our Core Cloud Services - Control status page integration
Core Cloud Services - Control (Zero trust cybersecurity for fast, secure digital transformation) is a a Cloud Infrastructure and Security solution that StatusGator has been monitoring since October 2019. Over the past over 6 years, we have collected data on on more than 3,063 outages that affected Core Cloud Services - Control users. When Core Cloud Services - Control publishes downtime on their status page, they do so across 876 components and 20 groups using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.
If you're wondering, "Is Core Cloud Services - Control down?", or need to know its current status, we've got you covered. Our platform tracks every reported outage, performance issue, and maintenance window to ensure you're informed. Whether Core Cloud Services - Control is experiencing a problem now or has recently resolved one, our detailed history keeps you updated.
More than 300 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 30,400 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.
-
Early Warning Signals
If we detect a potential Core Cloud Services - Control outage or other issue before it was reported on the official status page we will send an Early Warning Signal notification to StatusGator subscribers. We can often detect issues before they are officially acknowledged by the provider, giving you a head start on resolving any potential problems.
-
Down Notifications
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.
-
Warning Notifications
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.
-
Maintenance Notifications
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.
-
Status Messages
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.
-
Status Details
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.
-
Component Status Filtering
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 whenever a particular component is down. 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.
Get notified about Core Cloud Services - Control outages
Stay updated with instant alerts for Core Cloud Services - Control outages by signing up now!
Looking for Downdetector Core Cloud Services - Control alerts?
Frequently asked questions
Can't find your question? Email us to arrange a time to discuss. We'd love to chat!