dbt Cloud Outage History

dbt Cloud is up right now

There were 292 dbt Cloud outages since February 4, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor February 9, 2026

[APAC AWS] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components IDE (APAC AWS) (Partial outage) Scheduled Jobs (APAC AWS) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components Scheduled Jobs (APAC AWS) (Partial outage) IDE (APAC AWS) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components IDE (APAC AWS) (Partial outage) Scheduled Jobs (APAC AWS) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components IDE (APAC AWS) (Operational) Scheduled Jobs (APAC AWS) (Operational)

Read the full incident report →

Minor February 9, 2026

[EMEA AWS] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components Scheduled Jobs (EMEA AWS) (Partial outage) IDE (EMEA AWS) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components IDE (EMEA AWS) (Partial outage) Scheduled Jobs (EMEA AWS) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components IDE (EMEA AWS) (Partial outage) Scheduled Jobs (EMEA AWS) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components IDE (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational)

Read the full incident report →

Minor February 9, 2026

[EMEA Cell 1 AZURE] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components IDE (EMEA Cell 1 AZURE) (Partial outage) Scheduled Jobs (EMEA Cell 1 AZURE) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Partial outage) IDE (EMEA Cell 1 AZURE) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components IDE (EMEA Cell 1 AZURE) (Partial outage) Scheduled Jobs (EMEA Cell 1 AZURE) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components IDE (EMEA Cell 1 AZURE) (Operational) Scheduled Jobs (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor February 9, 2026

[EU Cell 1 GCP] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components Scheduled Jobs (EU Cell 1 GCP) (Partial outage) IDE (EU Cell 1 GCP) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components IDE (EU Cell 1 GCP) (Partial outage) Scheduled Jobs (EU Cell 1 GCP) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components IDE (EU Cell 1 GCP) (Partial outage) Scheduled Jobs (EU Cell 1 GCP) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components IDE (EU Cell 1 GCP) (Operational) Scheduled Jobs (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 9, 2026

[EU4 Cell 1 GCP] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components IDE (EU4 Cell 1 GCP) (Partial outage) Scheduled Jobs (EU4 Cell 1 GCP) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components IDE (EU4 Cell 1 GCP) (Partial outage) Scheduled Jobs (EU4 Cell 1 GCP) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components IDE (EU4 Cell 1 GCP) (Partial outage) Scheduled Jobs (EU4 Cell 1 GCP) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Operational) IDE (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 9, 2026

[JP Cell 1 AWS] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components Scheduled Jobs (JP Cell 1 AWS) (Partial outage) IDE (JP Cell 1 AWS) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components Scheduled Jobs (JP Cell 1 AWS) (Partial outage) IDE (JP Cell 1 AWS) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components Scheduled Jobs (JP Cell 1 AWS) (Partial outage) IDE (JP Cell 1 AWS) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components IDE (JP Cell 1 AWS) (Operational) Scheduled Jobs (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 9, 2026

[US AWS] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components IDE (US AWS) (Partial outage) Scheduled Jobs (US AWS) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components IDE (US AWS) (Partial outage) Scheduled Jobs (US AWS) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components IDE (US AWS) (Partial outage) Scheduled Jobs (US AWS) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components Scheduled Jobs (US AWS) (Operational) IDE (US AWS) (Operational)

Read the full incident report →

Minor February 9, 2026

[US Cell 1 AWS] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components Scheduled Jobs (US Cell 1 AWS) (Partial outage) IDE (US Cell 1 AWS) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components Scheduled Jobs (US Cell 1 AWS) (Partial outage) IDE (US Cell 1 AWS) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components Scheduled Jobs (US Cell 1 AWS) (Partial outage) IDE (US Cell 1 AWS) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components IDE (US Cell 1 AWS) (Operational) Scheduled Jobs (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 9, 2026

[US Cell 1 AZURE] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components Scheduled Jobs (US Cell 1 AZURE) (Partial outage) IDE (US Cell 1 AZURE) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components IDE (US Cell 1 AZURE) (Partial outage) Scheduled Jobs (US Cell 1 AZURE) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components Scheduled Jobs (US Cell 1 AZURE) (Partial outage) IDE (US Cell 1 AZURE) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components IDE (US Cell 1 AZURE) (Operational) Scheduled Jobs (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor February 9, 2026

[US Cell 1 GCP] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components IDE (US Cell 1 GCP) (Partial outage) Scheduled Jobs (US Cell 1 GCP) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components Scheduled Jobs (US Cell 1 GCP) (Partial outage) IDE (US Cell 1 GCP) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components Scheduled Jobs (US Cell 1 GCP) (Partial outage) IDE (US Cell 1 GCP) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components Scheduled Jobs (US Cell 1 GCP) (Operational) IDE (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 9, 2026

[US Cell 2 AWS] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components Scheduled Jobs (US Cell 2 AWS) (Partial outage) IDE (US Cell 2 AWS) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components IDE (US Cell 2 AWS) (Partial outage) Scheduled Jobs (US Cell 2 AWS) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components IDE (US Cell 2 AWS) (Partial outage) Scheduled Jobs (US Cell 2 AWS) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational) IDE (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 9, 2026

[US Cell 3 AWS] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components IDE (US Cell 3 AWS) (Partial outage) Scheduled Jobs (US Cell 3 AWS) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components IDE (US Cell 3 AWS) (Partial outage) Scheduled Jobs (US Cell 3 AWS) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components IDE (US Cell 3 AWS) (Partial outage) Scheduled Jobs (US Cell 3 AWS) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components IDE (US Cell 3 AWS) (Operational) Scheduled Jobs (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor February 9, 2026

[US Cell 4 AWS] dbt deps failures in job runs and dbt Studio

Detected by Pingoru
Feb 09, 2026, 08:09 PM UTC
Resolved
Feb 09, 2026, 08:09 PM UTC
Duration
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:01 PM UTC

    Status: Investigating 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/ Affected components IDE (US Cell 4 AWS) (Partial outage) Scheduled Jobs (US Cell 4 AWS) (Partial outage)

  2. identified Feb 09, 2026, 07:03 PM UTC

    Status: Identified 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. Affected components Scheduled Jobs (US Cell 4 AWS) (Partial outage) IDE (US Cell 4 AWS) (Partial outage)

  3. monitoring Feb 09, 2026, 07:42 PM UTC

    Status: Monitoring 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. Affected components Scheduled Jobs (US Cell 4 AWS) (Partial outage) IDE (US Cell 4 AWS) (Partial outage)

  4. resolved Feb 09, 2026, 08:09 PM UTC

    Status: Resolved 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. Affected components IDE (US Cell 4 AWS) (Operational) Scheduled Jobs (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor February 4, 2026

[US Cell 1 AWS] Runs delayed and CLI Invocations are timing-out

Detected by Pingoru
Feb 04, 2026, 01:25 PM UTC
Resolved
Feb 04, 2026, 01:25 PM UTC
Duration
Timeline · 3 updates
  1. investigating Feb 04, 2026, 10:55 AM UTC

    Status: Investigating 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. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance) IDE (US Cell 1 AWS) (Degraded performance) dbt platform CLI (US Cell 1 AWS) (Degraded performance)

  2. monitoring Feb 04, 2026, 12:55 PM UTC

    Status: Monitoring Studio and Cloud CLI performance has returned to normal and we are continuing to closely monitor the situation. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance) dbt platform CLI (US Cell 1 AWS) (Degraded performance) IDE (US Cell 1 AWS) (Degraded performance)

  3. resolved Feb 04, 2026, 01:25 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components IDE (US Cell 1 AWS) (Operational) Scheduled Jobs (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 4, 2026

[US Cell 2 AWS] Runs delayed and CLI Invocations are timing-out

Detected by Pingoru
Feb 04, 2026, 01:25 PM UTC
Resolved
Feb 04, 2026, 01:25 PM UTC
Duration
Timeline · 3 updates
  1. investigating Feb 04, 2026, 10:55 AM UTC

    Status: Investigating 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. Affected components dbt platform CLI (US Cell 2 AWS) (Degraded performance) IDE (US Cell 2 AWS) (Degraded performance) Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

  2. monitoring Feb 04, 2026, 12:55 PM UTC

    Status: Monitoring Studio and Cloud CLI performance has returned to normal and we are continuing to closely monitor the situation. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance) dbt platform CLI (US Cell 2 AWS) (Degraded performance) IDE (US Cell 2 AWS) (Degraded performance)

  3. resolved Feb 04, 2026, 01:25 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components IDE (US Cell 2 AWS) (Operational) Scheduled Jobs (US Cell 2 AWS) (Operational) dbt platform CLI (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 4, 2026

[US Cell 3 AWS] Runs delayed and CLI Invocations are timing-out

Detected by Pingoru
Feb 04, 2026, 01:25 PM UTC
Resolved
Feb 04, 2026, 01:25 PM UTC
Duration
Timeline · 3 updates
  1. investigating Feb 04, 2026, 10:55 AM UTC

    Status: Investigating 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. Affected components dbt platform CLI (US Cell 3 AWS) (Degraded performance) IDE (US Cell 3 AWS) (Degraded performance) Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

  2. monitoring Feb 04, 2026, 12:55 PM UTC

    Status: Monitoring Studio and Cloud CLI performance has returned to normal and we are continuing to closely monitor the situation. Affected components IDE (US Cell 3 AWS) (Degraded performance) dbt platform CLI (US Cell 3 AWS) (Degraded performance) Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

  3. resolved Feb 04, 2026, 01:25 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components IDE (US Cell 3 AWS) (Operational) Scheduled Jobs (US Cell 3 AWS) (Operational) dbt platform CLI (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor February 4, 2026

[US Cell 4 AWS] Runs delayed and CLI Invocations are timing-out

Detected by Pingoru
Feb 04, 2026, 01:25 PM UTC
Resolved
Feb 04, 2026, 01:25 PM UTC
Duration
Timeline · 3 updates
  1. investigating Feb 04, 2026, 10:55 AM UTC

    Status: Investigating 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. Affected components IDE (US Cell 4 AWS) (Degraded performance) dbt platform CLI (US Cell 4 AWS) (Degraded performance) Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

  2. monitoring Feb 04, 2026, 12:55 PM UTC

    Status: Monitoring Studio and Cloud CLI performance has returned to normal and we are continuing to closely monitor the situation. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance) dbt platform CLI (US Cell 4 AWS) (Degraded performance) IDE (US Cell 4 AWS) (Degraded performance)

  3. resolved Feb 04, 2026, 01:25 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components IDE (US Cell 4 AWS) (Operational) dbt platform CLI (US Cell 4 AWS) (Operational) Scheduled Jobs (US Cell 4 AWS) (Operational)

Read the full incident report →

Looking to track dbt Cloud downtime and outages?

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

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

5 free monitors · No credit card required