Collibra Outage History
Collibra partial outage · 2 active incidents View live status →Pingoru has recorded 20 incidents for Collibra: 19 in the last 12 months and 6 in the last 90 days.
Incidents, newest first
Notice October 22, 2026 eMudhra CA certificate compromise (industry-wide) – All, GovCloud, AMER, APAC and 7 more
Started Oct 22, 2026, 09:09 PM UTC· resolved Oct 22, 2026, 09:09 PM UTC
- investigating Oct 22, 2026, 09:09 PM UTC
Description: On October 20, 2026, eMudhra announced the compromise of private keys for eight intermediate certificate authority certificates. Follow eMudhra’s updates on the incident here. As of this update, Collibra Security and Engineering have not identified any risk of harm to Collibra environments or customer data. We continue to assess and address impacted resources as needed, and we will provide updates accordingly.
Major October 22, 2026 PHP2Shell vulnerabilities (industry-wide) 15d 8h All, GovCloud, AMER, APAC and 7 more
Started Oct 22, 2026, 12:00 PM UTC· resolved Nov 06, 2026, 08:57 PM UTC
- investigating Oct 22, 2026, 12:00 PM UTC
Description: On October 21, 2026, security researchers disclosed two critical remote code execution vulnerabilities in core PHP memory-handling routines, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). The vulnerabilities affect servers running vulnerable PHP runtimes. As of this update, Collibra Security and Engineering have not identified any impact to Collibra products, hosted services, or customer data. Collibra’s platform and customer-facing application infrastructure do not run on PHP. We continue to assess our environments and third-party vendors, and we will provide updates accordingly.
Notice October 22, 2026 eMudhra CA certificate compromise (industry-wide) – All, GovCloud, AMER, APAC and 7 more
Started Oct 22, 2026, 12:00 PM UTC· resolved Oct 22, 2026, 12:00 PM UTC
- investigating Oct 22, 2026, 12:00 PM UTC
Description: On October 20, 2026, eMudhra announced the compromise of private keys for eight intermediate certificate authority certificates. Follow eMudhra’s updates on the incident here . As of this update, Collibra Security and Engineering have not identified any risk of harm to Collibra environments or customer data. We continue to assess and address impacted resources as needed, and we will provide updates accordingly.
Major October 20, 2026 Collibra disruption 5h 10m AMER, APAC, EMEA, AI Governance & Privacy and 5 more
Started Oct 20, 2026, 07:16 AM UTC· resolved Oct 20, 2026, 12:26 PM UTC
- investigating Oct 20, 2026, 07:16 AM UTC
Description: An issue affecting EMEA has been detected. Symptoms: Some customers in GCP eu-west2 region may be unable to access their Collibra environment, or may see intermittent errors (such as 503 responses) and slow performance(timeouts). Services running in the region may also be briefly interrupted. The incident stems from a network issue at our cloud provider, Google Cloud, which has confirmed it is affecting multiple services in GCP eu-west2. Our engineers are working with Google and monitoring recovery. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating Oct 20, 2026, 08:44 AM UTC
A subset of Collibra environments hosted in GCP europe-west2 may still be unreachable or experiencing timeouts and 503 errors. Additionally, Lineage (new jobs) and Collibra Edge may be impacted across all clouds and regions.
- investigating Oct 20, 2026, 09:33 AM UTC
Collibra environments hosted in GCP europe-west2 are in recovery. Please note that the overall remediation activities are still in progress and moderate impact is still to be expected.
- resolved Oct 20, 2026, 12:26 PM UTC
All Collibra environments hosted in GCP europe-west2 have been successfully restored, and Lineage and Collibra Edge are fully operational in all regions. Remediation activities are complete, and all services are now operating normally. Recommended action: Please review any scheduled ingestions and lineage jobs that ran between 6:00 AM and 12:20 PM UTC and retry any that failed. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20102026”.
Major July 24, 2026 Duplicate External Mapping ID Disruption 21d 1h AMER, APAC, EMEA, Lineage and Integrations
Started Jul 24, 2026, 03:08 PM UTC· resolved Aug 14, 2026, 04:45 PM UTC
- monitoring Jul 24, 2026, 03:08 PM UTC
Description: A possible issue affecting Duplicate External Mapping ID has been detected. Symptoms description: When running both a JDBC scalable/delta ingestion and an API-based ingestion, both run under the same system. Collibra Engineering recommends that customers do the following: Do NOT to run JDBC scalable/delta ingestion for BigQuery, Databricks, or SAP for the same system asset. We are actively working on a permanent code fix for the underlying collision issue. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating Jul 24, 2026, 03:08 PM UTC
Description: A possible issue affecting Duplicate External Mapping ID has been detected. Symptoms description: When running both a JDBC scalable/delta ingestion and an API-based ingestion, both run under the same system. Collibra Engineering recommends that customers do the following: Do NOT to run JDBC scalable/delta ingestion for BigQuery, Databricks, or SAP for the same system asset. We are actively working on a permanent code fix for the underlying collision issue. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Aug 14, 2026, 04:45 PM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260814”.
- resolved Aug 14, 2026, 04:45 PM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260814”.
Major June 29, 2026 Data Governance disruption 5m EMEA, Data Governance
Started Jun 29, 2026, 08:45 AM UTC· resolved Jun 29, 2026, 08:50 AM UTC
- monitoring Jun 29, 2026, 08:45 AM UTC
Description: A possible issue affecting Data Governance has been detected. Search service impacted. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating Jun 29, 2026, 08:45 AM UTC
Description: A possible issue affecting Data Governance has been detected. Search service impacted. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Jun 29, 2026, 08:50 AM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260629”.
- resolved Jun 29, 2026, 08:50 AM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260629”.
Major June 15, 2026 Lineage and Integrations unavailable 47m AMER, APAC, EMEA, Lineage and Integrations
Started Jun 15, 2026, 10:08 AM UTC· resolved Jun 15, 2026, 10:55 AM UTC
- monitoring Jun 15, 2026, 10:08 AM UTC
Description: An issue affecting Lineage and Integrations has been detected. Symptoms description: Technical Lineage is currently unavailable. Collibra Engineering is working to restore the service and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- identified Jun 15, 2026, 10:08 AM UTC
Description: An issue affecting Lineage and Integrations has been detected. Symptoms description: Technical Lineage is currently unavailable. Collibra Engineering is working to restore the service and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Jun 15, 2026, 10:55 AM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260615”.
- resolved Jun 15, 2026, 10:55 AM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260615”.
Major June 11, 2026 Lineage and Integrations disruption 14m AMER, APAC, EMEA, Lineage and Integrations
Started Jun 11, 2026, 08:48 AM UTC· resolved Jun 11, 2026, 09:02 AM UTC
- monitoring Jun 11, 2026, 08:48 AM UTC
Description: A possible issue affecting Lineage and Integrations has been detected. Symptoms description: Customers using version 2026.05 may be unable to ingest data from their data sources. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating Jun 11, 2026, 08:48 AM UTC
Description: A possible issue affecting Lineage and Integrations has been detected. Symptoms description: Customers using version 2026.05 may be unable to ingest data from their data sources. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Jun 11, 2026, 09:02 AM UTC
Collibra Engineering has identified the root cause and implemented a fix. The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20261106”.
- resolved Jun 11, 2026, 09:02 AM UTC
Collibra Engineering has identified the root cause and implemented a fix. The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20261106”.
- monitoring Jun 15, 2026, 01:50 PM UTC
Customer-facing RCA for this incident can be downloaded here.
Major May 8, 2026 AWS US-EAST-1 disruption 3d 7h AMER, AI Governance & Privacy, Core Platform, Data Governance and 3 more
Started May 08, 2026, 12:55 AM UTC· resolved May 11, 2026, 08:19 AM UTC
- monitoring May 08, 2026, 12:55 AM UTC
Description: An issue affecting cloud services in AWS Region US-EAST-1 has been detected. Symptoms description: Collibra instances in this region may be unreachable. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating May 08, 2026, 12:55 AM UTC
Description: An issue affecting cloud services in AWS Region US-EAST-1 has been detected. Symptoms description: Collibra instances in this region may be unreachable. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring May 08, 2026, 07:13 AM UTC
Description: Recovery efforts continue for the issue affecting cloud services in AWS Region US-EAST-1. Collibra Engineering is actively working on restoring services, with recovery expected to be completed shortly. Some Collibra instances in this region may still experience intermittent reachability issues while remediation activities continue. Collibra Engineering continues to monitor the situation closely and we will provide further updates as they become available. Please continue to refer to the incident status page for the latest information. Thank you for your continued patience and understanding. We apologize for any inconvenience caused.
- investigating May 08, 2026, 07:13 AM UTC
Collibra Engineering is actively working on restoring services, with recovery expected to be completed shortly. Some Collibra instances in this region may still experience intermittent reachability issues while remediation activities continue. Collibra Engineering continues to monitor the situation closely and we will provide further updates as they become available. Please continue to refer to the incident status page for the latest information. Thank you for your continued patience and understanding. We apologize for any inconvenience caused.
- monitoring May 08, 2026, 01:20 PM UTC
Most Collibra instances have been successfully restored. Our engineering team is working diligently to recover the final remaining systems, and will continue to update the incident status page with new developments. Please note Collibra instances in this region may still experience intermittent issues while AWS continues their data center remediation activities. Thank you for your continued patience and understanding. We apologize for any inconvenience caused.
- investigating May 08, 2026, 01:20 PM UTC
Most Collibra instances have been successfully restored. Our engineering team is working diligently to recover the final remaining systems, and will continue to update the incident status page with new developments. Please note Collibra instances in this region may still experience intermittent issues while AWS continues their data center remediation activities. Thank you for your continued patience and understanding. We apologize for any inconvenience caused.
- monitoring May 11, 2026, 08:19 AM UTC
All remaining Collibra instances have now been successfully restored, and service stability has been confirmed. AWS has completed the primary remediation activities related to this incident. Thank you for your patience and understanding throughout this event. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260507".
- resolved May 11, 2026, 08:19 AM UTC
All remaining Collibra instances have now been successfully restored, and service stability has been confirmed. AWS has completed the primary remediation activities related to this incident. Thank you for your patience and understanding throughout this event. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260507".
Major April 20, 2026 Databricks Synchronization Issue on Edge versions 2025.10.182 and 2026.3.42 1d 8h AMER, APAC, EMEA, Core Platform
Started Apr 20, 2026, 11:42 AM UTC· resolved Apr 21, 2026, 08:00 PM UTC
- monitoring Apr 20, 2026, 11:42 AM UTC
Description: A Databricks synchronization issue has been identified affecting customers on Edge versions 2025.10.182 and 2026.3.42, preventing data import into Collibra Platform. A fix is in progress and will be delivered soon in Edge versions 2025.10.183 and 2026.03.43. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating Apr 20, 2026, 11:42 AM UTC
Description: A Databricks synchronization issue has been identified affecting customers on Edge versions 2025.10.182 and 2026.3.42, preventing data import into Collibra Platform. A fix is in progress and will be delivered soon in Edge versions 2025.10.183 and 2026.03.43. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Apr 21, 2026, 08:00 PM UTC
The issue has been resolved. A fix has been released for Edge versions 2025.10.183 and 2026.03.43. All production DGCs should pick it up within one hour. If an Edge site has automatic upgrades enabled, it will upgrade to the new version automatically. For other sites (automatic upgrade disabled), a message will be displayed in the Edge UI notifying users that a new version is available. Users can trigger the upgrade via that same UI. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260420".
- resolved Apr 21, 2026, 08:00 PM UTC
The issue has been resolved. A fix has been released for Edge versions 2025.10.183 and 2026.03.43. All production DGCs should pick it up within one hour. If an Edge site has automatic upgrades enabled, it will upgrade to the new version automatically. For other sites (automatic upgrade disabled), a message will be displayed in the Edge UI notifying users that a new version is available. Users can trigger the upgrade via that same UI. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260420".
Major April 20, 2026 Data Governance disruption 9h 21m AMER, APAC, EMEA, Data Governance
Started Apr 20, 2026, 09:00 AM UTC· resolved Apr 20, 2026, 06:21 PM UTC
- monitoring Apr 20, 2026, 09:00 AM UTC
Description: A possible issue affecting Data Governance has been detected. Symptoms description: Assessments functionality is currently impacted for Ultimate and Premier package customers due to a licensing issue. The root cause has been identified and Collibra Engineering expects the fix to be completed by end of business U.S. time today. Updates will be provided as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating Apr 20, 2026, 09:00 AM UTC
Description: A possible issue affecting Data Governance has been detected. Symptoms description: Assessments functionality is currently impacted for Ultimate and Premier package customers due to a licensing issue. The root cause has been identified and Collibra Engineering expects the fix to be completed by end of business U.S. time today. Updates will be provided as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Apr 20, 2026, 06:21 PM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260420-2”.
- resolved Apr 20, 2026, 06:21 PM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260420-2”.
Major March 26, 2026 Data Governance disruption 17h 7m Data Governance
Started Mar 26, 2026, 08:39 PM UTC· resolved Mar 27, 2026, 01:46 PM UTC
- monitoring Mar 26, 2026, 08:39 PM UTC
Description: A possible issue affecting Data Governance has been detected. GovCloud customers may experience issues managing capabilities. Specifically, they may be unable to add new capabilities or edit existing connections. In some cases, capabilities may appear with a notification indicating they have been revoked. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating Mar 26, 2026, 08:39 PM UTC
Description: A possible issue affecting Data Governance has been detected. GovCloud customers may experience issues managing capabilities. Specifically, they may be unable to add new capabilities or edit existing connections. In some cases, capabilities may appear with a notification indicating they have been revoked. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Mar 27, 2026, 11:18 AM UTC
Collibra Engineering has rolled out a fix for the underlying issue and continues to monitor the situation to ensure stability. If you continue to experience any issues, please contact Support for further assistance. Thank you for your patience and understanding.
- monitoring Mar 27, 2026, 11:18 AM UTC
Collibra Engineering has rolled out a fix for the underlying issue and continues to monitor the situation to ensure stability. If you continue to experience any issues, please contact Support for further assistance. Thank you for your patience and understanding.
- monitoring Mar 27, 2026, 01:46 PM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter.
- resolved Mar 27, 2026, 01:46 PM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter.
Major March 2, 2026 Lineage Release Postponed 22h 55m AMER, APAC, EMEA, Lineage and Integrations
Started Mar 02, 2026, 09:09 AM UTC· resolved Mar 03, 2026, 08:04 AM UTC
- monitoring Mar 02, 2026, 09:09 AM UTC
Due to an ongoing Incident affecting UAE AWS Region, Collibra has decided to postpone the planned maintenance window for all Collibra customers for today’s Lineage release. An update will be provided when the new maintenance window has been confirmed.
- monitoring Mar 02, 2026, 09:09 AM UTC
Due to an ongoing Incident affecting UAE AWS Region, Collibra has decided to postpone the planned maintenance window for all Collibra customers for today’s Lineage release. An update will be provided when the new maintenance window has been confirmed.
- monitoring Mar 02, 2026, 12:15 PM UTC
Collibra has decided to reschedule the March 2, 2026, planned Lineage maintenance to March 3, 2026. The maintenance will now take place on March 3, 2026, from 7:00 to 12:00 CET.
- in progress Mar 02, 2026, 12:15 PM UTC
Collibra has decided to reschedule the March 2, 2026, planned Lineage maintenance to March 3, 2026. The maintenance will now take place on March 3, 2026, from 7:00 to 12:00 CET.
- monitoring Mar 03, 2026, 08:04 AM UTC
Upgrade completed as planned. No further updates will be issued.
- resolved Mar 03, 2026, 08:04 AM UTC
Upgrade completed as planned. No further updates will be issued.
Major March 1, 2026 UAE AWS Region disruption 157d 5h EMEA, Core Platform
Started Mar 01, 2026, 02:18 PM UTC· resolved Aug 05, 2026, 07:43 PM UTC
- monitoring Mar 01, 2026, 02:18 PM UTC
Description: An issue affecting UAE AWS Region ME-CENTRAL-1 has been detected. Symptoms description: Some Collibra instances in this region are unreachable. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Mar 01, 2026, 02:18 PM UTC
Description: An issue affecting UAE AWS Region ME-CENTRAL-1 has been detected. Symptoms description: Some Collibra instances in this region are unreachable. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Mar 01, 2026, 09:02 PM UTC
Collibra engineers have implemented a workaround and are monitoring system health.
- monitoring Mar 01, 2026, 09:02 PM UTC
Collibra engineers have implemented a workaround and are monitoring system health.
- monitoring Mar 02, 2026, 07:25 AM UTC
We are seeing new impact on other availability zone in the ME region, impacting the availability of a subset of instances. We are monitoring the situation.
- investigating Mar 02, 2026, 07:25 AM UTC
We are seeing new impact on other availability zone in the ME region, impacting the availability of a subset of instances. We are monitoring the situation.
- monitoring Mar 02, 2026, 10:00 PM UTC
Collibra engineers have temporarily moved all affected customer environments to Europe, unless expressly prohibited from doing so, and are actively monitoring system health to maintain operational continuity. While the application is currently accessible, please note the following details regarding your data and specific service usage. Important: Use of Multi-Tenant Products We are currently working with AWS to restore access to your multi-tenant data, which is: Data Notebook Workflow Designer Lineage OAuth Applications (IAM) Our team is actively monitoring system health and collaborating closely with AWS to expedite the data migration process. We are committed to maintaining operational continuity and will provide you with a status update on the data restore by Tuesday, March 3. Please check back here for continuing developments.
- investigating Mar 02, 2026, 10:00 PM UTC
Collibra engineers have temporarily moved all affected customer environments to Europe, unless expressly prohibited from doing so, and are actively monitoring system health to maintain operational continuity. While the application is currently accessible, please note the following details regarding your data and specific service usage. Important: Use of Multi-Tenant Products We are currently working with AWS to restore access to your multi-tenant data, which is: Data Notebook Workflow Designer Lineage OAuth Applications (IAM) Our team is actively monitoring system health and collaborating closely with AWS to expedite the data migration process. We are committed to maintaining operational continuity and will provide you with a status update on the data restore by Tuesday, March 3. Please check back here for continuing developments.
- monitoring Mar 03, 2026, 12:16 PM UTC
Our engineering team continues to work closely with AWS and is actively dedicating resources to resolve this issue as quickly as possible. We appreciate your patience and will keep you informed as we make progress.
- investigating Mar 03, 2026, 12:16 PM UTC
Our engineering team continues to work closely with AWS and is actively dedicating resources to resolve this issue as quickly as possible. We appreciate your patience and will keep you informed as we make progress.
- monitoring Mar 04, 2026, 12:52 PM UTC
AWS continues to make measurable progress in its recovery efforts, and we are steadily regaining greater operational control across impacted services. In parallel, Collibra Engineering is implementing additional contingencies to further strengthen system resilience and safeguard continuity. We remain actively engaged, closely monitoring the environment to ensure stability as recovery advances. We will continue to share updates as progress continues.
- investigating Mar 04, 2026, 12:52 PM UTC
AWS continues to make measurable progress in its recovery efforts, and we are steadily regaining greater operational control across impacted services. In parallel, Collibra Engineering is implementing additional contingencies to further strengthen system resilience and safeguard continuity. We remain actively engaged, closely monitoring the environment to ensure stability as recovery advances. We will continue to share updates as progress continues.
- monitoring Mar 10, 2026, 01:19 PM UTC
AWS recovery efforts are ongoing, and all affected Collibra environments remain stable, supported by Collibra Engineering’s risk mitigation. In line with AWS guidance, Collibra has executed disaster recovery measures for customers with the flexibility to do so, leveraging alternate regions to ensure operational availability as restoration activities advance. We continue to maintain close oversight and remain fully engaged. Updates will be shared promptly if any significant developments occur.
- monitoring Mar 10, 2026, 01:19 PM UTC
AWS recovery efforts are ongoing, and all affected Collibra environments remain stable, supported by Collibra Engineering’s risk mitigation. In line with AWS guidance, Collibra has executed disaster recovery measures for customers with the flexibility to do so, leveraging alternate regions to ensure operational availability as restoration activities advance. We continue to maintain close oversight and remain fully engaged. Updates will be shared promptly if any significant developments occur.
- monitoring Aug 05, 2026, 07:43 PM UTC
Closing issue
- resolved Aug 05, 2026, 07:43 PM UTC
Closing issue
Major February 23, 2026 Core Platform disruption 1h 7m AMER, APAC, EMEA, Core Platform
Started Feb 23, 2026, 08:51 PM UTC· resolved Feb 23, 2026, 09:58 PM UTC
- monitoring Feb 23, 2026, 08:51 PM UTC
Description: A possible issue affecting Core Platform has been detected. Symptoms description: Customers may see impact when attempting to use a multitenant service. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating Feb 23, 2026, 08:51 PM UTC
Description: A possible issue affecting Core Platform has been detected. Symptoms description: Customers may see impact when attempting to use a multitenant service. Collibra Engineering is investigating and we will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Feb 23, 2026, 09:58 PM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260223”.
- resolved Feb 23, 2026, 09:58 PM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260223”.
Major February 6, 2026 Microsoft Power BI degraded services may impact Collibra's Power BI integration 35d 21h AMER, APAC, EMEA, Lineage and Integrations
Started Feb 06, 2026, 04:15 PM UTC· resolved Mar 14, 2026, 01:40 PM UTC
- monitoring Feb 06, 2026, 04:15 PM UTC
Description: Collibra is aware that Microsoft is currently experiencing a service degradation that may cause your Power BI jobs to slow down or time out. If a job fails, we recommend running it again once Microsoft Power BI services are fully restored. Note: While this is a distinct issue, we have escalated it to Microsoft in light of their recent Power BI service instability. We are monitoring the situation closely and will provide updates as they become available. Thank you for your patience and understanding.
- identified Feb 06, 2026, 04:15 PM UTC
Description: Collibra is aware that Microsoft is currently experiencing a service degradation that may cause your Power BI jobs to slow down or time out. If a job fails, we recommend running it again once Microsoft Power BI services are fully restored. Note: While this is a distinct issue, we have escalated it to Microsoft in light of their recent Power BI service instability. We are monitoring the situation closely and will provide updates as they become available. Thank you for your patience and understanding.
- monitoring Feb 11, 2026, 06:20 PM UTC
Description: Since early February, we have identified several performance issues affecting Power BI . Our Engineering team is working closely with Microsoft to determine the cause and implement a resolution. If you encounter any service degradation or slowdowns, please reach out to Collibra Support so we can assist you directly. Thank you for your patience and understanding.
- identified Feb 11, 2026, 06:20 PM UTC
Description: Since early February, we have identified several performance issues affecting Power BI . Our Engineering team is working closely with Microsoft to determine the cause and implement a resolution. If you encounter any service degradation or slowdowns, please reach out to Collibra Support so we can assist you directly. Thank you for your patience and understanding.
- monitoring Feb 17, 2026, 02:34 PM UTC
Microsoft has identified the root cause and has schedule a fix for March 14, 2026. Collibra Engineering is working closely with Microsoft to validate the fix prior to release.
- identified Feb 17, 2026, 02:34 PM UTC
Microsoft has identified the root cause and has schedule a fix for March 14, 2026. Collibra Engineering is working closely with Microsoft to validate the fix prior to release.
- monitoring Mar 14, 2026, 01:40 PM UTC
Microsoft has identified the root cause and has schedule a fix for March 14, 2026.
- resolved Mar 14, 2026, 01:40 PM UTC
Microsoft has identified the root cause and has schedule a fix for March 14, 2026.
Major January 28, 2026 Lineage and Integrations disruption 1d AMER, APAC, EMEA, Lineage and Integrations
Started Jan 28, 2026, 09:21 AM UTC· resolved Jan 29, 2026, 09:49 AM UTC
- monitoring Jan 28, 2026, 09:21 AM UTC
Description: Collibra has identified and resolved the recent issue affecting Microsoft Power BI integrations. The root cause was a change in how Power BI responds to authentication requests, and we have released a fix to restore full service. The fix has been deployed via Edge Release 2025.10.100-2 and 2025.6.219-2. How to receive the fix Edge auto-upgrade users: Your environment has automatically received the fix. Manual upgrade users: Please update to Edge Release 2025.10.100-2 or 2025.6.219-2 to apply the fix. CLI Harvester users: A new package with the fix is available to download here. If you need additional assistance, please contact your Collibra Support team.
- resolved Jan 28, 2026, 09:21 AM UTC
Description: Collibra has identified and resolved the recent issue affecting Microsoft Power BI integrations. The root cause was a change in how Power BI responds to authentication requests, and we have released a fix to restore full service. The fix has been deployed via Edge Release 2025.10.100-2 and 2025.6.219-2. How to receive the fix Edge auto-upgrade users: Your environment has automatically received the fix. Manual upgrade users: Please update to Edge Release 2025.10.100-2 or 2025.6.219-2 to apply the fix. CLI Harvester users: A new package with the fix is available to download here. If you need additional assistance, please contact your Collibra Support team.
- monitoring Jan 29, 2026, 09:49 AM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260127”.
- resolved Jan 29, 2026, 09:49 AM UTC
The issue has been resolved. We apologize for any inconvenience this may have caused, and appreciate your patience while we worked to resolve this matter. A Root Cause Analysis (RCA) document will be published within seven business days and will be available upon request. Please submit a support ticket via support.collibra.com with the following subject line: “RCA Request for Incident MI-20260127”.
Major November 18, 2025 Cloudflare - AMER, EMEA, APAC disruption 5h 17m AMER, APAC, EMEA, AI Governance & Privacy and 5 more
Started Nov 18, 2025, 01:09 PM UTC· resolved Nov 18, 2025, 06:26 PM UTC
- monitoring Nov 18, 2025, 01:09 PM UTC
Description: An issue affecting AMER, EMEA, APAC has been detected. Symptoms description: Some users may experience intermittent issues accessing their Collibra instances due to a Cloudflare global outage. Collibra Engineering will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- investigating Nov 18, 2025, 01:09 PM UTC
Description: An issue affecting AMER, EMEA, APAC has been detected. Symptoms description: Some users may experience intermittent issues accessing their Collibra instances due to a Cloudflare global outage. Collibra Engineering will update you as soon as new information is available. Please check back on the incident status page for developments. Thank you for your patience. Our apologies for any inconvenience caused.
- monitoring Nov 18, 2025, 02:50 PM UTC
Cloudflare has implemented a fix. Collibra Engineering is monitoring the health of our systems.
- monitoring Nov 18, 2025, 02:50 PM UTC
Cloudflare has implemented a fix. Collibra Engineering is monitoring the health of our systems.
- monitoring Nov 18, 2025, 04:31 PM UTC
While the Cloudflare service has improved, intermittent errors are still occurring. The Collibra team is monitoring the situation while Cloudflare continues remediation activities.
- monitoring Nov 18, 2025, 04:31 PM UTC
While the Cloudflare service has improved, intermittent errors are still occurring. The Collibra team is monitoring the situation while Cloudflare continues remediation activities.
- monitoring Nov 18, 2025, 06:26 PM UTC
The intermittent issues have been resolved by Cloudflare, and impacted Collibra instances are now operating normally.
- resolved Nov 18, 2025, 06:26 PM UTC
The intermittent issues have been resolved by Cloudflare, and impacted Collibra instances are now operating normally.