Cloudflare was down again: Here’s what happened.
Last checked from Zscaler Cloud official status page 2 min. 57 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 zscaler.net - APAC - Beijing III, zscaler.net - APAC - Shanghai II, and zscalertwo.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 Zscaler Cloud 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 Zscaler Cloud status data.
View and upvote the most commonly reported Zscaler Cloud issues to help us better indicate the service status.
Have a different problem with Zscaler Cloud?
Report an outageExplore our interactive Zscaler Cloud 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 Zscaler Cloud in the table below. If you're experiencing a problem now, check the current Zscaler Cloud status or report it.
| Incident Name | Duration | Started | Severity |
|---|---|---|---|
|
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
|
1h 56m |
Warn
|
|
|
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, APAC - Shanghai II: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, and EMEA - Lagos II: Lagos II Datacenter Issue
|
45m |
Warn
|
|
|
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
|
17h 30m |
Warn
|
|
|
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 - Chennai II: Chennai II, Hyderabad I, Mumbai VI Datacenter Issue, APAC - Hyderabad I: Chennai II, Hyderabad I, Mumbai VI Datacenter Issue, APAC - Mumbai VI: Chennai II, Hyderabad I, Mumbai VI 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
|
45m |
Warn
|
|
|
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 - Chennai II: Chennai II, Hyderabad I, Mumbai VI Datacenter Issue, APAC - Hyderabad I: Chennai II, Hyderabad I, Mumbai VI Datacenter Issue, APAC - Mumbai VI: Chennai II, Hyderabad I, Mumbai VI 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, APAC - Shanghai II: Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue, and Core Cloud Services - Authentication: Zidentity Portal Issue
|
50m |
Warn
|
Stay updated with instant alerts for Zscaler Cloud outages by signing up now!
You can also monitor any service or website on your status page
View details of the current Zscaler Cloud status below. If the status shows "Up" but you're still experiencing issues, you can report a problem such as connectivity issues, outages, or slow performance. These issues are commonly reported when Zscaler Cloud is down or facing partial disruptions.
Stay updated with instant alerts for Zscaler Cloud 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 Zscaler Cloud 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.
Zscaler Cloud (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 Zscaler Cloud users. When Zscaler Cloud 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 Zscaler Cloud 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 Zscaler Cloud is experiencing a problem now or has recently resolved one, our detailed history keeps you updated.
More than 300 StatusGator users monitor Zscaler Cloud 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 Zscaler Cloud incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If we detect a potential Zscaler Cloud 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 Zscaler Cloud 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 Zscaler Cloud 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.
Zscaler Cloud posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Zscaler Cloud enters a pre-planned maintenance window, keeping you up to date.
When Zscaler Cloud 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 Zscaler Cloud 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 Zscaler Cloud 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 Zscaler Cloud outages by signing up now!
Can't find your question? Email us to arrange a time to discuss. We'd love to chat!
