dbt Cloud Outage History

Started Mar 17, 2026, 12:45 AM UTC· resolved Mar 17, 2026, 04:27 AM UTC

1. investigating Mar 17, 2026, 12:45 AM UTC

   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.

2. identified Mar 17, 2026, 12:46 AM UTC

   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.

3. monitoring Mar 17, 2026, 01:37 AM UTC

   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].

4. resolved Mar 17, 2026, 04:27 AM UTC

   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].

Read the full incident report →

Started Mar 17, 2026, 12:45 AM UTC· resolved Mar 17, 2026, 04:27 AM UTC

1. investigating Mar 17, 2026, 12:45 AM UTC

   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.

2. identified Mar 17, 2026, 12:46 AM UTC

   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.

3. monitoring Mar 17, 2026, 01:37 AM UTC

   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].

4. resolved Mar 17, 2026, 04:27 AM UTC

   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].

Read the full incident report →

Started Mar 17, 2026, 12:45 AM UTC· resolved Mar 17, 2026, 04:27 AM UTC

1. investigating Mar 17, 2026, 12:45 AM UTC

   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.

2. identified Mar 17, 2026, 12:46 AM UTC

   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.

3. monitoring Mar 17, 2026, 01:37 AM UTC

   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].

4. resolved Mar 17, 2026, 04:27 AM UTC

   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].

Read the full incident report →

Started Mar 17, 2026, 12:45 AM UTC· resolved Mar 17, 2026, 04:27 AM UTC

1. investigating Mar 17, 2026, 12:45 AM UTC

   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.

2. identified Mar 17, 2026, 12:46 AM UTC

   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.

3. monitoring Mar 17, 2026, 01:37 AM UTC

   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].

4. resolved Mar 17, 2026, 04:27 AM UTC

   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].

Read the full incident report →

Started Mar 17, 2026, 12:45 AM UTC· resolved Mar 17, 2026, 04:27 AM UTC

1. investigating Mar 17, 2026, 12:45 AM UTC

   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.

2. identified Mar 17, 2026, 12:46 AM UTC

   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.

3. monitoring Mar 17, 2026, 01:37 AM UTC

   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].

4. resolved Mar 17, 2026, 04:27 AM UTC

   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].

Read the full incident report →

Started Mar 17, 2026, 12:45 AM UTC· resolved Mar 17, 2026, 04:27 AM UTC

1. investigating Mar 17, 2026, 12:45 AM UTC

   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.

2. identified Mar 17, 2026, 12:46 AM UTC

   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.

3. monitoring Mar 17, 2026, 01:37 AM UTC

   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].

4. resolved Mar 17, 2026, 04:27 AM UTC

   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].

Read the full incident report →

Started Mar 17, 2026, 12:45 AM UTC· resolved Mar 17, 2026, 04:27 AM UTC

1. investigating Mar 17, 2026, 12:45 AM UTC

   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.

2. identified Mar 17, 2026, 12:46 AM UTC

   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.

3. monitoring Mar 17, 2026, 01:37 AM UTC

   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].

4. resolved Mar 17, 2026, 04:27 AM UTC

   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].

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 13, 2026, 12:03 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 11:14 PM UTC· resolved Mar 17, 2026, 02:28 AM UTC

1. investigating Mar 12, 2026, 11:14 PM UTC

   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

   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.

3. resolved Mar 13, 2026, 12:03 AM UTC

   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.

4. identified Mar 13, 2026, 05:05 PM UTC

   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.

5. identified Mar 13, 2026, 05:48 PM UTC

   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.

6. identified Mar 13, 2026, 08:02 PM UTC

   A release for the fix to Fusion is currently underway. We will update once the release is completed.

7. monitoring Mar 13, 2026, 10:19 PM UTC

   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.

8. resolved Mar 17, 2026, 02:28 AM UTC

   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.

Read the full incident report →

Started Mar 11, 2026, 03:59 PM UTC· resolved Mar 11, 2026, 09:16 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 11, 2026, 03:44 PM UTC· resolved Mar 11, 2026, 09:16 PM UTC

1. investigating Mar 11, 2026, 03:44 PM UTC

   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.

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

   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.

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

   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.

4. resolved Mar 11, 2026, 09:16 PM UTC

   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.

Read the full incident report →

Started Mar 09, 2026, 01:36 PM UTC· resolved Mar 09, 2026, 01:40 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 09, 2026, 12:11 PM UTC· resolved Mar 09, 2026, 03:10 PM UTC

1. investigating Mar 09, 2026, 12:11 PM UTC

   • 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

   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.

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

   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.

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

   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].

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

   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.

Read the full incident report →