dbt Cloud Outage History

Started Apr 08, 2026, 08:01 PM UTC· resolved Apr 10, 2026, 09:49 PM UTC

1. identified Apr 08, 2026, 08:01 PM UTC

   We have identified an issue with delays in artifact processing that is causing stale metadata to display in Catalog. This is impacting Catalog anytime after 20:37 UTC. A fix is being implemented, and we will provide an update shortly.

2. monitoring Apr 08, 2026, 09:43 PM UTC

   We have deployed a fix for artifact processing that was causing delays in metadata updates in Catalog. Catalog has returned to its normal state and we are continuing to monitor.

3. resolved Apr 10, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 21:48 UTC. We have put measures in place to prevent a recurrence and artifact processing has 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.

Read the full incident report →

Started Apr 08, 2026, 08:01 PM UTC· resolved Apr 10, 2026, 09:49 PM UTC

1. identified Apr 08, 2026, 08:01 PM UTC

   We have identified an issue with delays in artifact processing that is causing stale metadata to display in Catalog. This is impacting Catalog anytime after 20:37 UTC. A fix is being implemented, and we will provide an update shortly.

2. monitoring Apr 08, 2026, 09:43 PM UTC

   We have deployed a fix for artifact processing that was causing delays in metadata updates in Catalog. Catalog has returned to its normal state and we are continuing to monitor.

3. resolved Apr 10, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 21:48 UTC. We have put measures in place to prevent a recurrence and artifact processing has 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.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 07, 2026, 03:46 PM UTC· resolved Apr 07, 2026, 03:49 PM UTC

1. monitoring Apr 07, 2026, 03:46 PM UTC

   Started: April 6, 2026 at approximately 3:00 PM ET Resolved: April 7, 2026 at approximately 11:30 AM ET Summary: We identified an issue where the Discovery API was returning stale model applied state data. As a result, model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs. This caused incorrect data to be displayed in dbt Explorer and via the Discovery API. Impact: Users may have seen outdated "last updated" timestamps and stale execution metadata on their models in dbt Explorer and via the Discovery API, despite jobs completing successfully. Resolution: At 11:30 AM ET on April 7, we deployed a fix to our metadata ingestion pipeline. Going forward, metadata will update correctly after each successful run. Note: Models that were affected during this period will not be retroactively corrected. Running your dbt Cloud jobs again will refresh the metadata to the correct state. We apologise for any disruption this caused to your workflows.

2. resolved Apr 07, 2026, 03:49 PM UTC

   Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata.

Read the full incident report →

Started Apr 05, 2026, 09:09 AM UTC· resolved Apr 05, 2026, 09:09 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Apr 05, 2026, 09:09 AM UTC· resolved Apr 05, 2026, 09:09 AM UTC

1. resolved Apr 05, 2026, 09:09 AM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 5:09 AM Eastern and 5:17AM Eastern an issue with the Scheduled Jobs resulted in Delayed Runs and Run Locks in US MT. The issue has since resolved itself. 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.

2. identified Apr 05, 2026, 09:09 AM UTC

   We have identified an issue with Scheduled Jobs resulted in Delayed Runs and Run Locks in US MT. We will provide further updates shortly.

Read the full incident report →

Started Mar 31, 2026, 08:09 PM UTC· resolved Mar 31, 2026, 08:09 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 31, 2026, 07:43 PM UTC· resolved Mar 31, 2026, 08:09 PM UTC

1. identified Mar 31, 2026, 07:43 PM UTC

   We have identified an issue with an internal service latency that resulted in delayed and failed dbt run invocations. A fix is being implemented, and we will provide an update shortly.

2. resolved Mar 31, 2026, 08:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. Between 19:43 UTC and 20:09 UTC an issue with an internal service latency resulted in delays and failures of dbt invocations. We have put measures in place to prevent a recurrence and dbt invocations have returned to normal. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Mar 31, 2026, 07:43 PM UTC· resolved Mar 31, 2026, 08:09 PM UTC

1. identified Mar 31, 2026, 07:43 PM UTC

   We have identified an issue with an internal service latency that resulted in delayed and failed dbt run invocations. A fix is being implemented, and we will provide an update shortly.

2. resolved Mar 31, 2026, 08:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. Between 19:43 UTC and 20:09 UTC an issue with an internal service latency resulted in delays and failures of dbt invocations. We have put measures in place to prevent a recurrence and dbt invocations have returned to normal. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Mar 27, 2026, 11:22 AM UTC· resolved Mar 27, 2026, 02:08 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 27, 2026, 11:22 AM UTC· resolved Mar 27, 2026, 02:08 PM UTC

1. investigating Mar 27, 2026, 11:22 AM UTC

   We are currently investigating an issue affecting dbt Cloud on Azure US multi-cell environment, where users are unable to access the platform or experience service unavailability. Our team is actively working to identify the root cause and restore full functionality. We will provide an update shortly.

2. monitoring Mar 27, 2026, 01:01 PM UTC

   We have identified and addressed the root cause of this incident. The issue originated from a routine vertical scaling operation on the Azure US multi-cell database that failed silently due to Azure capacity constraints. After direct intervention to restore the server, dbt has been brought back online across all affected components as of 7:43 AM EST. We are actively monitoring the environment to confirm full stability before resolving this incident. We appreciate your patience and will provide a final update shortly.

3. resolved Mar 27, 2026, 02:08 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 7:43am Eastern. Between 5:56am Eastern and 7:43am Eastern, an issue with the internal database server resulted in users on the dbt Azure US Multi-Cell environment being unable to access the platform or experiencing service unavailability,

Read the full incident report →

Started Mar 26, 2026, 10:02 PM UTC· resolved Mar 26, 2026, 11:23 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 26, 2026, 10:02 PM UTC· resolved Mar 26, 2026, 11:23 PM UTC

1. investigating Mar 26, 2026, 10:02 PM UTC

   We're currently experiencing some issues due to the current outage with OpenAI: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP Will be providing updates as soon as more information becomes available.

2. identified Mar 26, 2026, 10:03 PM UTC

   We're currently experiencing some issues due to the current outage with OpenAI: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP Will be providing updates as soon as more information becomes available.

3. resolved Mar 26, 2026, 11:23 PM UTC

   The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause.

Read the full incident report →