Is Zscaler Cloud APAC - Melbourne II down?
Current Zscaler Cloud APAC - Melbourne II status is UP

We checked the official Zscaler Cloud APAC - Melbourne II Status Page 1 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 APAC - Melbourne II Outages and Issues

Follow the recent outages and downtime for Zscaler Cloud APAC - Melbourne II in the table below.

Start Time

Type

Length

Message

Details

November 23, 2023 01:36 UTC

WARN

ongoing

Core Cloud Services - Content Delivery: Call Quality Monitoring Issue

See more
Start Time

November 23, 2023 01:36 UTC

Type WARN
Affected Components

zscalertwo.net - APAC - Melbourne II

zscalertwo.net - APAC - Sydney III

Message

Core Cloud Services - Content Delivery: Call Quality Monitoring Issue

Details

Core Cloud Services - Content Delivery: We are investigating an issue with Zoom Call Quality Monitoring on our Zscaler Digital Experience cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ...

November 22, 2023 23:06 UTC

WARN

about 3 hours

APAC - Melbourne II: Melbourne II Datacenter Issue and Core Cloud Services - Content Delivery: Call Quality Monitoring Issue

See more
Start Time

November 22, 2023 23:06 UTC

Type WARN
Affected Components

zscalertwo.net - APAC - Melbourne II

Message

APAC - Melbourne II: Melbourne II Datacenter Issue and Core Cloud Services - Content Delivery: Call Quality Monitoring Issue

Details

APAC - Melbourne II: We are investigating an issue with our Melbourne II datacenter. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. ... and Core Cloud Services - Content Delivery: We are investigating an issue with Zoom Call Quality Monitoring on our Zscaler Digital Experience cloud. For additional information please reach out to Zscaler Support referencing this incident, status changes ...

May 25, 2023 17:26 UTC

WARN

less than a minute

APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Shanghai II: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue

See more
Start Time

May 25, 2023 17:26 UTC

Type WARN
Affected Components

zscloud.net - APAC - Sydney III

zscloud.net - APAC - Auckland II

zscalertwo.net - APAC - Sydney III

zscaler.net - APAC - Auckland II

zscloud.net - APAC - Melbourne II

zscaler.net - APAC - Sydney III

zscaler.net - APAC - Melbourne II

zscalertwo.net - APAC - Auckland II

zscalertwo.net - APAC - Melbourne II

zscalerthree.net - APAC - Auckland II

zscalerthree.net - APAC - Melbourne II

zscalerthree.net - APAC - Sydney III

Message

APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Shanghai II: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue

Details

APAC - Kuala Lumpur I: We are investigating an issue with our Kuala Lumpur I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Shanghai II: We are investigating user authentication issue with our Shanghai II datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Beijing III: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai I: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., EMEA - Johannesburg III: We are investigating an issue with our Johannesburg III datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they ..., and EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory.

May 25, 2023 17:26 UTC

WARN

6 months

APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Shanghai II: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue

See more
Start Time

May 25, 2023 17:26 UTC

Type WARN
Affected Components

zscloud.net - APAC - Sydney III

zscloud.net - APAC - Auckland II

zscalertwo.net - APAC - Sydney III

zscaler.net - APAC - Auckland II

zscloud.net - APAC - Melbourne II

zscaler.net - APAC - Sydney III

zscaler.net - APAC - Melbourne II

zscalertwo.net - APAC - Auckland II

zscalertwo.net - APAC - Melbourne II

zscalerthree.net - APAC - Auckland II

zscalerthree.net - APAC - Melbourne II

zscalerthree.net - APAC - Sydney III

Message

APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Shanghai II: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue

Details

APAC - Kuala Lumpur I: We are investigating an issue with our Kuala Lumpur I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Shanghai II: We are investigating user authentication issue with our Shanghai II datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Beijing III: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai I: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., EMEA - Johannesburg III: We are investigating an issue with our Johannesburg III datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they ..., and EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory.

May 25, 2023 15:46 UTC

WARN

less than a minute

APAC - Auckland II: User Authentication Issues, APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, APAC - Melbourne II: User Authentication Issues, APAC - Sydney III: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Auckland II: User Authentication Issues, APAC - Melbourne II: User Authentication Issues, APAC - Sydney III: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Auckland II: User Authentication Issues, APAC - Melbourne II: User Authentication Issues, APAC - Shanghai II: User Authentication Issues, APAC - Sydney III: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Auckland II: User Authentication Issues, APAC - Melbourne II: User Authentication Issues, APAC - Sydney III: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue

