GitLab incident
Elevated Errors Affecting GitLab Duo Custom Agents
GitLab experienced a minor incident on July 17, 2026 affecting GitLab Duo and GitLab agent server for Kubernetes (Google Compute Engine), lasting 1h 25m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 17, 2026, 04:10 PM UTC
We're investigating an issue affecting GitLab Duo Custom Agents on GitLab.com. Our team is actively working to identify the cause and restore normal service. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- investigating Jul 17, 2026, 04:10 PM UTC
We're investigating an issue affecting GitLab Duo Custom Agents on GitLab.com. Our team is actively working to identify the cause and restore normal service.
- investigating Jul 17, 2026, 04:26 PM UTC
Our team is actively investigating the root cause of this issue. We'll continue to share updates as we learn more.
- investigating Jul 17, 2026, 04:26 PM UTC
Our team is actively investigating the root cause of this issue. We'll continue to share updates as we learn more.
- investigating Jul 17, 2026, 04:44 PM UTC
We continue to investigate the root cause of this issue. There are no material updates at this time, and we'll share additional information as it becomes available.
- investigating Jul 17, 2026, 04:44 PM UTC
We continue to investigate the root cause of this issue. There are no material updates at this time, and we'll share additional information as it becomes available.
- investigating Jul 17, 2026, 05:09 PM UTC
We're seeing signs of recovery, but our investigation into the root cause remains ongoing. We'll continue to provide updates as more information becomes available.
- investigating Jul 17, 2026, 05:09 PM UTC
We're seeing signs of recovery, but our investigation into the root cause remains ongoing. We'll continue to provide updates as more information becomes available.
- monitoring Jul 17, 2026, 05:22 PM UTC
We're seeing service recover and error rates return to expected levels. We'll continue to monitor the environment to ensure the recovery is sustained.
- monitoring Jul 17, 2026, 05:22 PM UTC
We're seeing service recover and error rates return to expected levels. We'll continue to monitor the environment to ensure the recovery is sustained.
- resolved Jul 17, 2026, 05:36 PM UTC
We've identified and mitigated the root cause of this issue. Service has remained stable throughout the monitoring period, and this incident is now resolved.