Companies/dbt Labs/Incidents

dbt Labs: Git failures for GitLab-integrated accounts

Affected components: 01JBCBN0CAA2QVD10W6BKMPDRF01JBCBN1KQCDFX2SZ1WHPRVPYE01JBCBN2VYP78DYVVARQJK3MJJ01JBCBN5C72ZRZYFXJYB936JEA01JBCD2ZXG0Y9ZGBC077TXQKN101JBCQQZ41M6BZCP649F5FFZYS01JBCQVPBNMJ60EVAVX611QWT201JBCR0NDT2ENWZZ6RZEF825KQ01JH8R89TW25GVBJRS0C69K5H901JRKCJTC2FSGQQZQBZHCSX8BB01K1EH8NN6PK7YBC7EV6QHG2WZ01K4T29F35RK5FECSXM2SW4XE801KF46A8M70AMCM21TWN89Z56W01KSMXDZMNB8ZAGBC1K7WZENT601KX12QA4EC01M2PN22RAW56SX

Timeline of updates

1. identified2026-10-07 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.

2. resolved2026-10-07 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.

Impact, status and times are the vendor’s own, as last archived. View on status.getdbt.com (opens in new tab).

dbt Labs profileRecent dbt Labs incidentsMarkdownJSON