dbt Cloud Outage History

There were 292 dbt Cloud outages since February 4, 2026 totaling 2h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor March 26, 2026

[US Cell 4 AWS] Experiencing issues with Copilot/AI functionality due to OpenAI outage

Detected by Pingoru: Mar 26, 2026, 11:23 PM UTC
Resolved: Mar 26, 2026, 11:23 PM UTC
Duration: —

Timeline · 3 updates

investigating Mar 26, 2026, 10:02 PM UTC

Status: Investigating We're currently experiencing some issues due to the current outage with OpenAI: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP Will be providing updates as soon as more information becomes available. Affected components dbt Copilot (US Cell 4 AWS) (Partial outage)
identified Mar 26, 2026, 10:03 PM UTC

Status: Identified We're currently experiencing some issues due to the current outage with OpenAI: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP Will be providing updates as soon as more information becomes available. Affected components dbt Copilot (US Cell 4 AWS) (Partial outage)
resolved Mar 26, 2026, 11:23 PM UTC

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (US Cell 4 AWS) (Operational)

Read the full incident report →

Major March 26, 2026

Experiencing issues with Copilot/AI functionality due to OpenAI outage

Detected by Pingoru: Mar 26, 2026, 10:02 PM UTC
Resolved: Mar 26, 2026, 11:23 PM UTC
Duration: 1h 21m

Read the full incident report →

Minor March 26, 2026

[US Cell 1 AWS] Job Notifications delayed

Detected by Pingoru: Mar 26, 2026, 08:28 PM UTC
Resolved: Mar 26, 2026, 08:28 PM UTC
Duration: —

Timeline · 2 updates

identified Mar 26, 2026, 06:27 AM UTC

Status: Identified We have identified an issue with webhooks that resulted in job notifications being delayed. A fix has been implemented. Affected components Web Application (US Cell 1 AWS) (Operational) dbt Copilot (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational) Semantic Layer API (US Cell 1 AWS) (Operational) Admin API (US Cell 1 AWS) (Operational) Metadata API (US Cell 1 AWS) (Operational) Metadata Ingestion (US Cell 1 AWS) (Operational) Scheduled Jobs (US Cell 1 AWS) (Partial outage) dbt platform CLI (US Cell 1 AWS) (Operational)
resolved Mar 26, 2026, 08:28 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are functioning normally as of 3:28 PM Eastern. Between 1:27 AM Eastern and 3:28 PM Eastern an issue with webhooks resulted in job notification delays where notifications were not sent until 3:28 PM Eastern. We have put measures in place to prevent a recurrence and the job notifications have 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 Metadata Ingestion (US Cell 1 AWS) (Operational) Web Application (US Cell 1 AWS) (Operational) Admin API (US Cell 1 AWS) (Operational) dbt Copilot (US Cell 1 AWS) (Operational) Semantic Layer API (US Cell 1 AWS) (Operational) Scheduled Jobs (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational) Metadata API (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 26, 2026

[US AWS] Orchestration jobs failing

Detected by Pingoru: Mar 26, 2026, 07:42 PM UTC
Resolved: Mar 26, 2026, 07:42 PM UTC
Duration: —

Timeline · 3 updates

identified Mar 26, 2026, 06:10 PM UTC

Status: Identified We have identified an issue with orchestration jobs that resulted in source freshness and compare steps failing for customers in multiple accounts. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US AWS) (Degraded performance)
monitoring Mar 26, 2026, 07:02 PM UTC

Status: Monitoring We have deployed a fix for orchestration job that was causing source freshness and compare steps failing for customers in multiple accounts. The orchestration job has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (US AWS) (Operational)
resolved Mar 26, 2026, 07:42 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of Mar 26 5:33PM UTC. Between Mar 25 10PM UTC and Mar 26 5:33PM UTC an issue with orchestration job resulted in source freshness and compare steps failing for customers in multiple accounts. We have put measures in place to prevent a recurrence and the orchestration job 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 March 26, 2026

[US Cell 1 AWS] Orchestration jobs failing

