dbt Cloud Outage History

dbt Cloud had 438 outages in the last 2 years — averaging 18 incidents per month.

There were 438 dbt Cloud outages since January 27, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor February 26, 2026

[JP Cell 1 AWS] dbt Insights Returning Errors

Detected by Pingoru: Feb 26, 2026, 04:20 PM UTC
Resolved: Feb 26, 2026, 04:20 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 26, 2026, 03:17 PM UTC

Status: Investigating We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Affected components Web Application (JP Cell 1 AWS) (Degraded performance)
monitoring Feb 26, 2026, 04:00 PM UTC

Status: Monitoring We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor. Affected components Web Application (JP Cell 1 AWS) (Operational)
resolved Feb 26, 2026, 04:20 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 26, 2026

[US AWS] dbt Insights Returning Errors

Detected by Pingoru: Feb 26, 2026, 04:20 PM UTC
Resolved: Feb 26, 2026, 04:20 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 26, 2026, 03:17 PM UTC

Status: Investigating We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Affected components Web Application (US AWS) (Degraded performance)
monitoring Feb 26, 2026, 04:00 PM UTC

Status: Monitoring We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor. Affected components Web Application (US AWS) (Operational)
resolved Feb 26, 2026, 04:20 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US AWS) (Operational)

Read the full incident report →

Minor February 26, 2026

[US Cell 1 AWS] dbt Insights Returning Errors

Detected by Pingoru: Feb 26, 2026, 04:20 PM UTC
Resolved: Feb 26, 2026, 04:20 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 26, 2026, 03:17 PM UTC

Status: Investigating We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Affected components Web Application (US Cell 1 AWS) (Degraded performance)
monitoring Feb 26, 2026, 04:00 PM UTC

Status: Monitoring We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 1 AWS) (Operational)
resolved Feb 26, 2026, 04:20 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 26, 2026

[US Cell 1 AZURE] dbt Insights Returning Errors

Detected by Pingoru: Feb 26, 2026, 04:20 PM UTC
Resolved: Feb 26, 2026, 04:20 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 26, 2026, 03:17 PM UTC

Status: Investigating We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Affected components Web Application (US Cell 1 AZURE) (Degraded performance)
monitoring Feb 26, 2026, 04:00 PM UTC

Status: Monitoring We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 1 AZURE) (Operational)
resolved Feb 26, 2026, 04:20 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor February 26, 2026

[US Cell 1 GCP] dbt Insights Returning Errors

Detected by Pingoru: Feb 26, 2026, 04:20 PM UTC
Resolved: Feb 26, 2026, 04:20 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 26, 2026, 03:17 PM UTC

Status: Investigating We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Affected components Web Application (US Cell 1 GCP) (Degraded performance)
monitoring Feb 26, 2026, 04:00 PM UTC

Status: Monitoring We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 1 GCP) (Operational)
resolved Feb 26, 2026, 04:20 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 26, 2026

[US Cell 2 AWS] dbt Insights Returning Errors

Detected by Pingoru: Feb 26, 2026, 04:20 PM UTC
Resolved: Feb 26, 2026, 04:20 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 26, 2026, 03:17 PM UTC

Status: Investigating We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Affected components Web Application (US Cell 2 AWS) (Degraded performance)
monitoring Feb 26, 2026, 04:00 PM UTC

Status: Monitoring We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 2 AWS) (Operational)
resolved Feb 26, 2026, 04:20 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 26, 2026

[US Cell 3 AWS] dbt Insights Returning Errors

Detected by Pingoru: Feb 26, 2026, 04:20 PM UTC
Resolved: Feb 26, 2026, 04:20 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 26, 2026, 03:17 PM UTC

Status: Investigating We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Affected components Web Application (US Cell 3 AWS) (Degraded performance)
monitoring Feb 26, 2026, 04:00 PM UTC

Status: Monitoring We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 3 AWS) (Operational)
resolved Feb 26, 2026, 04:20 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor February 26, 2026

[US Cell 4 AWS] dbt Insights Returning Errors

Detected by Pingoru: Feb 26, 2026, 04:20 PM UTC
Resolved: Feb 26, 2026, 04:20 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 26, 2026, 03:17 PM UTC

Status: Investigating We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Affected components Web Application (US Cell 4 AWS) (Degraded performance)
monitoring Feb 26, 2026, 04:00 PM UTC

Status: Monitoring We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 4 AWS) (Operational)
resolved Feb 26, 2026, 04:20 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[US AWS] Gitlab 403 and 429 Errors

Detected by Pingoru: Feb 25, 2026, 09:20 PM UTC
Resolved: Feb 25, 2026, 09:20 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 25, 2026, 07:49 PM UTC

Status: Identified There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/ Affected components IDE (US AWS) (Degraded performance) dbt platform CLI (US AWS) (Degraded performance)
monitoring Feb 25, 2026, 07:52 PM UTC

Status: Monitoring It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/ Affected components IDE (US AWS) (Degraded performance) dbt platform CLI (US AWS) (Degraded performance)
resolved Feb 25, 2026, 09:20 PM UTC

Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components dbt platform CLI (US AWS) (Operational) IDE (US AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[US Cell 1 AWS] Gitlab 403 and 429 Errors

Detected by Pingoru: Feb 25, 2026, 09:20 PM UTC
Resolved: Feb 25, 2026, 09:20 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 25, 2026, 07:49 PM UTC

Status: Identified There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/ Affected components dbt platform CLI (US Cell 1 AWS) (Degraded performance) IDE (US Cell 1 AWS) (Degraded performance)
monitoring Feb 25, 2026, 07:52 PM UTC

Status: Monitoring It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/ Affected components IDE (US Cell 1 AWS) (Degraded performance) dbt platform CLI (US Cell 1 AWS) (Degraded performance)
resolved Feb 25, 2026, 09:20 PM UTC

Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components dbt platform CLI (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[US Cell 2 AWS] Gitlab 403 and 429 Errors

Detected by Pingoru: Feb 25, 2026, 09:20 PM UTC
Resolved: Feb 25, 2026, 09:20 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 25, 2026, 07:49 PM UTC

Status: Identified There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/ Affected components IDE (US Cell 2 AWS) (Degraded performance) dbt platform CLI (US Cell 2 AWS) (Degraded performance)
monitoring Feb 25, 2026, 07:52 PM UTC

Status: Monitoring It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/ Affected components IDE (US Cell 2 AWS) (Degraded performance) dbt platform CLI (US Cell 2 AWS) (Degraded performance)
resolved Feb 25, 2026, 09:20 PM UTC

Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components dbt platform CLI (US Cell 2 AWS) (Operational) IDE (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[US Cell 3 AWS] Gitlab 403 and 429 Errors

Detected by Pingoru: Feb 25, 2026, 09:20 PM UTC
Resolved: Feb 25, 2026, 09:20 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 25, 2026, 07:49 PM UTC

Status: Identified There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/ Affected components IDE (US Cell 3 AWS) (Degraded performance) dbt platform CLI (US Cell 3 AWS) (Degraded performance)
monitoring Feb 25, 2026, 07:52 PM UTC

Status: Monitoring It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/ Affected components dbt platform CLI (US Cell 3 AWS) (Degraded performance) IDE (US Cell 3 AWS) (Degraded performance)
resolved Feb 25, 2026, 09:20 PM UTC

Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components IDE (US Cell 3 AWS) (Operational) dbt platform CLI (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[US Cell 4 AWS] Gitlab 403 and 429 Errors

Detected by Pingoru: Feb 25, 2026, 09:20 PM UTC
Resolved: Feb 25, 2026, 09:20 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 25, 2026, 07:49 PM UTC

Status: Identified There is currently a GitLab outage that may have some impact on git operations. We are monitoring on our end, please refer to the following statuspage for any more information and to stay up to date: https://status.gitlab.com/ Affected components IDE (US Cell 4 AWS) (Degraded performance) dbt platform CLI (US Cell 4 AWS) (Degraded performance)
monitoring Feb 25, 2026, 07:52 PM UTC

Status: Monitoring It appears that a fix has been shipped and GitLab and will continue to provide updates. More information: https://status.gitlab.com/ Affected components IDE (US Cell 4 AWS) (Degraded performance) dbt platform CLI (US Cell 4 AWS) (Degraded performance)
resolved Feb 25, 2026, 09:20 PM UTC

Status: Resolved This incident has now been resolved. Please refer to GitLab for more details: https://status.gitlab.com/ Affected components IDE (US Cell 4 AWS) (Operational) dbt platform CLI (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[APAC AWS] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (APAC AWS) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (APAC AWS) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (APAC AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[EMEA AWS] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (EMEA AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[EMEA Cell 1 AZURE] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor February 25, 2026

[EU Cell 1 GCP] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (EU Cell 1 GCP) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EU Cell 1 GCP) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 25, 2026

[EU4 Cell 1 GCP] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 25, 2026

[JP Cell 1 AWS] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[US AWS] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US AWS) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US AWS) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[US Cell 1 AWS] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[US Cell 1 AZURE] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor February 25, 2026

[US Cell 1 GCP] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 25, 2026

[US Cell 2 AWS] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 25, 2026

[US Cell 3 AWS] Compare changes job step failing for Databricks users

Detected by Pingoru: Feb 25, 2026, 06:46 PM UTC
Resolved: Feb 25, 2026, 06:46 PM UTC
Duration: —

Timeline · 3 updates

investigating Feb 24, 2026, 10:27 PM UTC

Status: Investigating We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)
identified Feb 24, 2026, 11:07 PM UTC

Status: Identified We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)
resolved Feb 25, 2026, 06:46 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 3 AWS) (Operational)

Read the full incident report →