Resolved after 1 hour 48 minutes, affecting Canary and GitLab agent server for Kubernetes (GitLab agent server for Kubernetes — Google Compute Engine), on May 6, 2026.
The fix is still in progress. For now, the workaround is to use GitLab - Current instead of GitLab - Next. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008
Affected components
Update timeline
- identified May 06, 2026, 07:01 PM UTC
A configuration update may cause some intermittent error messages on GitLab Next (Canary). We have identified the cause and the fix is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008
- identified May 06, 2026, 07:44 PM UTC
The fix is still in progress. For now, the workaround is to use GitLab - Current instead of GitLab - Next. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008
Your product runs on more than GitLab
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services