Detected by Pingoru: Mar 26, 2026, 07:42 PM UTC
Resolved: Mar 26, 2026, 07:42 PM UTC
Duration: —

Timeline · 3 updates

identified Mar 26, 2026, 06:10 PM UTC

Status: Identified We have identified an issue with orchestration jobs that resulted in source freshness and compare steps failing for customers in multiple accounts. A fix is being implemented, and we will provide an update shortly.
monitoring Mar 26, 2026, 07:02 PM UTC

Status: Monitoring We have deployed a fix for orchestration job that was causing source freshness and compare steps failing for customers in multiple accounts. The orchestration job has returned to its normal state and we are continuing to monitor.
resolved Mar 26, 2026, 07:42 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of Mar 26 5:33PM UTC. Between Mar 25 10PM UTC and Mar 26 5:33PM UTC an issue with orchestration job resulted in source freshness and compare steps failing for customers in multiple accounts. We have put measures in place to prevent a recurrence and the orchestration job 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.

Read the full incident report →

Minor March 26, 2026

[US Cell 2 AWS] Orchestration jobs failing

Detected by Pingoru: Mar 26, 2026, 07:42 PM UTC
Resolved: Mar 26, 2026, 07:42 PM UTC
Duration: —

Timeline · 3 updates

identified Mar 26, 2026, 06:10 PM UTC

Status: Identified We have identified an issue with orchestration jobs that resulted in source freshness and compare steps failing for customers in multiple accounts. A fix is being implemented, and we will provide an update shortly.
monitoring Mar 26, 2026, 07:02 PM UTC

Status: Monitoring We have deployed a fix for orchestration job that was causing source freshness and compare steps failing for customers in multiple accounts. The orchestration job has returned to its normal state and we are continuing to monitor.
resolved Mar 26, 2026, 07:42 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of Mar 26 5:33PM UTC. Between Mar 25 10PM UTC and Mar 26 5:33PM UTC an issue with orchestration job resulted in source freshness and compare steps failing for customers in multiple accounts. We have put measures in place to prevent a recurrence and the orchestration job 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.

Read the full incident report →

Minor March 26, 2026

Orchestration jobs failing

Detected by Pingoru: Mar 26, 2026, 06:10 PM UTC
Resolved: Mar 26, 2026, 07:42 PM UTC
Duration: 1h 31m

Read the full incident report →

Minor March 17, 2026

