Expired GitLab project access tokens not refreshing causing failures in posting commit statuses
dbt Cloud does not post CI job commit statuses back to GitLab for affected projects. This affects existing projects with a GitLab integration whose project access token expired, in the EU2 (Azure) region after 06:00 UTC on 3 November. dbt Cloud identified the cause and is working on a fix.
State
Identified
Started
Ongoing for
1 h 39 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 3 min 64%
Identified
36 min 36%
Updates
Times in UTCAs posted by dbt Cloud
We have identified an issue with Gitlab project access tokens not being refreshed. Our engineers are working on a fix for this, and we will provide an update shortly.
We’re investigating an issue with the GitLab integration that is causing CI job commit statuses to not post back to GitLab. This is **limited to existing projects with a GitLab integration whose project access token has expired and was not refreshed.** It is impacting a small number of customers on the EU2 (Azure) region anytime after 06:00 UTC (01:00 AM Eastern) on 3 November. Affected customers may see missing pipeline statuses on merge requests, which can block merges that require passing statuses. **New project configurations and new GitLab integrations are not impacted.** There is currently no known workaround for affected existing projects, and reconnecting the repository does not resolve it. Our engineers are working on a resolution and we will provide updates approximately every 30 minutes, or as soon as new information becomes available. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you believe you are affected.
We’re investigating an issue with the GitLab integration that is causing CI job commit statuses to not post back to GitLab. This is **limited to existing projects with a GitLab integration whose project access token has expired and was not refreshed.** It is impacting a small number of customers on the EU2 (Azure) region anytime after 06:00 UTC (01:00 AM Eastern) on 3 November. Affected customers may see missing pipeline statuses on merge requests, which can block merges that require passing statuses. **New project configurations and new GitLab integrations are not impacted.** There is currently no known workaround for affected existing projects, and reconnecting the repository does not resolve it. Our engineers are working on a resolution and we will provide updates approximately every 30 minutes, or as soon as new information becomes available. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you believe you are affected.
dbt Cloud in the last 90 days
Full historyIncidents in 90 days
23
Days with an incident
25
Median duration
2 h 58 min
This incident
45% shorter than 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.live/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.live/feed.xml?providers=dbt/feed subscribe https://outages.live/feed.xml?providers=dbtFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane