Is Core Cloud Services - Zscaler Cloud Connector Portal down?
Current Core Cloud Services - Zscaler Cloud Connector Portal status is UP

We checked the official Core Cloud Services - Zscaler Cloud Connector Portal Status Page 4 min. 58 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 Core Cloud Services - Zscaler Cloud Connector Portal Outages and Issues

Follow the recent outages and downtime for Core Cloud Services - Zscaler Cloud Connector Portal in the table below.

Start Time

Type

Length

Message

Details

March 23, 2024 14:26 UTC

WARN

ongoing

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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, 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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, 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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

See more
Start Time

March 23, 2024 14:26 UTC

Type WARN
Affected Components

zscaler.net - Core Cloud Services - Authentication

zscaler.net - Core Cloud Services - Traffic Forwarding

zscaler.net - Core Cloud Services - Zscaler Client connector

zscaler.net - Core Cloud Services - Zscaler Cloud Connector Portal

zscaler.net - Core Cloud Services - Admin UI

zscaler.net - Core Cloud Services - Partner Admin UI

zscaler.net - Core Cloud Services - Source IP Anchoring (SIPA)

Message

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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, 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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, 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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

Details

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 - 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 - 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 - 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 - 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 - 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 - 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 - 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 - 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 23, 2024 08:37 UTC

WARN

about 6 hours

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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Zscaler Client connector: Traffic Forwarding Issue, Core Cloud Services - Zscaler Cloud Connector Portal: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Admin UI: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding 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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, 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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

See more
Start Time

March 23, 2024 08:37 UTC

Type WARN
Affected Components

zscaler.net - Core Cloud Services - Zscaler Client connector

zscaler.net - Core Cloud Services - Zscaler Cloud Connector Portal

zscaler.net - Core Cloud Services - Admin UI

Message

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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, Core Cloud Services - Traffic Forwarding: Traffic Forwarding Issue, Core Cloud Services - Zscaler Client connector: Traffic Forwarding Issue, Core Cloud Services - Zscaler Cloud Connector Portal: Traffic Forwarding Issue, Core Cloud Services - Authentication: Traffic Forwarding Issue, Core Cloud Services - Admin UI: Traffic Forwarding Issue, Core Cloud Services - Source IP Anchoring (SIPA): Traffic Forwarding 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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, 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 - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, EMEA - Johannesburg II: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Johannesburg III: Capetown, Johannesburg II, Johannesburg III Datacenter Issue, EMEA - Manchester I: Inaccurate GeoIP resolution for ZIA IPs, and EMEA - Stockholm III: Stockholm III Traffic Rerouted

Details

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 - 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 ..., Core Cloud Services - Traffic Forwarding: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Zscaler Client connector: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Zscaler Cloud Connector Portal: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Authentication: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Admin UI: We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., Core Cloud Services - Source IP Anchoring (SIPA): We are investigating an issue with our zscaler.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support with reference to this incident. Status ..., 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 - 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 - 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 - 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 - 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 - 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 - 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 07, 2024 07:56 UTC

WARN

about 3 hours

Core Cloud Services - Zscaler Client connector: Administration UI and User Authentication Issues, Core Cloud Services - Zscaler Cloud Connector Portal: Administration UI and User Authentication Issues, Core Cloud Services - Authentication: Administration UI and User Authentication Issues, Core Cloud Services - Admin UI: Administration UI and User Authentication Issues, Core Cloud Services - Partner Admin UI: Administration UI and User Authentication Issues, and Core Cloud Services - Source IP Anchoring (SIPA): Administration UI and User Authentication Issues

See more
Start Time

March 07, 2024 07:56 UTC

Type WARN
Affected Components

zscaler.net - Core Cloud Services - Zscaler Client connector

zscaler.net - Core Cloud Services - Zscaler Cloud Connector Portal

zscaler.net - Core Cloud Services - Authentication