[APAC AWS] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Web Application (APAC AWS) (Degraded performance) Admin API (APAC AWS) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Web Application (APAC AWS) (Degraded performance) Admin API (APAC AWS) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Web Application (APAC AWS) (Operational) Admin API (APAC AWS) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Web Application (APAC AWS) (Operational) Admin API (APAC AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[EMEA AWS] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Web Application (EMEA AWS) (Degraded performance) Admin API (EMEA AWS) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Admin API (EMEA AWS) (Degraded performance) Web Application (EMEA AWS) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Admin API (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Web Application (EMEA AWS) (Operational) Admin API (EMEA AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[EMEA Cell 1 AZURE] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Web Application (EMEA Cell 1 AZURE) (Degraded performance) Admin API (EMEA Cell 1 AZURE) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Admin API (EMEA Cell 1 AZURE) (Degraded performance) Web Application (EMEA Cell 1 AZURE) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Web Application (EMEA Cell 1 AZURE) (Operational) Admin API (EMEA Cell 1 AZURE) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Web Application (EMEA Cell 1 AZURE) (Operational) Admin API (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 17, 2026

[EU Cell 1 GCP] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Admin API (EU Cell 1 GCP) (Degraded performance) Web Application (EU Cell 1 GCP) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Admin API (EU Cell 1 GCP) (Degraded performance) Web Application (EU Cell 1 GCP) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Web Application (EU Cell 1 GCP) (Operational) Admin API (EU Cell 1 GCP) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Admin API (EU Cell 1 GCP) (Operational) Web Application (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 17, 2026

[EU4 Cell 1 GCP] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Web Application (EU4 Cell 1 GCP) (Degraded performance) Admin API (EU4 Cell 1 GCP) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Admin API (EU4 Cell 1 GCP) (Degraded performance) Web Application (EU4 Cell 1 GCP) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Web Application (EU4 Cell 1 GCP) (Operational) Admin API (EU4 Cell 1 GCP) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Web Application (EU4 Cell 1 GCP) (Operational) Admin API (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 17, 2026

[JP Cell 1 AWS] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Admin API (JP Cell 1 AWS) (Degraded performance) Web Application (JP Cell 1 AWS) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Admin API (JP Cell 1 AWS) (Degraded performance) Web Application (JP Cell 1 AWS) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Admin API (JP Cell 1 AWS) (Operational) Web Application (JP Cell 1 AWS) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Admin API (JP Cell 1 AWS) (Operational) Web Application (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US AWS] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Web Application (US AWS) (Degraded performance) Admin API (US AWS) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Web Application (US AWS) (Degraded performance) Admin API (US AWS) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Admin API (US AWS) (Operational) Web Application (US AWS) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Web Application (US AWS) (Operational) Admin API (US AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 1 AWS] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Admin API (US Cell 1 AWS) (Degraded performance) Web Application (US Cell 1 AWS) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Web Application (US Cell 1 AWS) (Degraded performance) Admin API (US Cell 1 AWS) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Web Application (US Cell 1 AWS) (Operational) Admin API (US Cell 1 AWS) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Web Application (US Cell 1 AWS) (Operational) Admin API (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 1 AZURE] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Admin API (US Cell 1 AZURE) (Degraded performance) Web Application (US Cell 1 AZURE) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Admin API (US Cell 1 AZURE) (Degraded performance) Web Application (US Cell 1 AZURE) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Web Application (US Cell 1 AZURE) (Operational) Admin API (US Cell 1 AZURE) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Admin API (US Cell 1 AZURE) (Operational) Web Application (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 1 GCP] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Web Application (US Cell 1 GCP) (Degraded performance) Admin API (US Cell 1 GCP) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Web Application (US Cell 1 GCP) (Degraded performance) Admin API (US Cell 1 GCP) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Admin API (US Cell 1 GCP) (Operational) Web Application (US Cell 1 GCP) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Admin API (US Cell 1 GCP) (Operational) Web Application (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 2 AWS] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Web Application (US Cell 2 AWS) (Degraded performance) Admin API (US Cell 2 AWS) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Web Application (US Cell 2 AWS) (Degraded performance) Admin API (US Cell 2 AWS) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Web Application (US Cell 2 AWS) (Operational) Admin API (US Cell 2 AWS) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Admin API (US Cell 2 AWS) (Operational) Web Application (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 3 AWS] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Admin API (US Cell 3 AWS) (Degraded performance) Web Application (US Cell 3 AWS) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Web Application (US Cell 3 AWS) (Degraded performance) Admin API (US Cell 3 AWS) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Web Application (US Cell 3 AWS) (Operational) Admin API (US Cell 3 AWS) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Admin API (US Cell 3 AWS) (Operational) Web Application (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 4 AWS] Audit Log Events Delayed

Detected by Pingoru: Mar 17, 2026, 04:27 AM UTC
Resolved: Mar 17, 2026, 04:27 AM UTC
Duration: —

Timeline · 4 updates

investigating Mar 17, 2026, 12:45 AM UTC

Status: Investigating We are currently investigating an issue causing delays in audit log event updates. Users may experience delays in seeing recent audit log activity. Our team is working on a resolution and will provide updates every 30 minutes or as new information becomes available. Affected components Web Application (US Cell 4 AWS) (Degraded performance) Admin API (US Cell 4 AWS) (Degraded performance)
identified Mar 17, 2026, 12:46 AM UTC

Status: Identified We have identified the cause of delays in audit log event updates. Our team is actively working on a fix to restore normal performance. We will continue to provide updates every 30 minutes or as new information becomes available. Affected components Admin API (US Cell 4 AWS) (Degraded performance) Web Application (US Cell 4 AWS) (Degraded performance)
monitoring Mar 17, 2026, 01:37 AM UTC

Status: Monitoring We have deployed a fix for the issue that was causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC. Audit log events are now processing normally, and we are continuing to monitor. If you are experiencing any unexpected behaviour, please reach out to [email protected]. Affected components Admin API (US Cell 4 AWS) (Operational) Web Application (US Cell 4 AWS) (Operational)
resolved Mar 17, 2026, 04:27 AM UTC

Status: Resolved The issue causing delays in audit log event updates between 16 Mar 10:45 PM UTC and 17 Mar 1:13 AM UTC has been fully resolved. Audit log events are now processing normally. If you continue to experience delays and are unsure of the root cause, please contact Support at [email protected]. Affected components Web Application (US Cell 4 AWS) (Operational) Admin API (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[APAC AWS] Studio Errors with Snowflake OAuth Authentication

Detected by Pingoru: Mar 17, 2026, 02:28 AM UTC
Resolved: Mar 17, 2026, 02:28 AM UTC
Duration: —

Timeline · 8 updates

investigating Mar 12, 2026, 11:14 PM UTC

Status: Investigating We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error: Error Configuration Error: Snowflake OAuth authentication does not support 'user'. We are actively working on a resolution. We will provide updates approximately every 30 minutes or as soon as new information becomes available. Affected components IDE (APAC AWS) (Degraded performance)
monitoring Mar 12, 2026, 11:32 PM UTC

Status: Monitoring A fix has been deployed for the issue affecting some Snowflake OAuth users encountering the error Error Configuration Error: Snowflake OAuth authentication does not support 'user'. when opening dbt Studio IDE and we are seeing signs that the issue has been remediated. We are continuing to monitor the platform to ensure the fix is fully effective. Affected components IDE (APAC AWS) (Operational)
resolved Mar 13, 2026, 12:03 AM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience issues and are unsure of the root cause. Affected components IDE (APAC AWS) (Operational)
identified Mar 13, 2026, 05:05 PM UTC

Status: Identified We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error(s): • dbt1300: [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token.dbt(1300) • [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token A fix is being implemented, and we will provide an update shortly. Affected components IDE (APAC AWS) (Degraded performance)
identified Mar 13, 2026, 05:48 PM UTC

Status: Identified The issue affecting some Snowflake customers using dbt Fusion where users are encountering OAuth issues has a fix identified and currently being validated for similar auth methods. The fix will be released pending successful validation. Affected components IDE (APAC AWS) (Degraded performance)
identified Mar 13, 2026, 08:02 PM UTC

Status: Identified A release for the fix to Fusion is currently underway. We will update once the release is completed. Affected components IDE (APAC AWS) (Degraded performance)
monitoring Mar 13, 2026, 10:19 PM UTC

Status: Monitoring We have deployed a fix for Snowflake OAuth connections on Fusion enabled dbt platform accounts. The dbt Cloud IdE has returned to its normal state and we are continuing to monitor. Affected components IDE (APAC AWS) (Operational)
resolved Mar 17, 2026, 02:28 AM 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 IDE (APAC AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[EMEA AWS] Studio Errors with Snowflake OAuth Authentication

Detected by Pingoru: Mar 17, 2026, 02:28 AM UTC
Resolved: Mar 17, 2026, 02:28 AM UTC
Duration: —

Timeline · 8 updates

investigating Mar 12, 2026, 11:14 PM UTC

Status: Investigating We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error: Error Configuration Error: Snowflake OAuth authentication does not support 'user'. We are actively working on a resolution. We will provide updates approximately every 30 minutes or as soon as new information becomes available. Affected components IDE (EMEA AWS) (Degraded performance)
monitoring Mar 12, 2026, 11:32 PM UTC

Status: Monitoring A fix has been deployed for the issue affecting some Snowflake OAuth users encountering the error Error Configuration Error: Snowflake OAuth authentication does not support 'user'. when opening dbt Studio IDE and we are seeing signs that the issue has been remediated. We are continuing to monitor the platform to ensure the fix is fully effective. Affected components IDE (EMEA AWS) (Operational)
resolved Mar 13, 2026, 12:03 AM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience issues and are unsure of the root cause. Affected components IDE (EMEA AWS) (Operational)
identified Mar 13, 2026, 05:05 PM UTC

Status: Identified We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error(s): • dbt1300: [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token.dbt(1300) • [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA AWS) (Degraded performance)
identified Mar 13, 2026, 05:48 PM UTC

Status: Identified The issue affecting some Snowflake customers using dbt Fusion where users are encountering OAuth issues has a fix identified and currently being validated for similar auth methods. The fix will be released pending successful validation. Affected components IDE (EMEA AWS) (Degraded performance)
identified Mar 13, 2026, 08:02 PM UTC

Status: Identified A release for the fix to Fusion is currently underway. We will update once the release is completed. Affected components IDE (EMEA AWS) (Degraded performance)
monitoring Mar 13, 2026, 10:19 PM UTC

Status: Monitoring We have deployed a fix for Snowflake OAuth connections on Fusion enabled dbt platform accounts. The dbt Cloud IdE has returned to its normal state and we are continuing to monitor. Affected components IDE (EMEA AWS) (Operational)
resolved Mar 17, 2026, 02:28 AM 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 IDE (EMEA AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[EMEA Cell 1 AZURE] Studio Errors with Snowflake OAuth Authentication

Detected by Pingoru: Mar 17, 2026, 02:28 AM UTC
Resolved: Mar 17, 2026, 02:28 AM UTC
Duration: —

Timeline · 8 updates

investigating Mar 12, 2026, 11:14 PM UTC

Status: Investigating We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error: Error Configuration Error: Snowflake OAuth authentication does not support 'user'. We are actively working on a resolution. We will provide updates approximately every 30 minutes or as soon as new information becomes available. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)
monitoring Mar 12, 2026, 11:32 PM UTC

Status: Monitoring A fix has been deployed for the issue affecting some Snowflake OAuth users encountering the error Error Configuration Error: Snowflake OAuth authentication does not support 'user'. when opening dbt Studio IDE and we are seeing signs that the issue has been remediated. We are continuing to monitor the platform to ensure the fix is fully effective. Affected components IDE (EMEA Cell 1 AZURE) (Operational)
resolved Mar 13, 2026, 12:03 AM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience issues and are unsure of the root cause. Affected components IDE (EMEA Cell 1 AZURE) (Operational)
identified Mar 13, 2026, 05:05 PM UTC

Status: Identified We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error(s): • dbt1300: [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token.dbt(1300) • [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)
identified Mar 13, 2026, 05:48 PM UTC

Status: Identified The issue affecting some Snowflake customers using dbt Fusion where users are encountering OAuth issues has a fix identified and currently being validated for similar auth methods. The fix will be released pending successful validation. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)
identified Mar 13, 2026, 08:02 PM UTC

Status: Identified A release for the fix to Fusion is currently underway. We will update once the release is completed. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)
monitoring Mar 13, 2026, 10:19 PM UTC

Status: Monitoring We have deployed a fix for Snowflake OAuth connections on Fusion enabled dbt platform accounts. The dbt Cloud IdE has returned to its normal state and we are continuing to monitor. Affected components IDE (EMEA Cell 1 AZURE) (Operational)
resolved Mar 17, 2026, 02:28 AM 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 IDE (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 17, 2026

[EU Cell 1 GCP] Studio Errors with Snowflake OAuth Authentication

Detected by Pingoru: Mar 17, 2026, 02:28 AM UTC
Resolved: Mar 17, 2026, 02:28 AM UTC
Duration: —

Timeline · 8 updates

investigating Mar 12, 2026, 11:14 PM UTC

Status: Investigating We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error: Error Configuration Error: Snowflake OAuth authentication does not support 'user'. We are actively working on a resolution. We will provide updates approximately every 30 minutes or as soon as new information becomes available. Affected components IDE (EU Cell 1 GCP) (Degraded performance)
monitoring Mar 12, 2026, 11:32 PM UTC

Status: Monitoring A fix has been deployed for the issue affecting some Snowflake OAuth users encountering the error Error Configuration Error: Snowflake OAuth authentication does not support 'user'. when opening dbt Studio IDE and we are seeing signs that the issue has been remediated. We are continuing to monitor the platform to ensure the fix is fully effective. Affected components IDE (EU Cell 1 GCP) (Operational)
resolved Mar 13, 2026, 12:03 AM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience issues and are unsure of the root cause. Affected components IDE (EU Cell 1 GCP) (Operational)
identified Mar 13, 2026, 05:05 PM UTC

Status: Identified We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error(s): • dbt1300: [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token.dbt(1300) • [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU Cell 1 GCP) (Degraded performance)
identified Mar 13, 2026, 05:48 PM UTC

Status: Identified The issue affecting some Snowflake customers using dbt Fusion where users are encountering OAuth issues has a fix identified and currently being validated for similar auth methods. The fix will be released pending successful validation. Affected components IDE (EU Cell 1 GCP) (Degraded performance)
identified Mar 13, 2026, 08:02 PM UTC

Status: Identified A release for the fix to Fusion is currently underway. We will update once the release is completed. Affected components IDE (EU Cell 1 GCP) (Degraded performance)
monitoring Mar 13, 2026, 10:19 PM UTC

Status: Monitoring We have deployed a fix for Snowflake OAuth connections on Fusion enabled dbt platform accounts. The dbt Cloud IdE has returned to its normal state and we are continuing to monitor. Affected components IDE (EU Cell 1 GCP) (Operational)
resolved Mar 17, 2026, 02:28 AM 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 IDE (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 17, 2026

[EU4 Cell 1 GCP] Studio Errors with Snowflake OAuth Authentication

Detected by Pingoru: Mar 17, 2026, 02:28 AM UTC
Resolved: Mar 17, 2026, 02:28 AM UTC
Duration: —

Timeline · 8 updates

investigating Mar 12, 2026, 11:14 PM UTC

Status: Investigating We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error: Error Configuration Error: Snowflake OAuth authentication does not support 'user'. We are actively working on a resolution. We will provide updates approximately every 30 minutes or as soon as new information becomes available. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)
monitoring Mar 12, 2026, 11:32 PM UTC

Status: Monitoring A fix has been deployed for the issue affecting some Snowflake OAuth users encountering the error Error Configuration Error: Snowflake OAuth authentication does not support 'user'. when opening dbt Studio IDE and we are seeing signs that the issue has been remediated. We are continuing to monitor the platform to ensure the fix is fully effective. Affected components IDE (EU4 Cell 1 GCP) (Operational)
resolved Mar 13, 2026, 12:03 AM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience issues and are unsure of the root cause. Affected components IDE (EU4 Cell 1 GCP) (Operational)
identified Mar 13, 2026, 05:05 PM UTC

Status: Identified We’re investigating an issue affecting some Snowflake customers using dbt Fusion where users may encounter the error(s): • dbt1300: [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token.dbt(1300) • [Snowflake] 390309 (08004): The user you were trying to authenticate as differs from the user tied to the access token A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)
identified Mar 13, 2026, 05:48 PM UTC

Status: Identified The issue affecting some Snowflake customers using dbt Fusion where users are encountering OAuth issues has a fix identified and currently being validated for similar auth methods. The fix will be released pending successful validation. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)
identified Mar 13, 2026, 08:02 PM UTC

Status: Identified A release for the fix to Fusion is currently underway. We will update once the release is completed. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)
monitoring Mar 13, 2026, 10:19 PM UTC

Status: Monitoring We have deployed a fix for Snowflake OAuth connections on Fusion enabled dbt platform accounts. The dbt Cloud IdE has returned to its normal state and we are continuing to monitor. Affected components IDE (EU4 Cell 1 GCP) (Operational)
resolved Mar 17, 2026, 02:28 AM 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 IDE (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Looking to track dbt Cloud downtime and outages?

Pingoru polls dbt Cloud's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when dbt Cloud reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track dbt Cloud alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring dbt Cloud for free

5 free monitors · No credit card required