Cloudflare was down again: Here’s what happened.
Last checked from Core Cloud Services - IaC Scanning official status page 8 sec. ago
Zero trust cybersecurity for fast, secure digital transformation.
Not working for you?
Report an outageStatusGator reports that Zscaler Cloud is currently experiencing a partial outage. There are confirmed issues with zscloud.net - APAC - Beijing, zscaler.net - APAC - Shanghai II, and zscaler.net - APAC - Beijing III and 9 other components, but all other components are operational. APAC - Beijing: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Beijing III: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Shanghai II: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Beijing: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Beijing III: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Shanghai II: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Beijing: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Beijing III: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Shanghai II: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Beijing: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, APAC - Beijing III: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, and APAC - Shanghai II: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue
This chart represents Core Cloud Services - IaC Scanning 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 - IaC Scanning status data.
View and upvote the most commonly reported Core Cloud Services - IaC Scanning issues to help us better indicate the service status.
Have a different problem with Core Cloud Services - IaC Scanning?
Report an outageExplore our interactive Core Cloud Services - IaC Scanning 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.
| Incident description | Duration | StatusGator detected | Officially acknowledged |
|---|---|---|---|
| Intermittent internet access issues with ZScaler. | 1h 20m |
Never acknowledged
|
Follow the recent outages and downtime for Core Cloud Services - IaC Scanning in the table below. If you're experiencing a problem now, check the current Core Cloud Services - IaC Scanning status or report it.
| Incident Name | Duration | Started | Severity |
|---|---|---|---|
|
EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, and EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue
|
836d 13h 45m |
Warn
|
|
|
EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, and Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue
|
1h 25m |
Warn
|
|
|
EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue, and Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue
|
1m |
Warn
|
|
|
EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Capetown IV: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg II: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, EMEA - Johannesburg III: Johannesburg III ,Johannesburg II, Capetown IV, Capetown Datacenter Issue, Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue, and Core Cloud Services - IaC Scanning: Zscaler Posture Control Issue
|
17h 19m |
Warn
|
|
|
Africa - Capetown: Capetown Datacenter Issue, Asia - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, Africa - Capetown: Capetown Datacenter Issue, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, Asia - Shanghai: Shanghai Datacenter Issue, Europe - Frankfurt VI: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Dusseldorf I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Vienna I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, US & Canada - Seattle: Seattle Datacenter Issue, Europe - Frankfurt IV: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, Europe - Moscow III: Moscow III Datacenter Issue, Europe - Munich I: Dusseldorf I, Frankfurt IV, Munich I,Vienna I, Frankfurt VI Datacenter Issue, and Core Cloud Services - Workload Segmentation Cloud: Zscaler Workload Segmentation Issue
|
167d 8h 4m |
Warn
|
Stay updated with instant alerts for Core Cloud Services - IaC Scanning 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 - IaC Scanning outages by signing up now!
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 - IaC Scanning outages, potential problems, and its current status in real-time, ensuring you're always prepared to act.
StatusGator monitors over 7,030 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.
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.
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.
Core Cloud Services - IaC Scanning (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 about 6 years, we have collected data on on more than 2,750 outages that affected Core Cloud Services - IaC Scanning users. When Core Cloud Services - IaC Scanning publishes downtime on their status page, they do so across 788 components and 17 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 - IaC Scanning 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 - IaC Scanning 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 - IaC Scanning 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 25,600 notifications to our users about Core Cloud Services - IaC Scanning incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If we detect a potential Core Cloud Services - IaC Scanning 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.
If Core Cloud Services - IaC Scanning 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 - IaC Scanning 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 - IaC Scanning posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Core Cloud Services - IaC Scanning enters a pre-planned maintenance window, keeping you up to date.
When Core Cloud Services - IaC Scanning 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 - IaC Scanning 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 - IaC Scanning 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.
Stay updated with instant alerts for Core Cloud Services - IaC Scanning outages by signing up now!
Can't find your question? Email us to arrange a time to discuss. We'd love to chat!
