dbt Cloud Outage History
dbt Cloud is up right nowPingoru has recorded 767 incidents for dbt Cloud: 767 in the last 12 months and 201 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 597 (11%) |
Incidents, newest first
Minor February 17, 2026 [US Cell 2 AWS] Intermittent Job Failures –
Started Feb 17, 2026, 10:14 PM UTC· resolved Feb 17, 2026, 10:14 PM UTC
- resolved Feb 17, 2026, 10:14 PM UTC
Starting at approximately 2:14 PM PST, some customers may have experienced job failures with the error message “Unexpected acquire failure.” Affected jobs may have failed to start or stalled during execution. The underlying issue has been identified and resolved. Systems are now operating normally, and jobs should now run successfully.
Minor February 16, 2026 [APAC AWS] Outbound Webhooks missing dispatches –
Started Feb 16, 2026, 11:01 AM UTC· resolved Feb 16, 2026, 11:01 AM UTC
- resolved Feb 16, 2026, 11:01 AM UTC
Between Feb 16 12:01 UTC and Feb 17 9:56 UTC we experienced an issue with outbound webhooks not being dispatched for some accounts due to an unexpected issue with one of the underlying mechanisms. This issue has since been identified and resolved. We apologise for any inconveniences this may have caused. Please contacts us at [email protected] with any questions or concerns.
Minor February 14, 2026 [US AWS] Small number of scheduled run are cancelled 23m
Started Feb 14, 2026, 05:19 PM UTC· resolved Feb 14, 2026, 05:43 PM UTC
- investigating Feb 14, 2026, 05:19 PM UTC
We're identified an issue with Scheduler pickup that is causing very small number of runs to be cancelled. This is impacting scheduled runs in US Multi tenant region between 16:30 to 16:35 UTC. The impact is minimal and only effected a few runs and the issue seems to be resolved and we are monitoring. The Impacted cancelled run need to be retried as a workaround. Please reach out to [email protected] "[email protected]": mailto:[email protected] for any further queries or clarifications.
- monitoring Feb 14, 2026, 05:23 PM UTC
The issue impacting scheduled runs in the US multi-tenant region between 16:30 and 16:35 UTC is now resolved. The runs have returned to normal, and we are continuing to monitor. The Impacted cancelled run Affected components Scheduled Jobs (US AWS) (Degraded performance)
- resolved Feb 14, 2026, 05:43 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 16:35 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.
Minor February 12, 2026 [APAC AWS] dbt Copilot SQL generation failures across all regions 3h 15m
Started Feb 12, 2026, 03:00 PM UTC· resolved Feb 12, 2026, 06:15 PM UTC
- identified Feb 12, 2026, 03:00 PM UTC
We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/
- monitoring Feb 12, 2026, 05:52 PM UTC
We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable.
- resolved Feb 12, 2026, 06:15 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.
Minor February 12, 2026 [EMEA AWS] dbt Copilot SQL generation failures across all regions 3h 15m
Started Feb 12, 2026, 03:00 PM UTC· resolved Feb 12, 2026, 06:15 PM UTC
- identified Feb 12, 2026, 03:00 PM UTC
We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/
- monitoring Feb 12, 2026, 05:52 PM UTC
We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable.
- resolved Feb 12, 2026, 06:15 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.
Minor February 12, 2026 [EMEA Cell 1 AZURE] dbt Copilot SQL generation failures across all regions 3h 15m
Started Feb 12, 2026, 03:00 PM UTC· resolved Feb 12, 2026, 06:15 PM UTC
- identified Feb 12, 2026, 03:00 PM UTC
We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/
- monitoring Feb 12, 2026, 05:52 PM UTC
We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable.
- resolved Feb 12, 2026, 06:15 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.
Minor February 12, 2026 [US AWS] dbt Copilot SQL generation failures across all regions 3h 15m
Started Feb 12, 2026, 03:00 PM UTC· resolved Feb 12, 2026, 06:15 PM UTC
- identified Feb 12, 2026, 03:00 PM UTC
We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/
- monitoring Feb 12, 2026, 05:52 PM UTC
We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable.
- resolved Feb 12, 2026, 06:15 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.
Minor February 12, 2026 [US Cell 1 AWS] dbt Copilot SQL generation failures across all regions 3h 15m
Started Feb 12, 2026, 03:00 PM UTC· resolved Feb 12, 2026, 06:15 PM UTC
- identified Feb 12, 2026, 03:00 PM UTC
We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/
- monitoring Feb 12, 2026, 05:52 PM UTC
We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable.
- resolved Feb 12, 2026, 06:15 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.
Minor February 12, 2026 [US Cell 1 AZURE] dbt Copilot SQL generation failures across all regions 3h 15m
Started Feb 12, 2026, 03:00 PM UTC· resolved Feb 12, 2026, 06:15 PM UTC
- identified Feb 12, 2026, 03:00 PM UTC
We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/
- monitoring Feb 12, 2026, 05:52 PM UTC
We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable.
- resolved Feb 12, 2026, 06:15 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.
Minor February 12, 2026 [US Cell 2 AWS] dbt Copilot SQL generation failures across all regions 3h 15m
Started Feb 12, 2026, 03:00 PM UTC· resolved Feb 12, 2026, 06:15 PM UTC
- identified Feb 12, 2026, 03:00 PM UTC
We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/
- monitoring Feb 12, 2026, 05:52 PM UTC
We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable.
- resolved Feb 12, 2026, 06:15 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.
Minor February 12, 2026 [US Cell 3 AWS] dbt Copilot SQL generation failures across all regions 3h 15m
Started Feb 12, 2026, 03:00 PM UTC· resolved Feb 12, 2026, 06:15 PM UTC
- identified Feb 12, 2026, 03:00 PM UTC
We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/
- monitoring Feb 12, 2026, 05:52 PM UTC
We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable.
- resolved Feb 12, 2026, 06:15 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.
Minor February 9, 2026 [APAC AWS] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [EMEA AWS] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [EMEA Cell 1 AZURE] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [EU Cell 1 GCP] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [EU4 Cell 1 GCP] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [JP Cell 1 AWS] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [US AWS] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [US Cell 1 AWS] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [US Cell 1 AZURE] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [US Cell 1 GCP] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [US Cell 2 AWS] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [US Cell 3 AWS] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 9, 2026 [US Cell 4 AWS] dbt deps failures in job runs and dbt Studio 1h 8m
Started Feb 09, 2026, 07:01 PM UTC· resolved Feb 09, 2026, 08:09 PM UTC
- investigating Feb 09, 2026, 07:01 PM UTC
We're investigating dbt deps failures impacting scheduled jobs and dbt Studio due to an ongoing Github incident. This is impacting job runs and Studio sessions anytime after 19:01 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Github status page: https://www.githubstatus.com/
- identified Feb 09, 2026, 07:03 PM UTC
We have identified an issue with an ongoing Github incident that resulted in failures in job runs and Studio sessions. We will provide an update shortly.
- monitoring Feb 09, 2026, 07:42 PM UTC
The GitHub incident that was resulting in dbt deps failures has been resolved. Scheduled Jobs and the Studio IDE have returned to a normal state and we are continuing to monitor.
- resolved Feb 09, 2026, 08:09 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. We have put measures in place to prevent a recurrence and git operations 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.
Minor February 4, 2026 [US Cell 1 AWS] Runs delayed and CLI Invocations are timing-out 2h 30m
Started Feb 04, 2026, 10:55 AM UTC· resolved Feb 04, 2026, 01:25 PM UTC
- investigating Feb 04, 2026, 10:55 AM UTC
We're investigating an issue with some delays starting runs and intermittent failures in Studio and the Cloud CLI between 10:55 am - 12:55 pm UTC. 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.
- monitoring Feb 04, 2026, 12:55 PM UTC
Studio and Cloud CLI performance has returned to normal and we are continuing to closely monitor the situation.
- resolved Feb 04, 2026, 01:25 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.