All Systems Operational
Web Application (cloud.getdbt.com) Operational
90 days ago
99.96 % uptime
Today
API Operational
90 days ago
99.97 % uptime
Today
Scheduled Jobs Operational
90 days ago
100.0 % uptime
Today
Metadata 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
External Dependencies Operational
Slack Operational
Slack Messaging Operational
Slack Apps/Integrations/APIs Operational
AWS kms-us-east-1 Operational
AWS s3-us-standard Operational
GitHub Git Operations Operational
GitHub Webhooks Operational
GitHub API Requests Operational
Atlassian Bitbucket Git via HTTPS Operational
IDE Operational
90 days ago
99.97 % uptime
Today
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.
Past Incidents
May 27, 2022

No incidents reported today.

May 26, 2022

No incidents reported.

May 25, 2022

No incidents reported.

May 24, 2022

No incidents reported.

May 23, 2022

No incidents reported.

May 22, 2022

No incidents reported.

May 21, 2022

No incidents reported.

May 20, 2022

No incidents reported.

May 19, 2022

No incidents reported.

May 18, 2022

No incidents reported.

May 17, 2022
Resolved - Starting at 2:50PM Eastern (18:50 UTC) on Monday, May 16, IDE sessions and Scheduled Jobs for GitHub app-integrated projects running dbt 0.19.2 or earlier experienced failures with a "Failed to generate an access token" error while cloning the git repository.

We shipped a fix to Scheduled Jobs which prevented the issue for all runs after 11:08AM Eastern (15:08 UTC) on Tuesday, May 17 and a subsequent fix for IDE sessions which took effect for all sessions launched after 5:45PM Eastern (21:45 UTC). Projects running dbt 0.19.2 or earlier are once again running as expected.

May 17, 21:47 EDT
Update - We have identified an additional issue that was causing IDE sessions on dbt 0.19.2 and earlier to fail with this message. We are rolling out another fix and are continuing to monitor.
May 17, 18:07 EDT
Monitoring - We have rolled back a recent change that we believe was causing this issue. As of 11:08AM Eastern no additional scheduled runs have been affected and we are continuing to monitor.
May 17, 12:07 EDT
Investigating - We are investigating an issue with intermittent failures to clone with a "Failed to generate an access token!" error on Scheduled Jobs and IDE sessions using version 0.19.2 and earlier of dbt.
May 17, 10:46 EDT
May 16, 2022

No incidents reported.

May 15, 2022
Completed - The scheduled maintenance has been completed.
May 15, 14:00 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 15, 12:01 EDT
Scheduled - We will be applying infrastructure upgrades during this time. There might be a small period of downtime during the upgrade process.
May 12, 14:26 EDT
May 14, 2022
Resolved - We've confirmed that our rollback resolved the latency on query. We are back in baseline normal prep times.
May 14, 07:11 EDT
Monitoring - We've identified a query contributing to the latency and rolled back some recent system upgrades to mitigate the issue. We are continuing to monitor the issue.
May 14, 06:28 EDT
Investigating - We are aware of high prep times on scheduled jobs starting from 2:00AM Eastern and are actively investigating the issue.
May 14, 05:43 EDT
May 13, 2022
Resolved - PR-triggered runs are now once again updating GitHub commit statuses as expected for all projects.
May 13, 14:11 EDT
Monitoring - We have rolled out a fix for this issue, which was impacting PR runs for a subset of GitHub-integrated projects from approximately Thursday, May 12 at 2PM Eastern until Friday, May 13 at 11:45AM Eastern.

Affected PRs should be re-submitted or updated in order to trigger a re-run of the dbt Cloud job and an update to the commit status and allow merges.

May 13, 13:06 EDT
Identified - We have identified the root cause which is impacting only projects that were integrated with GitHub before May 2021. We are rolling out a fix which should go live in the next 30 minutes.

For urgent cases, dissociating and reassociating the GitHub repository and re-submitting the PR or re-running the job manually should successfully update the status.

May 13, 12:25 EDT
Investigating - We are aware of an issue with commit status messages not being updated on GitHub for PR-triggered jobs and are actively investigating the issue.
May 13, 11:51 EDT