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.
Resolved
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.
Monitoring
Update posted at 12:27 UTC: Services in EMEA are returning to normal. Job runs, run cancellations, notifications and metadata ingestion should now be working as expected. We are monitoring to confirm full recovery.
Identified
Update posted at 10:20 UTC: This issue is related to an ongoing incident with our cloud provider (GCP).
Metadata ingestion in EMEA is now also affected, so some customers may see out-of-date information in dbt Explorer.
Identified
Update posted at 08:20 UTC: This issue is related to an ongoing incident with our cloud provider (GCP).
We have cleared the runs that were stuck in “Running”. Until the provider incident is resolved, some run cancellations may still fail.
Investigating
Update posted at 07:56 UTC: We are continuing to investigate the issue causing delayed and stuck job runs in EMEA. Our engineering team is working to restore normal service.
We will post another update within 60 minutes.
Investigating
We are investigating an issue affecting a small number of dbt platform accounts in our EMEA region. Starting around 06:00 UTC, some job runs may be stuck in a “Running” state and can’t be cancelled. Stuck runs may count against your account’s run concurrency, so new runs may start late.
Our engineering team is working on a fix. We will post another update within 60 minutes.
