GitLab experienced a minor incident on May 6, 2026 affecting Canary and GitLab agent server for Kubernetes (Google Compute Engine), lasting 1h 48m. The incident has been resolved; the full update timeline is below.
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
Looking to track GitLab downtime and outages?
Pingoru polls GitLab's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when GitLab reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track GitLab alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required