StatusGator
StatusGator
Sign In Sign Up
Sign In Sign Up

Is Core Cloud Services - Workload Segmentation Cloud down?
Current Core Cloud Services - Workload Segmentation Cloud status is UP

We checked the official Core Cloud Services - Workload Segmentation Cloud Status Page 3 min. 20 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

Start a Free Trial

Recent Core Cloud Services - Workload Segmentation Cloud Outages and Issues

Follow the recent outages and downtime for Core Cloud Services - Workload Segmentation Cloud in the table below.

Start Time

Type

Length

Message

Details

April 07, 2023 22:17 UTC

WARN

ongoing

APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Kuala Lumpur I: Kuala Lumpur I 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 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 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 II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue

 See more
Start Time

April 07, 2023 22:17 UTC

Type WARN
Affected Components

edgewise.services - Core Cloud Services - Workload Segmentation Cloud
Message

APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Kuala Lumpur I: Kuala Lumpur I 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 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 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 II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue
Details

APAC - Beijing III: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - 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.

April 07, 2023 15:41 UTC

WARN

about 7 hours

APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Kuala Lumpur I: Kuala Lumpur I 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 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 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 II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, EMEA - Moscow III: Moscow III Datacenter Issue, and Core Cloud Services - Workload Segmentation Cloud: Zscaler Workload Segmentation Issue

 See more
Start Time

April 07, 2023 15:41 UTC

Type WARN
Affected Components

edgewise.services - Core Cloud Services - Workload Segmentation Cloud
Message

APAC - Beijing III: Beijing III, Shanghai II Datacenter Issue, APAC - Kuala Lumpur I: Kuala Lumpur I 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 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 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 II: Beijing III, Shanghai II Datacenter Issue, EMEA - Moscow III: Moscow III Datacenter Issue, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, EMEA - Moscow III: Moscow III Datacenter Issue, and Core Cloud Services - Workload Segmentation Cloud: Zscaler Workload Segmentation Issue
Details

APAC - Beijing III: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - 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 ..., 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., and Core Cloud Services - Workload Segmentation Cloud: We are investigating an issue with our edgewise.services Cloud in console03. Events may be delayed until this is resolved. For additional information please reach out to Zscaler Support referencing this ...

March 21, 2023 18:01 UTC

WARN

17 days

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, Americas - Sao Paulo II: Sao Paulo II, Sao Paullo IV Datacenter Issue, Americas - Sao Paulo IV: Sao Paulo II, Sao Paullo IV 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, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue

 See more
Start Time

March 21, 2023 18:01 UTC

Type WARN
Affected Components

edgewise.services - Core Cloud Services - Workload Segmentation Cloud
Message

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, Americas - Sao Paulo II: Sao Paulo II, Sao Paullo IV Datacenter Issue, Americas - Sao Paulo IV: Sao Paulo II, Sao Paullo IV 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, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue
Details

APAC - Beijing III: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., EMEA - Capetown: We are investigating an issue with our Capetown datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ..., 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., Americas - Sao Paulo II: We are investigating an issue with our Sao Paulo II and Sao Paullo IV datacenter. We are investigating periods of slowness and/or increased latency. For additional information please reach out ..., Americas - Sao Paulo IV: We are investigating an issue with our Sao Paulo II and Sao Paullo IV datacenter. We are investigating periods of slowness and/or increased latency. For additional information please reach out ..., APAC - Beijing III: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., EMEA - Capetown: We are investigating an issue with our Capetown datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - 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.

March 21, 2023 15:31 UTC

WARN

about 3 hours

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, Americas - Sao Paulo II: Sao Paulo II, Sao Paullo IV Datacenter Issue, Americas - Sao Paulo IV: Sao Paulo II, Sao Paullo IV 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, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, EMEA - Moscow III: Moscow III Datacenter Issue, and Core Cloud Services - Workload Segmentation Cloud: Zscaler Workload Segmentation Issue

 See more
Start Time

March 21, 2023 15:31 UTC

Type WARN
Affected Components

edgewise.services - Core Cloud Services - Workload Segmentation Cloud
Message

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, Americas - Sao Paulo II: Sao Paulo II, Sao Paullo IV Datacenter Issue, Americas - Sao Paulo IV: Sao Paulo II, Sao Paullo IV 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, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, EMEA - Moscow III: Moscow III Datacenter Issue, and Core Cloud Services - Workload Segmentation Cloud: Zscaler Workload Segmentation Issue
Details

