Is Zscaler Cloud EMEA - Johannesburg III down?
Current Zscaler Cloud EMEA - Johannesburg III status is UP

We checked the official Zscaler Cloud EMEA - Johannesburg III Status Page 4 min. 4 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Zscaler Cloud EMEA - Johannesburg III Outages and Issues

Follow the recent outages and downtime for Zscaler Cloud EMEA - Johannesburg III in the table below.

Start Time

Type

Length

Message

Details

April 15, 2024 00:11 UTC

WARN

less than a minute

EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs

See more
Start Time

April 15, 2024 00:11 UTC

Type WARN
Affected Components

zscalerone.net - EMEA - Capetown

zscalerone.net - EMEA - Johannesburg II

zscalertwo.net - EMEA - Capetown

zscalertwo.net - EMEA - Johannesburg II

zscalertwo.net - EMEA - Johannesburg III

zscloud.net - EMEA - Capetown

zscloud.net - EMEA - Johannesburg II

zscalerthree.net - EMEA - Johannesburg II

zscalerthree.net - EMEA - Johannesburg III

zscaler.net - EMEA - Capetown

zscaler.net - EMEA - Johannesburg II

zscaler.net - EMEA - Johannesburg III

zscloud.net - EMEA - Johannesburg III

Message

EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs

Details

EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., and EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ...

April 15, 2024 00:11 UTC

WARN

ongoing

EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs

See more
Start Time

April 15, 2024 00:11 UTC

Type WARN
Affected Components

zscalerone.net - EMEA - Capetown

zscalerone.net - EMEA - Johannesburg II

zscalertwo.net - EMEA - Capetown

zscalertwo.net - EMEA - Johannesburg II

zscalertwo.net - EMEA - Johannesburg III

zscloud.net - EMEA - Capetown

zscloud.net - EMEA - Johannesburg II

zscalerthree.net - EMEA - Johannesburg II

zscalerthree.net - EMEA - Johannesburg III

zscaler.net - EMEA - Capetown

zscaler.net - EMEA - Johannesburg II

zscaler.net - EMEA - Johannesburg III

zscloud.net - EMEA - Johannesburg III

Message

EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs

Details

EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ..., and EMEA - Manchester I: Zscaler is investigating reports of an issue with our Manchester I datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to ...

March 15, 2024 08:56 UTC

WARN

less than a minute

APAC - Chennai II: Chennai II Datacenter Issue, APAC - Singapore IV: Singapore IV Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

See more
Start Time

March 15, 2024 08:56 UTC

Type WARN
Affected Components

zscaler.net - EMEA - Johannesburg III

zscalertwo.net - EMEA - Johannesburg III

zscalerthree.net - EMEA - Johannesburg III

zscloud.net - EMEA - Johannesburg III

Message

APAC - Chennai II: Chennai II Datacenter Issue, APAC - Singapore IV: Singapore IV Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

Details

APAC - Chennai II: Zscaler has detected an issue with our Chennai II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For more information, please check our ..., APAC - Singapore IV: We are investigating an issue with our Singapore IV datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...

March 15, 2024 08:56 UTC

WARN

about 1 month

APAC - Chennai II: Chennai II Datacenter Issue, APAC - Singapore IV: Singapore IV Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

See more
Start Time

March 15, 2024 08:56 UTC

Type WARN
Affected Components

zscaler.net - EMEA - Johannesburg III

zscalertwo.net - EMEA - Johannesburg III

zscalerthree.net - EMEA - Johannesburg III

zscloud.net - EMEA - Johannesburg III

Message

APAC - Chennai II: Chennai II Datacenter Issue, APAC - Singapore IV: Singapore IV Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Capetown: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

Details

APAC - Chennai II: Zscaler has detected an issue with our Chennai II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For more information, please check our ..., APAC - Singapore IV: We are investigating an issue with our Singapore IV datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Capetown: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg II: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., EMEA - Johannesburg III: Zscaler has detected an issue with our Capetown, Johannesburg II, Johannesburg III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require ..., and EMEA - Stockholm III: Zscaler has detected an issue with our Stockholm III datacenter. Traffic has been re-routed to the next closest datacenter while we investigate. For more information, please check our FAQ. If ...

December 22, 2023 06:16 UTC

WARN

less than a minute

APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, and APAC - Shanghai II: Shanghai II Datacenter Issue

See more
Start Time

December 22, 2023 06:16 UTC

Type WARN
Affected Components

zscalertwo.net - EMEA - Johannesburg III

zscloud.net - EMEA - Johannesburg III

zscaler.net - EMEA - Capetown IV

zscaler.net - EMEA - Johannesburg III

zscalertwo.net - EMEA - Capetown IV

zscloud.net - EMEA - Capetown IV

zscalerthree.net - EMEA - Capetown IV

zscalerthree.net - EMEA - Johannesburg III

Message

APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, APAC - Shanghai II: Shanghai II Datacenter Issue, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, Core Cloud Services - Security: Sandbox Issue, and APAC - Shanghai II: Shanghai II Datacenter Issue

Details

APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., EMEA - London V: We are currently investigating an issue that seems to be related to a Microsoft Geolocation Issue that may be impacting Azure , Office and other Microsoft  login services that have ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., EMEA - London V: We are currently investigating an issue that seems to be related to a Microsoft Geolocation Issue that may be impacting Azure , Office and other Microsoft  login services that have ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., EMEA - London V: We are currently investigating an issue that seems to be related to a Microsoft Geolocation Issue that may be impacting Azure , Office and other Microsoft  login services that have ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ..., EMEA - London V: We are currently investigating an issue that seems to be related to a Microsoft Geolocation Issue that may be impacting Azure , Office and other Microsoft  login services that have ..., Core Cloud Services - Security: We are investigating an issue with Sandbox functionality. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status changes ..., and APAC - Shanghai II: Zscaler has detected an issue with our Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For more information, please check our FAQ. If you need further ...

2024-04-15 04:49:45 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-15 04:49:45 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-15 04:49:45 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-15 04:49:45 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-15 04:49:45 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Zscaler Cloud EMEA - Johannesburg III History

StatusGator has over 4 years of Zscaler Cloud EMEA - Johannesburg III status history.

2 status changes in the last 24 hours

Zscaler Cloud EMEA - Johannesburg III status, last 24 hours:

5:00 AM
11:00 AM
5:00 PM
11:00 PM
5:00 AM
5:00 AM
5:00 PM
5:00 AM
  • Up: 19 hours

  • Warn: 5 hours

  • Down: 0 minutes

  • Maintenance: 0 minutes

Zscaler Cloud EMEA - Johannesburg III Outage and Status History

We've been monitoring Zscaler Cloud EMEA - Johannesburg III outages since October 7, 2019.
Here's the history of service outages we've observed from the Zscaler Cloud EMEA - Johannesburg III Status Page:

Instant enriched data from
3,580 status pages

About Our Zscaler Cloud EMEA - Johannesburg III Status Page Integration

Zscaler Cloud EMEA - Johannesburg III is a Cloud Infrastructure and Security solution that StatusGator has been monitoring since October 2019. Over the past over 4 years, we have collected data on on more than 1,805 outages that affected Zscaler Cloud EMEA - Johannesburg III users. When Zscaler Cloud EMEA - Johannesburg III publishes downtime on their status page, they do so across 518 components and 11 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 - Johannesburg III 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 6,800 notifications to our users about Zscaler Cloud EMEA - Johannesburg III incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Zscaler Cloud EMEA - Johannesburg III 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 - Johannesburg III 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 - Johannesburg III posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Zscaler Cloud EMEA - Johannesburg III enters a pre-planned maintenance window, keeping you up to date.

Zscaler Cloud EMEA - Johannesburg III does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate Zscaler Cloud EMEA - Johannesburg III maintenance events into your unified calendar.

When Zscaler Cloud EMEA - Johannesburg III 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 - Johannesburg III 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 - Johannesburg III 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.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Zscaler Cloud EMEA - Johannesburg III Down?

Are you experiencing issues with Zscaler Cloud EMEA - Johannesburg III? Sign up to receive notifications when Zscaler Cloud EMEA - Johannesburg III publishes outages.

Zscaler Cloud EMEA - Johannesburg III Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,580 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Zscaler Cloud EMEA - Johannesburg III?

Sign up for StatusGator and see all historical information about Zscaler Cloud EMEA - Johannesburg III outages and performance issues. Get free, instant notifications when Zscaler Cloud EMEA - Johannesburg III goes down.