Last checked from Zscaler Cloud EMEA - Munich I official status page 4 min. 5 sec. ago
Zscaler Cloud EMEA - Munich I not working for you?
Report an issueThis chart represents Zscaler Cloud EMEA - Munich I 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 EMEA - Munich I status data.
View and upvote the most commonly reported issues to help us better indicate the service status.
Have a different problem with Zscaler Cloud EMEA - Munich I?
Report an issue
We've been monitoring Zscaler Cloud EMEA - Munich I outages since October 7, 2019. Here's the history of service outages we've observed from the Zscaler Cloud EMEA - Munich I Status Page
Follow the recent outages and downtime for Zscaler Cloud EMEA - Munich I in the table below.
| Incident Name | Duration | Started | Severity |
|---|---|---|---|
|
EMEA - Brussels II: Traffic slowness from Brussels DC towards us-west regions
|
100d 9h 51m |
Warn
|
|
|
EMEA - Amsterdam II: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Brussels II: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Capetown IV: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Frankfurt IV: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Frankfurt V: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Frankfurt VI: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Cape Town III: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Dusseldorf I: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Johannesburg III: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Oslo III: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Dublin II: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Ireland: Traffic slowness from EMEA DCs towards us-west regions, EMEA - London III: Traffic slowness from EMEA DCs towards us-west regions, EMEA - London IV: Traffic slowness from EMEA DCs towards us-west regions, EMEA - London V: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Madrid III: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Manchester I: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Marseille I: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Milan III: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Moscow III: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Munich I: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Paris II: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Paris III: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Paris IV: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Stockholm III: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Stockholm IV: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Tel Aviv: Traffic slowness from EMEA DCs towards us-west regions, EMEA - Warsaw II: Traffic slowness from EMEA DCs towards us-west regions, and EMEA - Zurich I: Traffic slowness from EMEA DCs towards us-west regions
|
1h 10m |
Warn
|
|
|
APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Capetown: Capetown Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Capetown: Capetown Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, and EMEA - Moscow III: Moscow III Datacenter Issue
|
519d 6h 5m |
Warn
|
|
|
APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Capetown: Capetown Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Capetown: Capetown Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Munich I: Munich I Datacenter Issue, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, and EMEA - Moscow III: Moscow III Datacenter Issue
|
25m |
Warn
|
|
|
APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Amsterdam: Google Meet Captcha Issue, EMEA - Capetown: Capetown Datacenter Issue, EMEA - Johannesburg II: Google Meet Captcha Issue, EMEA - Johannesburg III: Google Meet Captcha Issue, EMEA - Frankfurt IV: Google Meet Captcha Issue, EMEA - London III: Google Meet Captcha Issue, EMEA - Milan III: Google Meet Captcha Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Oslo II: Google Meet Captcha Issue, EMEA - Paris II: Google Meet Captcha Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Amsterdam: Google Meet Captcha Issue, EMEA - Johannesburg II: Google Meet Captcha Issue, EMEA - Johannesburg III: Google Meet Captcha Issue, EMEA - Frankfurt IV: Google Meet Captcha Issue, EMEA - London III: Google Meet Captcha Issue, EMEA - Milan III: Google Meet Captcha Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Oslo II: Google Meet Captcha Issue, EMEA - Paris II: Google Meet Captcha Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Amsterdam: Google Meet Captcha Issue, EMEA - Capetown: Capetown Datacenter Issue, EMEA - Johannesburg II: Google Meet Captcha Issue, EMEA - Johannesburg III: Google Meet Captcha Issue, EMEA - Frankfurt IV: Google Meet Captcha Issue, EMEA - London III: Google Meet Captcha Issue, EMEA - Milan III: Google Meet Captcha Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Oslo II: Google Meet Captcha Issue, EMEA - Paris II: Google Meet Captcha Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Shanghai: Shanghai Datacenter Issue, APAC - Shanghai II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, Core Cloud Services - Traffic Forwarding: Singtel impacted by submarine cable fault, and EMEA - Moscow III: Moscow III Datacenter Issue
|
1m |
Warn
|
Stay updated with instant alerts for Zscaler Cloud EMEA - Munich I outages by signing up now!
You can also monitor any service or website on your status page
Stay updated with instant alerts for Zscaler Cloud EMEA - Munich I 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 freeZscaler Cloud EMEA - Munich I 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,171 outages that affected Zscaler Cloud EMEA - Munich I users. When Zscaler Cloud EMEA - Munich I publishes downtime on their status page, they do so across 630 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 Zscaler Cloud EMEA - Munich I 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,700 notifications to our users about Zscaler Cloud EMEA - Munich I incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If Zscaler Cloud EMEA - Munich I 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 EMEA - Munich I 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 EMEA - Munich I posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Zscaler Cloud EMEA - Munich I enters a pre-planned maintenance window, keeping you up to date.
When Zscaler Cloud EMEA - Munich I 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 EMEA - Munich I 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 EMEA - Munich I 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 Zscaler Cloud EMEA - Munich I outages by signing up now!
Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!