APAC - Beijing III: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., EMEA - Capetown: We are investigating an issue with our Capetown datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ..., 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., Americas - Sao Paulo II: We are investigating an issue with our Sao Paulo II and Sao Paullo IV datacenter. We are investigating periods of slowness and/or increased latency. For additional information please reach out ..., Americas - Sao Paulo IV: We are investigating an issue with our Sao Paulo II and Sao Paullo IV datacenter. We are investigating periods of slowness and/or increased latency. For additional information please reach out ..., APAC - Beijing III: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., EMEA - Capetown: We are investigating an issue with our Capetown datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - 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 ..., 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., and Core Cloud Services - Workload Segmentation Cloud: We are investigating an issue with Workload Segmentation on our edgewise.services cloud.  Delays in policy updates may be experienced.  For additional information please reach out to Zscaler Support referencing this ...

March 19, 2023 22:51 UTC

WARN

1 day

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, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue

 See more
Start Time

March 19, 2023 22:51 UTC

Type WARN
Affected Components

edgewise.services - Core Cloud Services - Workload Segmentation Cloud
Message

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, EMEA - Johannesburg III: Johannesburg III Traffic Rerouted, and EMEA - Moscow III: Moscow III Datacenter Issue
Details

APAC - Beijing III: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., EMEA - Capetown: We are investigating an issue with our Capetown datacenter. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., EMEA - Capetown: We are investigating an issue with our Capetown datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., 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, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., APAC - Shanghai: We are investigating an issue with our Shanghai datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any assistance or would ..., APAC - Shanghai II: We are investigating an issue with our Beijing III, Shanghai II datacenters. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. If you require any ..., 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 - 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:35:34 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

2024-04-11 09:35:34 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

2024-04-11 09:35:34 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

2024-04-11 09:35:34 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

2024-04-11 09:35:34 UTC UTC

 STATUS

? minutes

Sign in to view more status history.

 See more

Sign Up for More Core Cloud Services - Workload Segmentation Cloud History

StatusGator has over 4 years of Core Cloud Services - Workload Segmentation Cloud status history.

Sign Up

No outages or status changes in the last 24 hours

Core Cloud Services - Workload Segmentation Cloud 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

Core Cloud Services - Workload Segmentation Cloud Outage and Status History

We've been monitoring Core Cloud Services - Workload Segmentation Cloud outages since October 7, 2019.
Here's the history of service outages we've observed from the Core Cloud Services - Workload Segmentation Cloud Status Page:

April 2024

March 2024

February 2024

  • Up

  • Warn

  • Down

  • Maintenance

Solutions for Everyone
Education
  • Keep students and staff informed
  • Reduce ticket volume
  • Essential for remote learning

Learn more

DevOps
  • Shorten incident downtime
  • Unify maintenance schedules
  • Integrates with incident tools

Learn more

IT Teams
  • Reduce ticket volumes
  • Improve transparency
  • Shorten resolution times

Learn more

Instant enriched data from
3,580 status pages

About Our Core Cloud Services - Workload Segmentation Cloud Status Page Integration

Core Cloud Services - Workload Segmentation Cloud 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 Core Cloud Services - Workload Segmentation Cloud users. When Core Cloud Services - Workload Segmentation Cloud 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 Core Cloud Services - Workload Segmentation 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 6,800 notifications to our users about Core Cloud Services - Workload Segmentation Cloud incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Core Cloud Services - Workload Segmentation 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 Core Cloud Services - Workload Segmentation 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.

Core Cloud Services - Workload Segmentation Cloud posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Core Cloud Services - Workload Segmentation Cloud enters a pre-planned maintenance window, keeping you up to date.

Core Cloud Services - Workload Segmentation Cloud 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 Core Cloud Services - Workload Segmentation Cloud maintenance events into your unified calendar.

When Core Cloud Services - Workload Segmentation 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 Core Cloud Services - Workload Segmentation 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 Core Cloud Services - Workload Segmentation Cloud 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!

Core Cloud Services - Workload Segmentation Cloud Down?

Are you experiencing issues with Core Cloud Services - Workload Segmentation Cloud? Sign up to receive notifications when Core Cloud Services - Workload Segmentation Cloud publishes outages.

Sign Up

Core Cloud Services - Workload Segmentation Cloud 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 Core Cloud Services - Workload Segmentation Cloud?

Sign up for StatusGator and see all historical information about Core Cloud Services - Workload Segmentation Cloud outages and performance issues. Get free, instant notifications when Core Cloud Services - Workload Segmentation Cloud goes down.