zscaler.net - Core Cloud Services - Admin UI

zscaler.net - Core Cloud Services - Partner Admin UI

zscaler.net - Core Cloud Services - Source IP Anchoring (SIPA)

Message

Core Cloud Services - Zscaler Client connector: Administration UI and User Authentication Issues, Core Cloud Services - Zscaler Cloud Connector Portal: Administration UI and User Authentication Issues, Core Cloud Services - Authentication: Administration UI and User Authentication Issues, Core Cloud Services - Admin UI: Administration UI and User Authentication Issues, Core Cloud Services - Partner Admin UI: Administration UI and User Authentication Issues, and Core Cloud Services - Source IP Anchoring (SIPA): Administration UI and User Authentication Issues

Details

Core Cloud Services - Zscaler Client connector: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., Core Cloud Services - Zscaler Cloud Connector Portal: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., Core Cloud Services - Authentication: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., Core Cloud Services - Admin UI: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., Core Cloud Services - Partner Admin UI: We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ..., and Core Cloud Services - Source IP Anchoring (SIPA): We are investigating an issue with the administration UI and user authentication on our zscaler.net Cloud. We are investigating intermittent connection timeouts. For more information, please check our FAQ. If ...

January 05, 2024 07:01 UTC

WARN

2 months

EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, and EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's

See more
Start Time

January 05, 2024 07:01 UTC

Type WARN
Affected Components

zscalerthree.net - Core Cloud Services - Zscaler Cloud Connector Portal

Message

EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, and EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's

Details

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 ..., 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 ..., 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 ..., and 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 ...

January 05, 2024 05:36 UTC

WARN

about 1 hour

EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, and Core Cloud Services - Zscaler Cloud Connector Portal: Zscaler Client Connector Portal

See more
Start Time

January 05, 2024 05:36 UTC

Type WARN
Affected Components

zscalerthree.net - Core Cloud Services - Zscaler Cloud Connector Portal

Message

EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, EMEA - London V: Inaccurate GeoIP resolution for ZIA IP's, and Core Cloud Services - Zscaler Cloud Connector Portal: Zscaler Client Connector Portal

Details

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 ..., 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 ..., 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 ..., 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 ..., and Core Cloud Services - Zscaler Cloud Connector Portal: We are investigating an issue with the Zscaler Client Connector Portal on our zscalerthree.net Cloud. For more information, please check our FAQ. If you need further assistance, contact Zscaler Support ...

2024-04-25 15:45:14 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-25 15:45:14 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-25 15:45:14 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-25 15:45:14 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-25 15:45:14 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Core Cloud Services - Zscaler Cloud Connector Portal History

StatusGator has over 4 years of Core Cloud Services - Zscaler Cloud Connector Portal status history.

No outages or status changes in the last 24 hours

Core Cloud Services - Zscaler Cloud Connector Portal status, last 24 hours:

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

  • Warn: 0 minutes

  • Down: 0 minutes

  • Maintenance: 0 minutes

Core Cloud Services - Zscaler Cloud Connector Portal Outage and Status History

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

  • Up

  • Warn

  • Down

  • Maintenance

Instant enriched data from
3,580 status pages

About Our Core Cloud Services - Zscaler Cloud Connector Portal Status Page Integration

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

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

Core Cloud Services - Zscaler Cloud Connector Portal 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 - Zscaler Cloud Connector Portal maintenance events into your unified calendar.

When Core Cloud Services - Zscaler Cloud Connector Portal 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 - Zscaler Cloud Connector Portal 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 - Zscaler Cloud Connector Portal 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 - Zscaler Cloud Connector Portal Down?

Are you experiencing issues with Core Cloud Services - Zscaler Cloud Connector Portal? Sign up to receive notifications when Core Cloud Services - Zscaler Cloud Connector Portal publishes outages.

Core Cloud Services - Zscaler Cloud Connector Portal 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 - Zscaler Cloud Connector Portal?

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