dbt Cloud Outage History
dbt Cloud is up right nowPingoru has recorded 767 incidents for dbt Cloud: 767 in the last 12 months and 210 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 82 | 70 of 720 (10%) |
| May 2026 | 126 | 155 of 744 (21%) |
| June 2026 | 55 | 40 of 720 (6%) |
| July 2026 | 81 | 29 of 744 (4%) |
| August 2026 | 78 | 22 of 744 (3%) |
| September 2026 | 77 | 53 of 720 (7%) |
| October 2026 | 44 | 69 of 593 (12%) |
Incidents, newest first
Minor May 6, 2026 [EMEA Cell 1 AZURE] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [EU Cell 1 GCP] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [EU4 Cell 1 GCP] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [JP Cell 1 AWS] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [US AWS] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [US Cell 1 AWS] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [US Cell 1 AZURE] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [US Cell 1 GCP] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [US Cell 2 AWS] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [US Cell 3 AWS] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor May 6, 2026 [US Cell 4 AWS] target.user resolving to None in development environments 10h
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 02:40 AM UTC
- investigating May 06, 2026, 04:40 PM UTC
We're investigating an issue with Snowflake SSO profile generation that is causing target.user to resolve to "None" in development environments. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 06, 2026, 11:10 PM UTC
We have identified an issue with Snowflake SSO profile generation that resulted in target.user resolving to "None" in development environments. A fix is being implemented, and we will provide an update shortly.
- identified May 07, 2026, 12:16 AM UTC
We are continuing the implementation of a fix to address the reported issue. We will provide an update as soon as the fix is deployed. Thank you for your patience.
- monitoring May 07, 2026, 01:38 AM UTC
We have deployed a fix for the reported issue. dbt Studio has returned to its normal state and we are continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 07, 2026, 02:40 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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. We thank you for your patience and understanding.
Minor April 30, 2026 [US AWS] jobs failing on dbt deps due to private packages 4h 42m
Started Apr 30, 2026, 08:18 PM UTC· resolved May 01, 2026, 01:00 AM UTC
- identified Apr 30, 2026, 08:18 PM UTC
We have identified an issue with private packages that resulted in jobs failing on the dbt deps step. A fix is being implemented, and we will provide an update shortly.
- resolved May 01, 2026, 01:00 AM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 01:00 UTC. Between 20:18 UTC and 01:00 UTC an issue with private packages resulted in dbt deps failures in job runs. We have put measures in place to prevent a recurrence and scheduled jobs 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.
Minor April 23, 2026 FlightSQL authentication error on Semantic Layer failing with working service token 4m
Started Apr 23, 2026, 11:59 PM UTC· resolved Apr 24, 2026, 12:04 AM UTC
No vendor updates were posted for this incident.
Minor April 23, 2026 [US Cell 1 AWS] FlightSQL authentication error on Semantic Layer failing with working service token 4m
Started Apr 23, 2026, 11:59 PM UTC· resolved Apr 24, 2026, 12:04 AM UTC
- monitoring Apr 23, 2026, 11:59 PM UTC
We have deployed a fix for the Semantic Layer that was causing service token authentication failures. The Semantic Layer has returned to its normal state and we are continuing to monitor.
- resolved Apr 24, 2026, 12:04 AM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 12:31 PM Eastern. Between 10:42 AM Eastern and 12:24 PM Eastern an issue with the Semantic Layer resulted in service token authentication failures . We have put measures in place to prevent a recurrence and the Semantic Layer 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.
Minor April 23, 2026 Small percentage of 429 errors impacting very few users 49m
Started Apr 23, 2026, 04:38 PM UTC· resolved Apr 23, 2026, 05:28 PM UTC
No vendor updates were posted for this incident.
Minor April 22, 2026 Login Authentication code exchange failures 1h 33m
Started Apr 22, 2026, 07:19 PM UTC· resolved Apr 22, 2026, 08:53 PM UTC
No vendor updates were posted for this incident.
Minor April 22, 2026 [APAC AWS] Login Authentication code exchange failures 1h 33m
Started Apr 22, 2026, 07:19 PM UTC· resolved Apr 22, 2026, 08:53 PM UTC
- investigating Apr 22, 2026, 07:19 PM UTC
We're investigating an issue with Authentication that is causing Logins to fail. This is impacting dbt Platform in EMEA and AU region between 18:35pm and 18:55pm UTC. The team is investigating.
- monitoring Apr 22, 2026, 07:25 PM UTC
The suspected cause for the underlying issue is an outage with an upstream dependent system. A sharp decline in error rates and increasing login successes, indicating recovery is underway. Operational status has been confirmed with manual checks and successful logs, users are now able to log in again on the affected tenants. We are continuing to monitor this issue.
- resolved Apr 22, 2026, 08:53 PM UTC
The issue has been resolved, and all affected systems are now functioning normally.
Minor April 22, 2026 [EMEA AWS] Login Authentication code exchange failures 1h 33m
Started Apr 22, 2026, 07:19 PM UTC· resolved Apr 22, 2026, 08:53 PM UTC
- investigating Apr 22, 2026, 07:19 PM UTC
We're investigating an issue with Authentication that is causing Logins to fail. This is impacting dbt Platform in EMEA and AU region between 18:35pm and 18:55pm UTC. The team is investigating.
- monitoring Apr 22, 2026, 07:25 PM UTC
The suspected cause for the underlying issue is an outage with an upstream dependent system. A sharp decline in error rates and increasing login successes, indicating recovery is underway. Operational status has been confirmed with manual checks and successful logs, users are now able to log in again on the affected tenants. We are continuing to monitor this issue.
- resolved Apr 22, 2026, 08:53 PM UTC
The issue has been resolved, and all affected systems are now functioning normally.
Minor April 20, 2026 [EMEA AWS] deps failures due to private packages in dbt Platform 2h 28m
Started Apr 20, 2026, 10:24 PM UTC· resolved Apr 21, 2026, 12:52 AM UTC
- investigating Apr 20, 2026, 10:24 PM UTC
We're investigating an issue with scheduled jobs and the studio IDE that is causing deps failures for some customers using private packages. This is impacting job runs and studio IDE sessions anytime after 3:20 PM Eastern. 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.
- identified Apr 20, 2026, 10:37 PM UTC
We have identified an issue with private packages that resulted in deps failures in scheduled jobs and the studio ide for some customers. A fix is being implemented, and we will provide an update shortly.
- identified Apr 20, 2026, 11:52 PM UTC
We have identified an issue impacting a subset of customers using private packages with Azure DevOps, resulting in deps failures in scheduled jobs and the Studio IDE. We are continuing to deploy a fix and will provide further updates as they become available.
- monitoring Apr 21, 2026, 12:23 AM UTC
We have deployed a fix for the private packages dependency resolution in dbt Cloud that was causing deps failures in scheduled jobs and the Studio IDE for a subset of customers using Azure DevOps. The affected systems have returned to their normal state and we are continuing to monitor.
- resolved Apr 21, 2026, 12:52 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. An issue with private package dependency resolution in dbt Cloud resulted in dbt deps failures in scheduled jobs and the Studio IDE for customers using Azure DevOps. We have put measures in place to prevent a recurrence and the affected systems have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.
Minor April 20, 2026 [EU4 Cell 1 GCP] deps failures due to private packages in dbt Platform 2h 28m
Started Apr 20, 2026, 10:24 PM UTC· resolved Apr 21, 2026, 12:52 AM UTC
- investigating Apr 20, 2026, 10:24 PM UTC
We're investigating an issue with scheduled jobs and the studio IDE that is causing deps failures for some customers using private packages. This is impacting job runs and studio IDE sessions anytime after 3:20 PM Eastern. 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.
- identified Apr 20, 2026, 10:37 PM UTC
We have identified an issue with private packages that resulted in deps failures in scheduled jobs and the studio ide for some customers. A fix is being implemented, and we will provide an update shortly.
- identified Apr 20, 2026, 11:52 PM UTC
We have identified an issue impacting a subset of customers using private packages with Azure DevOps, resulting in deps failures in scheduled jobs and the Studio IDE. We are continuing to deploy a fix and will provide further updates as they become available.
- monitoring Apr 21, 2026, 12:23 AM UTC
We have deployed a fix for the private packages dependency resolution in dbt Cloud that was causing deps failures in scheduled jobs and the Studio IDE for a subset of customers using Azure DevOps. The affected systems have returned to their normal state and we are continuing to monitor.
- resolved Apr 21, 2026, 12:52 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. An issue with private package dependency resolution in dbt Cloud resulted in dbt deps failures in scheduled jobs and the Studio IDE for customers using Azure DevOps. We have put measures in place to prevent a recurrence and the affected systems have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.
Minor April 20, 2026 [US AWS] deps failures due to private packages in dbt Platform 2h 28m
Started Apr 20, 2026, 10:24 PM UTC· resolved Apr 21, 2026, 12:52 AM UTC
- investigating Apr 20, 2026, 10:24 PM UTC
We're investigating an issue with scheduled jobs and the studio IDE that is causing deps failures for some customers using private packages. This is impacting job runs and studio IDE sessions anytime after 3:20 PM Eastern. 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.
- identified Apr 20, 2026, 10:37 PM UTC
We have identified an issue with private packages that resulted in deps failures in scheduled jobs and the studio ide for some customers. A fix is being implemented, and we will provide an update shortly.
- identified Apr 20, 2026, 11:52 PM UTC
We have identified an issue impacting a subset of customers using private packages with Azure DevOps, resulting in deps failures in scheduled jobs and the Studio IDE. We are continuing to deploy a fix and will provide further updates as they become available.
- monitoring Apr 21, 2026, 12:23 AM UTC
We have deployed a fix for the private packages dependency resolution in dbt Cloud that was causing deps failures in scheduled jobs and the Studio IDE for a subset of customers using Azure DevOps. The affected systems have returned to their normal state and we are continuing to monitor.
- resolved Apr 21, 2026, 12:52 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. An issue with private package dependency resolution in dbt Cloud resulted in dbt deps failures in scheduled jobs and the Studio IDE for customers using Azure DevOps. We have put measures in place to prevent a recurrence and the affected systems have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.
Minor April 20, 2026 [US Cell 1 AZURE] deps failures due to private packages in dbt Platform 2h 28m
Started Apr 20, 2026, 10:24 PM UTC· resolved Apr 21, 2026, 12:52 AM UTC
- investigating Apr 20, 2026, 10:24 PM UTC
We're investigating an issue with scheduled jobs and the studio IDE that is causing deps failures for some customers using private packages. This is impacting job runs and studio IDE sessions anytime after 3:20 PM Eastern. 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.
- identified Apr 20, 2026, 10:37 PM UTC
We have identified an issue with private packages that resulted in deps failures in scheduled jobs and the studio ide for some customers. A fix is being implemented, and we will provide an update shortly.
- identified Apr 20, 2026, 11:52 PM UTC
We have identified an issue impacting a subset of customers using private packages with Azure DevOps, resulting in deps failures in scheduled jobs and the Studio IDE. We are continuing to deploy a fix and will provide further updates as they become available.
- monitoring Apr 21, 2026, 12:23 AM UTC
We have deployed a fix for the private packages dependency resolution in dbt Cloud that was causing deps failures in scheduled jobs and the Studio IDE for a subset of customers using Azure DevOps. The affected systems have returned to their normal state and we are continuing to monitor.
- resolved Apr 21, 2026, 12:52 AM UTC
The issue has been resolved, and all affected systems are now functioning normally. An issue with private package dependency resolution in dbt Cloud resulted in dbt deps failures in scheduled jobs and the Studio IDE for customers using Azure DevOps. We have put measures in place to prevent a recurrence and the affected systems have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.
Major April 20, 2026 deps failures due to private packages in dbt Platform 2h 28m
Started Apr 20, 2026, 10:24 PM UTC· resolved Apr 21, 2026, 12:52 AM UTC
No vendor updates were posted for this incident.
Minor April 18, 2026 Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
No vendor updates were posted for this incident.
Minor April 18, 2026 [APAC AWS] Job Run logs unavailable 3h 54m
Started Apr 18, 2026, 02:01 PM UTC· resolved Apr 18, 2026, 05:56 PM UTC
- investigating Apr 18, 2026, 02:01 PM UTC
We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified Apr 18, 2026, 02:13 PM UTC
We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly.
- identified Apr 18, 2026, 03:28 PM UTC
We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly.
- resolved Apr 18, 2026, 05:56 PM UTC
The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. 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.