Failure to clone (500 errors) due to GitLab incident
Resolved·Degraded performance

The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email support@getdbt.com if you continue to experience delays and are unsure of the root cause.

Tue, Apr 15, 2025, 11:31 PM
(2 weeks ago)
·
Affected components
IDE (EMEA AWS)
Scheduled Jobs (EMEA AWS)
Updates

Resolved

The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email support@getdbt.com if you continue to experience delays and are unsure of the root cause.

Tue, Apr 15, 2025, 11:31 PM

Monitoring

Update to include additional impacts with dbt Cloud scheduled jobs. We are continuing to monitor.

Tue, Apr 15, 2025, 10:27 PM(1 hour earlier)

Monitoring

We are monitoring an active incident with GitLab that is impacting some dbt Cloud user's within the IDE and deployment jobs, failing to clone due to 500 errors fatal: expected flush after ref listing . The GitLab status page can be found here: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/67fe8cb4bbc96c0e9d91739f Please reach out to Support at support@getdbt.com if you are experiencing cloning failures and are unsure if the impact is due to this incident, or if you have any questions. We will continue to monitor and update the status once this incident has been resolved.

Tue, Apr 15, 2025, 10:18 PM