dbt Cloud incident: Git failures for GitLab-integrated accounts

1. resolvedOct 7, 2026, 08:03 UTC

   A rate-limit change being previewed by GitLab caused failures for some customers using the native GitLab integration with [GitLab.com](http://GitLab.com). This impacted IDE pull and fetch operations and job run clone steps between 2026-10-07 15:23 UTC and 2026-10-07 16:03 UTC. Git operations returned to normal at the end of that window, and we have since seen only isolated rate-limit errors. Please contact Support at [[email protected]](mailto:[email protected]) if you continue to experience issues or have any follow-up questions.

2. identifiedOct 7, 2026, 07:23 UTC

   We identified that a rate-limit change being previewed by GitLab was causing Git fetch and clone requests from the native GitLab integration to fail for some customers. This affected IDE pull and fetch operations and job run clone steps.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in dbt Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Grafana Cloud: IRM Unable to Send SMS to Thailand NumbersMinor · Oct 5, 2026, 16:17 UTC
• LiveKit: Investigating reports of elevated RoomService API errorsMinor · Oct 6, 2026, 00:10 UTC
• Twilio: SMS Delivery Delays and Failures from Twilio to Movistar El SalvadorMinor · Oct 6, 2026, 20:59 UTC

How often does dbt Cloud have incidents?

dbt Cloud reported 30 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 17m. See dbt Cloud's uptime and incident history