support@getdbt.com address not found
The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") email has returned to normal.
The latest update from dbt Cloud.
State
Resolved
Started
67 d ago
2026-08-26 15:58 UTC
Lasted
5 h 51 min
until 2026-08-26 21:49 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 22 min 23%
Monitoring
4 h 29 min 77%
Updates
Times in UTCAs posted by dbt Cloud
The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") email has returned to normal.
Support emails from and to [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") have returned to its normal state and we are continuing to monitor.
We have deployed a fix for the [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.
We're investigating an issue with the [support@getdbt.com](mailto:support@getdbt.com "support@getdbt.com") email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [support@dbtlabs.com](mailto:support@dbtlabs.com "support@dbtlabs.com") email instead.
dbt Cloud in the last 90 days
Full historyIncidents in 90 days
22
Days with an incident
24
Median duration
2 h 58 min
This incident
2.0× the median
Other dbt Cloud incidents
All incidentsdbt Cloud·dbt Wizard SQL execution failing
The issue has been resolved, and all affected systems are now functioning normally as of 5:50pm UTC. Please contact Support via email [support@getdbt.com](http://support@getdbt.com) if you continue to experience delays and are unsure of the root cause.
dbt Cloud·Degraded performance across dbt platform
The issue has been resolved, and all affected systems are now functioning normally as of 19:35 UTC. Between 19:18- 19:35 UTC on 28 October, an issue with the dbt platform services resulted in errors for customers loading dbt Studio, running jobs, or using the API. We have put measures in place to prevent a recurrence and the platform has returned to normal. Please contact Support via email at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause
dbt Cloud·dbt deps failures in dbt job runs and Studio
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.
dbt Cloud·Delayed and stuck job runs in EMEA
**Update posted at 15:05 UTC:** This incident has been resolved. Between about 06:00 and 12:10 UTC, an incident with our cloud provider (GCP) affected services in EMEA. Some customers saw stuck or delayed job runs, failed run cancellations, delayed notifications, out-of-date information in dbt Explorer and intermittent Semantic Layer errors. All services have recovered and are working as expected. If you still see any issues, please contact support.
dbt Cloud·Intermittent dbt package download failures
The issue has been resolved, and all affected systems are now functioning normally as of 16:10 UTC. We have put measures in place to prevent a recurrence and dbt package installations have returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.
Follow dbt Cloud
Your coding agent knows when dbt Cloud is down, and tells you when a failure is theirs, not yours. You can also get dbt Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dbt" and tell me if dbt Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=dbt/feed subscribe https://outages.cc/feed.xml?providers=dbtFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane