Git failures for GitLab-integrated accounts

What to do

• Check whether your product depends on dbt Cloud. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-12 19:21 UTC and 2026-10-07 08:03 UTC may need a replay.

• Subscribe to dbt Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=dbt-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from dbt Cloud 2

1. identifiedOct 7, 2026, 7:23 AM 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.

   provider

2. resolvedOct 7, 2026, 8:03 AM 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 [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.