All Systems Operational
North America (N. Virginia) ? Operational
90 days ago
99.96 % uptime
Today
Web Application Operational
90 days ago
99.9 % uptime
Today
IDE Operational
90 days ago
99.95 % uptime
Today
Scheduled Jobs Operational
90 days ago
99.95 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Metadata API ? Operational
90 days ago
100.0 % uptime
Today
Metadata Ingestion ? Operational
90 days ago
100.0 % uptime
Today
AWS kms-us-east-1 Operational
AWS s3-us-standard Operational
AWS ec2-us-east-1 Operational
Europe (Frankfurt) ? Operational
90 days ago
99.97 % uptime
Today
Web Application Operational
90 days ago
99.9 % uptime
Today
IDE Operational
90 days ago
99.95 % uptime
Today
Scheduled Jobs Operational
90 days ago
99.98 % uptime
Today
Metadata API ? Operational
90 days ago
100.0 % uptime
Today
Metadata Ingestion ? Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
AWS kms-eu-central-1 Operational
AWS s3-eu-central-1 Operational
AWS ec2-eu-central-1 Operational
External Dependencies Operational
Slack Operational
Slack Messaging Operational
Slack Apps/Integrations/APIs Operational
GitHub Git Operations Operational
GitHub Webhooks Operational
GitHub API Requests Operational
Atlassian Bitbucket Git via HTTPS Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
dbt Cloud CI Maintenance Feb 6, 2023 10:00-12:00 EST
dbt Cloud CI ingestion is undergoing maintenance during this time. We expect CI job runs to operate normally.
Posted on Jan 25, 2023 - 14:55 EST
Past Incidents
Feb 1, 2023

No incidents reported today.

Jan 31, 2023

No incidents reported.

Jan 30, 2023

No incidents reported.

Jan 29, 2023

No incidents reported.

Jan 28, 2023

No incidents reported.

Jan 27, 2023

No incidents reported.

Jan 26, 2023

No incidents reported.

Jan 25, 2023
Resolved - Between 10:00 AM and 10:53 AM Eastern (1500 and 1553 UTC), a 3rd party integration was causing failures in API calls to the US multi-tenant instance of dbt Cloud, leading to the UI becoming unresponsive. We have put measures in place to prevent a recurrence and the dbt Cloud UI responsiveness has returned to normal. There was no impact to scheduled runs during this time.

If you continue to experience errors or unexpected slowness loading the UI, please contact Support via Chat or email support@getdbt.com for further investigation.

Jan 25, 15:04 EST
Monitoring - We have identified an issue with a 3rd party integration that was causing failures in API calls to dbt Cloud, leading to the UI becoming unresponsive, and have taken steps to block traffic from that service until we can work with the service provider to resolve the issue. dbt Cloud UI responsiveness should be returning to normal and we are continuing to monitor.
Jan 25, 11:22 EST
Investigating - We have received reports of the dbt Cloud UI in the US Multitenant instance loading slowly or failing to load with a 502 error. We are actively investigating this issue.
Jan 25, 10:24 EST
Resolved - We have resolved the issue that was preventing branch switching in the IDE.  Users experiencing this issue should see it resolved by reloading the page in their browser.

If you continue to experience this issue after a browser reload, please contact Support via chat or at support@getdbt.com for further investigation.

