Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Incorta and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Incorta.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Google Cloud Platform Regions | Active |
GCP - Asia North East 1 (Tokyo) | Active |
GCP - Asia South East 1 (Singapore) | Active |
GCP - Europe West 2 (London) | Active |
GCP - Middle East Central 1 (Doha) | Active |
GCP - Middle East Central 2 (Dammam) | Active |
GCP - US Central 1 (Iowa) | Active |
GCP - US West 1 (Oregon) | Active |
Microsoft Azure Regions | Active |
Azure - UAE North (Dubai) | Active |
Azure - UK South (London) | Active |
Azure - West Europe (Netherlands) | Active |
View the latest incidents for Incorta and check for official updates:
Description: The incident has be resolved. Incident Report: ### Summary: On 17 February , Network Data plane Takes Longer than Usual To Initialize. Customers in multiple GCP domains (cloud3, cloud4, cloud5 and cloud6) suffers from spark workloads pending for healthy compute nodes longer than usual. ### Root Cause: Forced upgrade for network data plane leads to degraded performance of network data plane of workers. The aim of the forced upgrade was to provide better secure and performance for management data planes. The forced upgrades was tested in internal different regions, but due to high concurrency and requests in cloud4, cloud5 and cloud6 it took some time to stabilize network data plane. ### Remediation and Prevention: Incorta Cloud Engineers alerted with workloads takes longer than usual, started immediately to investigate and mitigate the. issue within an hour of issue discovery. High demand of spark executors and slowness of spark executors to starts was correlated with the forced upgrade event of the data plane. If your service or application was affected, we apologize — this is not the level of quality and reliability we strive to offer you. Incorta Cloud is committed to preventing a repeat of this issue in the future and is completing the following actions: [Mitigation] Upgrade deprecated compute workloads. [Done] [Prevent] Exclude GKE clusters from the forced upgrade window of cloud provider. [Done] [Monitor] Improve monitoring of spark workload failures in Arcane. [In progress]
Status: Resolved
Impact: Minor | Started At: Feb. 17, 2024, 6:01 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: Oct. 30, 2023, 8:20 p.m.
Description: This incident has been resolved root cause is under investigation
Status: Resolved
Impact: Major | Started At: Aug. 2, 2023, 6:28 p.m.
Description: Partial Service Disturbance in cloud2 Impacted components: cluster connection process Impacted domain: cloud2 Root cause: under investigation
Status: Resolved
Impact: None | Started At: May 15, 2023, 9 a.m.
Description: Issue identified in a communication component between portal and regions fix applied by dropping failed communication from communication queue further analysis is in progress
Status: Resolved
Impact: None | Started At: Feb. 5, 2023, 8:18 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.