All Systems Operational
North America (N. Virginia) ? Operational
90 days ago
99.98 % uptime
Today
Web Application Operational
90 days ago
100.0 % uptime
Today
IDE Operational
90 days ago
99.93 % uptime
Today
Scheduled Jobs Operational
90 days ago
100.0 % 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
100.0 % uptime
Today
Web Application Operational
90 days ago
100.0 % uptime
Today
IDE Operational
90 days ago
100.0 % uptime
Today
Scheduled Jobs 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
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
Australia (Sydney) ? Operational
90 days ago
99.99 % uptime
Today
Web Application Operational
90 days ago
100.0 % uptime
Today
IDE Operational
90 days ago
99.95 % uptime
Today
Scheduled Jobs Operational
90 days ago
100.0 % 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 ec2-ap-southeast-2 Operational
AWS kms-ap-southeast-2 Operational
AWS s3-ap-southeast-2 Operational
North America Cell 1 ? Operational
90 days ago
100.0 % uptime
Today
Web Application Operational
90 days ago
100.0 % uptime
Today
IDE Operational
90 days ago
100.0 % uptime
Today
Scheduled Jobs Operational
90 days ago
100.0 % 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
North America Cell 2 ? Operational
90 days ago
100.0 % uptime
Today
Web Application Operational
90 days ago
100.0 % uptime
Today
IDE Operational
90 days ago
100.0 % uptime
Today
Scheduled Jobs Operational
90 days ago
100.0 % 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
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 SSH 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.
Past Incidents
Apr 20, 2024

No incidents reported today.

Apr 19, 2024
Completed - The scheduled maintenance has been completed.
Apr 19, 21:15 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 19, 20:15 EDT
Scheduled - We will be performing upgrades on our infrastructure. We expect to see a small amount of downtime (less than 5 min) impacting all of dbt Cloud in Cell 1.
Apr 19, 12:13 EDT
Apr 18, 2024

No incidents reported.

Apr 17, 2024
Resolved - The issue has been resolved, and all affected systems are now functioning normally.

Please contact Support via email at support@getdbt.com if you continue to experience any issues and are unsure of the root cause.

We understand how critical dbt Cloud is to your ability to get work done day-to-day and your experience matters to us. We’re grateful to you for your patience during this incident.

Apr 17, 03:42 EDT
Identified - We have identified an issue with Snowflake OAuth when users attempt to authenticate which appears as a 500 error. We believe we have identified the root cause and currently investigating further. Please contact us on support@getdbt.com with any questions.
Apr 17, 02:34 EDT
Apr 16, 2024

No incidents reported.

Apr 15, 2024

No incidents reported.

Apr 14, 2024

No incidents reported.

Apr 13, 2024

No incidents reported.

Apr 12, 2024

No incidents reported.

Apr 11, 2024

No incidents reported.

Apr 10, 2024
Resolved - This issue has been resolved. Please reach out to support in case you have any issues.
Apr 10, 20:08 EDT
Monitoring - A fix is currently being implemented, and we will continue to monitor the progress of this issue. Please contact Support via email support@getdbt.com if you continue to experience issues with GitHub Webhooks while running CI jobs.
Apr 10, 19:02 EDT
Identified - We have identified the issue that is causing the failed GitHub Webhooks in US multi-cells 1 and 2, and are working on a fix. We will provide an update once that fix has been rolled out.
Apr 10, 17:50 EDT
Investigating - We are seeing issues causing Github Webhooks to fail within our US multi-cells 1 and 2. We're currently investigating and will be updating shortly.
Apr 10, 17:26 EDT
Resolved - This incident is now resolved. If you do continue to experience any further issue, please contact support@getdbt.com
Apr 10, 03:53 EDT
Monitoring - We have applied a fix for the issue and are currently monitoring. Tests on internal environments have confirmed that the status and not the status code is being returned for the status_humanized field.
Apr 10, 03:40 EDT
Identified - We have identified the cause and are working on a fix.
Apr 10, 02:47 EDT
Investigating - We have had reports that the dbt Cloud API has begun returning status codes (e.g. "3") into the "status_humanized" field when polling API jobs. This affects any implementations expecting humanized status strings (i.e. "Running", "Success", etc.)

We are investigating the problem and hope to have a further update soon.

Apr 10, 02:25 EDT
Apr 9, 2024
Resolved - We would like to inform you that a fix has been applied and the issue has been resolved. If you do continue to experience the issue, please contact support@getdbt.com
Apr 9, 12:51 EDT
Identified - We have identified the cause of the issue and are working on a fix.
Apr 9, 11:56 EDT
Investigating - We have had a couple of reports of a full source freshness being run in jobs even when only a specific source is selected. If run step is dbt source freshness -s source:
and the Run source freshness checkbox is unchecked, a full dbt source freshness is run as an additional step.

We are investigating the cause and hope to have a further update soon.

Apr 9, 10:43 EDT
Apr 8, 2024

No incidents reported.

Apr 7, 2024

No incidents reported.

Apr 6, 2024

No incidents reported.