Git failures for GitLab-integrated accounts

Final update

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.

1. Resolved · Oct 7, 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 [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.
2. Identified · Oct 7, 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.