dbt Cloud Outage History

dbt Cloud is up right now

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

Source: https://status.getdbt.com

Minor March 17, 2026

[JP Cell 1 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
  1. 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.

  2. 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 (JP Cell 1 AWS) (Operational)

  3. 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 (JP Cell 1 AWS) (Operational)

  4. 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 (JP Cell 1 AWS) (Degraded performance)

  5. 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 (JP Cell 1 AWS) (Degraded performance)

  6. 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 (JP Cell 1 AWS) (Degraded performance)

  7. 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 (JP Cell 1 AWS) (Operational)

  8. 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 (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US 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
  1. 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 (US AWS) (Degraded performance)

  2. 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 (US AWS) (Operational)

  3. 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 (US AWS) (Operational)

  4. 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 (US AWS) (Degraded performance)

  5. 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 (US AWS) (Degraded performance)

  6. 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 (US AWS) (Degraded performance)

  7. 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 (US AWS) (Operational)

  8. 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 (US AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 1 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
  1. 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 (US Cell 1 AWS) (Degraded performance)

  2. 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 (US Cell 1 AWS) (Operational)

  3. 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 (US Cell 1 AWS) (Operational)

  4. 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 (US Cell 1 AWS) (Degraded performance)

  5. 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 (US Cell 1 AWS) (Degraded performance)

  6. 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 (US Cell 1 AWS) (Degraded performance)

  7. 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 (US Cell 1 AWS) (Operational)

  8. 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 (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US 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
  1. 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 (US Cell 1 AZURE) (Degraded performance)

  2. 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 (US Cell 1 AZURE) (Operational)

  3. 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 (US Cell 1 AZURE) (Operational)

  4. 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 (US Cell 1 AZURE) (Degraded performance)

  5. 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 (US Cell 1 AZURE) (Degraded performance)

  6. 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 (US Cell 1 AZURE) (Degraded performance)

  7. 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 (US Cell 1 AZURE) (Operational)

  8. 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 (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 17, 2026

[US 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
  1. 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 (US Cell 1 GCP) (Degraded performance)

  2. 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 (US Cell 1 GCP) (Operational)

  3. 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 (US Cell 1 GCP) (Operational)

  4. 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 (US Cell 1 GCP) (Degraded performance)

  5. 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 (US Cell 1 GCP) (Degraded performance)

  6. 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 (US Cell 1 GCP) (Degraded performance)

  7. 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 (US Cell 1 GCP) (Operational)

  8. 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 (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 2 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
  1. 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 (US Cell 2 AWS) (Degraded performance)

  2. 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 (US Cell 2 AWS) (Operational)

  3. 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 (US Cell 2 AWS) (Operational)

  4. 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 (US Cell 2 AWS) (Degraded performance)

  5. 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 (US Cell 2 AWS) (Degraded performance)

  6. 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 (US Cell 2 AWS) (Degraded performance)

  7. 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 (US Cell 2 AWS) (Operational)

  8. 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 (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 3 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
  1. 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 (US Cell 3 AWS) (Degraded performance)

  2. 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 (US Cell 3 AWS) (Operational)

  3. 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 (US Cell 3 AWS) (Operational)

  4. 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 (US Cell 3 AWS) (Degraded performance)

  5. 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 (US Cell 3 AWS) (Degraded performance)

  6. 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 (US Cell 3 AWS) (Degraded performance)

  7. 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 (US Cell 3 AWS) (Operational)

  8. 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 (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor March 17, 2026

[US Cell 4 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
  1. 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 (US Cell 4 AWS) (Degraded performance)

  2. 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 (US Cell 4 AWS) (Operational)

  3. 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 (US Cell 4 AWS) (Operational)

  4. 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 (US Cell 4 AWS) (Degraded performance)

  5. 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 (US Cell 4 AWS) (Degraded performance)

  6. 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 (US Cell 4 AWS) (Degraded performance)

  7. 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 (US Cell 4 AWS) (Operational)

  8. 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 (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor March 11, 2026

[US AWS] Failed Scheduled jobs for Redshift. Runtime Error: 'table_subtype'

Detected by Pingoru
Mar 11, 2026, 09:16 PM UTC
Resolved
Mar 11, 2026, 09:16 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Mar 11, 2026, 03:44 PM UTC

    Status: Investigating We're investigating an issue with Redshift adapter that is causing Runtime Error 'table_subtype'. This is impacting scheduled runs. 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 Scheduled Jobs (US AWS) (Partial outage)

  2. identified Mar 11, 2026, 05:22 PM UTC

    Status: Identified We have identified the root cause of the Redshift runtime error. A fix is being worked on, and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US AWS) (Partial outage)

  3. monitoring Mar 11, 2026, 06:41 PM UTC

    Status: Monitoring We have deployed a fix that was causing Redshift Runtime errors. All components affected has returned to its normal state and we are continuing to monitor. Affected components IDE (US AWS) (Degraded performance) Scheduled Jobs (US AWS) (Degraded performance) dbt platform CLI (US AWS) (Degraded performance)

  4. resolved Mar 11, 2026, 09:16 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 IDE (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational) dbt platform CLI (US AWS) (Operational)

Read the full incident report →

Minor March 9, 2026

[US Cell 1 GCP] dbt cloud application is down in US GCP instance

Detected by Pingoru
Mar 09, 2026, 03:10 PM UTC
Resolved
Mar 09, 2026, 03:10 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Mar 09, 2026, 12:11 PM UTC

    Status: Investigating • We're investigating an issue where dbt Cloud is unavailable in US GCP instance aka us3 instance. The engineering and infrastructure teams have been alerted and are addressing this as a high priority. We will keep the status page "status page": https://status.getdbt.com/ updated as we work on the issue.

  2. identified Mar 09, 2026, 12:47 PM UTC

    Status: Identified We have identified an issue affecting the dbt Cloud application that caused the dbt cloud app to become temporarily unavailable. Our engineering team are working on it, and we will provide another update shortly. Affected components Admin API (US Cell 1 GCP) (Degraded performance) Web Application (US Cell 1 GCP) (Degraded performance)

  3. identified Mar 09, 2026, 02:38 PM UTC

    Status: Identified We have identified an issue affecting the dbt Cloud application that caused it to become temporarily unavailable. Our engineering teams are working on it, and we will provide another update shortly. Affected components Admin API (US Cell 1 GCP) (Full outage) dbt platform CLI (US Cell 1 GCP) (Full outage) Metadata API (US Cell 1 GCP) (Full outage) Semantic Layer API (US Cell 1 GCP) (Full outage) Web Application (US Cell 1 GCP) (Full outage)

  4. monitoring Mar 09, 2026, 02:52 PM UTC

    Status: Monitoring We have deployed a fix for the issue that was causing degradation of the dbt Cloud application. Functionality has been restored, and we are continuing to monitor the system to ensure stability. If you continue to experience any issues, please contact Support at [email protected]. Affected components dbt platform CLI (US Cell 1 GCP) (Operational) Metadata API (US Cell 1 GCP) (Operational) Semantic Layer API (US Cell 1 GCP) (Operational) Web Application (US Cell 1 GCP) (Operational) Admin API (US Cell 1 GCP) (Operational)

  5. resolved Mar 09, 2026, 03:10 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 10:52 AM Eastern. Between 6:30 AM Eastern and 10:52 AM Eastern an issue with the Web Application resulted in multiple services being inaccessible . We have put measures in place to prevent a recurrence and all services 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 Web Application (US Cell 1 GCP) (Operational) Admin API (US Cell 1 GCP) (Operational) dbt platform CLI (US Cell 1 GCP) (Operational) Metadata API (US Cell 1 GCP) (Operational) Semantic Layer API (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 9, 2026

[US Cell 1 AZURE] dbt Studio Unavailable

Detected by Pingoru
Mar 09, 2026, 01:40 PM UTC
Resolved
Mar 09, 2026, 01:40 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Mar 09, 2026, 09:11 AM UTC

    Status: Investigating We're investigating an issue with dbt Studio in Azure US. 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 IDE (US Cell 1 AZURE) (Partial outage)

  2. monitoring Mar 09, 2026, 01:38 PM UTC

    Status: Monitoring We have deployed a fix that was causing issues with dbt Studio. dbt Studio has returned to its normal state and we are continuing to monitor. Affected components IDE (US Cell 1 AZURE) (Degraded performance)

  3. resolved Mar 09, 2026, 01:40 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally/ We have put measures in place to prevent a recurrence and the dbt Studio 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 IDE (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 6, 2026

[APAC AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 (APAC AWS) (Degraded performance) dbt platform CLI (APAC AWS) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (APAC AWS) (Degraded performance) dbt platform CLI (APAC AWS) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (APAC AWS) (Operational) Web Application (APAC AWS) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 (APAC AWS) (Partial outage) dbt platform CLI (APAC AWS) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components IDE (APAC AWS) (Partial outage) dbt platform CLI (APAC AWS) (Partial outage) Web Application (APAC AWS) (Operational)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (APAC AWS) (Operational) Web Application (APAC AWS) (Operational) IDE (APAC AWS) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 IDE (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational) Web Application (APAC AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[EMEA AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 (EMEA AWS) (Degraded performance) dbt platform CLI (EMEA AWS) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (EMEA AWS) (Degraded performance) Web Application (EMEA AWS) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components Web Application (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 (EMEA AWS) (Partial outage) dbt platform CLI (EMEA AWS) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (EMEA AWS) (Partial outage) Web Application (EMEA AWS) (Operational) IDE (EMEA AWS) (Partial outage)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components Web Application (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) IDE (EMEA AWS) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 IDE (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[EMEA Cell 1 AZURE] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 dbt platform CLI (EMEA Cell 1 AZURE) (Degraded performance) Web Application (EMEA Cell 1 AZURE) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (EMEA Cell 1 AZURE) (Degraded performance) dbt platform CLI (EMEA Cell 1 AZURE) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components Web Application (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 dbt platform CLI (EMEA Cell 1 AZURE) (Partial outage) Web Application (EMEA Cell 1 AZURE) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA Cell 1 AZURE) (Partial outage) Web Application (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Partial outage)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components IDE (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Operational) Web Application (EMEA Cell 1 AZURE) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 dbt platform CLI (EMEA Cell 1 AZURE) (Operational) Web Application (EMEA Cell 1 AZURE) (Operational) IDE (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 6, 2026

[EU Cell 1 GCP] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 (EU Cell 1 GCP) (Degraded performance) dbt platform CLI (EU Cell 1 GCP) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (EU Cell 1 GCP) (Degraded performance) Web Application (EU Cell 1 GCP) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components Web Application (EU Cell 1 GCP) (Operational) dbt platform CLI (EU Cell 1 GCP) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 dbt platform CLI (EU Cell 1 GCP) (Partial outage) Web Application (EU Cell 1 GCP) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (EU Cell 1 GCP) (Partial outage) IDE (EU Cell 1 GCP) (Partial outage) Web Application (EU Cell 1 GCP) (Operational)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components IDE (EU Cell 1 GCP) (Operational) dbt platform CLI (EU Cell 1 GCP) (Operational) Web Application (EU Cell 1 GCP) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 dbt platform CLI (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational) Web Application (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 6, 2026

[EU4 Cell 1 GCP] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 dbt platform CLI (EU4 Cell 1 GCP) (Degraded performance) Web Application (EU4 Cell 1 GCP) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (EU4 Cell 1 GCP) (Degraded performance) Web Application (EU4 Cell 1 GCP) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components Web Application (EU4 Cell 1 GCP) (Operational) dbt platform CLI (EU4 Cell 1 GCP) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 dbt platform CLI (EU4 Cell 1 GCP) (Partial outage) Web Application (EU4 Cell 1 GCP) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU4 Cell 1 GCP) (Partial outage) Web Application (EU4 Cell 1 GCP) (Operational) dbt platform CLI (EU4 Cell 1 GCP) (Partial outage)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components Web Application (EU4 Cell 1 GCP) (Operational) IDE (EU4 Cell 1 GCP) (Operational) dbt platform CLI (EU4 Cell 1 GCP) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 IDE (EU4 Cell 1 GCP) (Operational) dbt platform CLI (EU4 Cell 1 GCP) (Operational) Web Application (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 6, 2026

[JP Cell 1 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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) dbt platform CLI (JP Cell 1 AWS) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (JP Cell 1 AWS) (Degraded performance) dbt platform CLI (JP Cell 1 AWS) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components Web Application (JP Cell 1 AWS) (Operational) dbt platform CLI (JP Cell 1 AWS) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 dbt platform CLI (JP Cell 1 AWS) (Partial outage) Web Application (JP Cell 1 AWS) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (JP Cell 1 AWS) (Partial outage) IDE (JP Cell 1 AWS) (Partial outage) Web Application (JP Cell 1 AWS) (Operational)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components Web Application (JP Cell 1 AWS) (Operational) IDE (JP Cell 1 AWS) (Operational) dbt platform CLI (JP Cell 1 AWS) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 IDE (JP Cell 1 AWS) (Operational) dbt platform CLI (JP Cell 1 AWS) (Operational) Web Application (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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) dbt platform CLI (US AWS) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (US AWS) (Degraded performance) dbt platform CLI (US AWS) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (US AWS) (Operational) Web Application (US AWS) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 dbt platform CLI (US AWS) (Partial outage) Web Application (US AWS) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (US AWS) (Operational) dbt platform CLI (US AWS) (Partial outage) IDE (US AWS) (Partial outage)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components IDE (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) Web Application (US AWS) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 IDE (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) Web Application (US AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 1 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 dbt platform CLI (US Cell 1 AWS) (Degraded performance) Web Application (US Cell 1 AWS) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (US Cell 1 AWS) (Degraded performance) Web Application (US Cell 1 AWS) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (US Cell 1 AWS) (Operational) Web Application (US Cell 1 AWS) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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) (Partial outage) dbt platform CLI (US Cell 1 AWS) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Partial outage) dbt platform CLI (US Cell 1 AWS) (Partial outage)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 IDE (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational) Web Application (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 1 AZURE] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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) dbt platform CLI (US Cell 1 AZURE) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (US Cell 1 AZURE) (Degraded performance) dbt platform CLI (US Cell 1 AZURE) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 1 AZURE) (Operational) dbt platform CLI (US Cell 1 AZURE) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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) (Partial outage) dbt platform CLI (US Cell 1 AZURE) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (US Cell 1 AZURE) (Partial outage) IDE (US Cell 1 AZURE) (Partial outage) Web Application (US Cell 1 AZURE) (Operational)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 1 AZURE) (Operational) dbt platform CLI (US Cell 1 AZURE) (Operational) IDE (US Cell 1 AZURE) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 dbt platform CLI (US Cell 1 AZURE) (Operational) IDE (US Cell 1 AZURE) (Operational) Web Application (US Cell 1 AZURE) (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