Jan 25, 12:10 EST
Identified - We have identified an issue preventing the switching of branches in the IDE in the US and EMEA multitenant instances of dbt Cloud and are working on a fix.
Jan 25, 11:51 EST
Jan 24, 2023
Resolved - A small number of runs (

If you have a cancelled run and are not sure if it was related to this issue, please contact Support via chat or email support@getdbt.com with the impacted Run ID.

Jan 24, 18:24 EST
Identified - We have identified an issue in the US Multitenant instance of dbt Cloud that is causing a small set of runs to be cancelled with a 30 minute timeout error message during periods of peak load, generally at :00 and :30 each hour. We have rolled out a fix and are monitoring to ensure its effectiveness.
Jan 24, 16:31 EST
Jan 23, 2023

No incidents reported.

Jan 22, 2023

No incidents reported.

Jan 21, 2023

No incidents reported.

Jan 20, 2023
Resolved - From approximately 9:57AM - 10:27AM Eastern (1457 - 1527 UTC) all scheduled jobs were delayed due to a dbt Cloud issue. As of 11:00 AM Eastern (1600 UTC), all delayed jobs should have successfully started unless manually cancelled and newly scheduled runs are being started on time.

If your jobs continue to be delayed, this may be due to a previous run of the same job still executing or because you have reached your job concurrency limit. Please contact Support via chat or email support@getdbt.com if you continue to experience delays and are unsure of the root cause.

Jan 20, 11:20 EST
Identified - We have implemented a solution to allow the delayed jobs to begin running as of 10:27 AM Eastern (1527 UTC) and are in the process of implementing a fix to prevent this issue from reoccurring.
Jan 20, 10:46 EST
Investigating - We are aware of an issue that has caused all runs that were triggered or scheduled on or after 9:57 AM Eastern (1457 UTC) to be queued and not start on time. These runs are currently delayed and we are working to identify a fix that will allow these runs to start.

We will update this status at approximately 15 minute intervals until we have implemented a solution.

Jan 20, 10:26 EST
Resolved - This incident has been resolved.
Jan 20, 01:20 EST
Update - During the incident, Account Owners or Account Admins that attempted to complete the project setup flow may have inadvertently modified their connection configuration such as the hostname or credentials in an attempt to resolve the issue. These settings, if incorrectly configured, may cause jobs to fail or IDE sessions to fail to launch.

If you see any issues with jobs or IDE sessions failing due to invalid credentials or incorrect hostnames, please double-check that the connection configurations on the project level under Account Settings and at the Environment level under the Deploy menu are correct.

Please reach out to Support via chat or by emailing support@getdbt.com if you need additional assistance.

Jan 19, 03:30 EST
Monitoring - A fix for this issue has rolled out and we are monitoring for any reoccurrence of the issue within a small subset of accounts with still-running jobs that started between 11:04 PM and 12:32 AM Eastern (4:04 and 5:32 UTC).

If you continue to be redirected to the "Complete Project Setup" screen in dbt Cloud please contact Support via chat or email at support@getdbt.com.

Jan 19, 02:30 EST
Update - A fix to the recent change that was incorrectly re-routing parts of the dbt Cloud UI to the Complete Project Setup flow has rolled out. Most accounts should be able to successfully use the dbt Cloud application and IDE.

We working on addressing a small remaining subset of accounts with still-running jobs that launched while the change was live as these jobs can re-introduce the issue.

We will provide a status update on the progress of the rollout at 60 minute intervals until this issue is resolved.

Jan 19, 01:43 EST
Update - A fix to the recent change that was incorrectly re-routing parts of the dbt Cloud UI to the Complete Project Setup flow has rolled out and we have cleaned up IDE sessions that would reintroduce the problem when accessed.

We continue to investigate a recurring issue for a small remaining subset of accounts with jobs that launched while the change was live. We will provide a status update on the progress of the rollout at 15 minute intervals until this issue is resolved.

Jan 19, 01:20 EST
Update - A fix to the recent change that is incorrectly re-routing parts of the dbt Cloud UI to the Complete Project Setup flow has rolled out and we have cleaned up IDE sessions that would reintroduce the problem when accessed.

We are now investigating a recurring issue for a subset of accounts with jobs that launched while the change was live. We will provide a status update on the progress of the rollout at 15 minute intervals until this issue is resolved.

Jan 19, 00:58 EST
Update - A fix to the recent change that is incorrectly re-routing parts of the dbt Cloud UI to the Complete Project Setup flow has rolled out and we are working on cleaning up IDE sessions that may reintroduce the problem when accessed. We will provide a status update on the progress of the rollout at 15 minute intervals until this issue is resolved.
Jan 19, 00:36 EST
Update - A fix to the recent change that is incorrectly re-routing parts of the dbt Cloud UI to the Complete Project Setup flow is in the process of rolling out. We will provide a status update on the progress of the rollout at 15 minute intervals until this issue is resolved.
Jan 19, 00:20 EST
Identified - A recent change is incorrectly re-routing parts of the dbt Cloud UI to the Complete Project Setup flow resulting in an inability to use the dbt Cloud app. Our team is actively working on reverting the changes.
Jan 18, 23:40 EST
Jan 19, 2023
Jan 18, 2023
Resolved - Between 8:28PM and 9:05PM Eastern (1:28AM and 2:05AM UTC) a GitHub incident caused the dbt deps command to repeatedly fail for a small number of scheduled jobs in dbt Cloud. Most jobs were unaffected as the existing retry mechanisms in dbt Cloud successfully mitigated the issue but a small number of jobs (

If a job during this time failed in the dbt deps step, please try re-executing the job and reach out to Support via chat or at support@getdbt.com if you are unsure whether your job's failure was due to this incident.

Jan 18, 21:43 EST
Investigating - There is an active GitHub incident that is impacting scheduled jobs and is causing failures in the dbt deps step of the job. This issue may also impact the use of the dbt deps command in the IDE.

We are monitoring this incident (which is also being tracked at githubstatus.com) and will update this status page once we observe jobs are no longer affected.

Jan 18, 21:05 EST