See more
Start Time

May 25, 2023 15:46 UTC

Type WARN
Affected Components

zscloud.net - APAC - Sydney III

zscaler.net - APAC - Melbourne II

zscloud.net - APAC - Auckland II

zscaler.net - APAC - Sydney III

zscalertwo.net - APAC - Melbourne II

zscalerthree.net - APAC - Auckland II

zscalerthree.net - APAC - Melbourne II

zscalerthree.net - APAC - Sydney III

zscalertwo.net - APAC - Sydney III

zscaler.net - APAC - Auckland II

zscloud.net - APAC - Melbourne II

zscalertwo.net - APAC - Auckland II

Message

APAC - Auckland II: User Authentication Issues, APAC - Kuala Lumpur I: Kuala Lumpur I Datacenter Issue, APAC - Melbourne II: User Authentication Issues, APAC - Sydney III: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Auckland II: User Authentication Issues, APAC - Melbourne II: User Authentication Issues, APAC - Sydney III: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Auckland II: User Authentication Issues, APAC - Melbourne II: User Authentication Issues, APAC - Shanghai II: User Authentication Issues, APAC - Sydney III: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Auckland II: User Authentication Issues, APAC - Melbourne II: User Authentication Issues, APAC - Sydney III: User Authentication Issues, EMEA - Moscow III: Moscow III Datacenter Issue, APAC - Beijing III: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Beijing II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai I: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, APAC - Shanghai II: Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue

Details

APAC - Auckland II: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., APAC - Kuala Lumpur I: We are investigating an issue with our Kuala Lumpur I datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., APAC - Melbourne II: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., APAC - Sydney III: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Auckland II: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., APAC - Melbourne II: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., APAC - Sydney III: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Auckland II: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., APAC - Melbourne II: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., APAC - Shanghai II: We are investigating user authentication issue with our Shanghai II datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as ..., APAC - Sydney III: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Auckland II: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., APAC - Melbourne II: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., APAC - Sydney III: We are investigating user authentication issue with our Auckland II, Melbourne II, Sydney III datacenters. We are investigating periods of slowness and/or increased latency. For additional information please reach out to ..., EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory., APAC - Beijing III: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Beijing II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai I: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Beijing, Beijing II, Shanghai I, Shanghai II datacenter. We are investigating periods of slowness and/or increased latency. For additional information please ..., EMEA - Johannesburg III: We are investigating an issue with our Johannesburg III datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they ..., and EMEA - Moscow III: We are investigating an issue with our Moscow III datacenter, some domestic and international traffic destinations may be impacted. For additional information please reference the following Advisory.

2024-04-11 09:55:47 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-11 09:55:47 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-11 09:55:47 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-11 09:55:47 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-11 09:55:47 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Zscaler Cloud APAC - Melbourne II History

StatusGator has over 4 years of Zscaler Cloud APAC - Melbourne II status history.

No outages or status changes in the last 24 hours

Zscaler Cloud APAC - Melbourne II status, last 24 hours:

10:00 AM
4:00 PM
10:00 PM
4:00 AM
10:00 AM
10:00 AM
10:00 PM
10:00 AM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

  • Maintenance: 0 minutes

Zscaler Cloud APAC - Melbourne II Outage and Status History

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

April 2024

March 2024

February 2024

  • Up

  • Warn

  • Down

  • Maintenance

Instant enriched data from
3,580 status pages

About Our Zscaler Cloud APAC - Melbourne II Status Page Integration

Zscaler Cloud APAC - Melbourne II 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 APAC - Melbourne II users. When Zscaler Cloud APAC - Melbourne II 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 APAC - Melbourne II 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 APAC - Melbourne II incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

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

Zscaler Cloud APAC - Melbourne II 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 APAC - Melbourne II maintenance events into your unified calendar.

When Zscaler Cloud APAC - Melbourne II 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 APAC - Melbourne II 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 APAC - Melbourne II 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 APAC - Melbourne II Down?

Are you experiencing issues with Zscaler Cloud APAC - Melbourne II? Sign up to receive notifications when Zscaler Cloud APAC - Melbourne II publishes outages.

Zscaler Cloud APAC - Melbourne II 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 APAC - Melbourne II?

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