- Detected by Pingoru
- Jun 13, 2026, 03:53 AM UTC
- Resolved
- Jun 13, 2026, 07:56 AM UTC
- Duration
- 4h 2m
Affected: GitLab DuoGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 07:08 AM UTC
- Resolved
- Jun 11, 2026, 08:19 PM UTC
- Duration
- 13h 10m
Affected: WebsiteGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 09:17 AM UTC
- Resolved
- Jun 08, 2026, 01:22 PM UTC
- Duration
- 4h 4m
Affected: WebsiteGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 11:58 AM UTC
- Resolved
- Jun 05, 2026, 01:46 PM UTC
- Duration
- 1h 47m
Affected: CI/CDCI/CD - Hosted runners on LinuxGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 13 updates
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 04:05 PM UTC
- Resolved
- Jun 05, 2026, 07:51 AM UTC
- Duration
- 15h 45m
Affected: GitLab DuoGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 02:39 PM UTC
- Resolved
- Jun 03, 2026, 05:53 PM UTC
- Duration
- 3h 13m
Affected: GitLab DuoGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 12:50 PM UTC
- Resolved
- May 29, 2026, 11:41 PM UTC
- Duration
- 10h 50m
Affected: GitLab DuoGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 15 updates
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 07:31 AM UTC
- Resolved
- May 27, 2026, 09:55 AM UTC
- Duration
- 2h 23m
Affected: Git OperationsGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 04:16 PM UTC
- Resolved
- May 26, 2026, 05:21 PM UTC
- Duration
- 1h 4m
Affected: CI/CD - Hosted runners on LinuxGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 12:50 PM UTC
- Resolved
- May 26, 2026, 02:25 PM UTC
- Duration
- 1h 34m
Affected: GitLab DuoGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 09:42 AM UTC
- Resolved
- May 21, 2026, 10:29 AM UTC
- Duration
- 46m
Affected: WebsiteAPIGit OperationsPackage RegistryContainer RegistryGitLab PagesCI/CDCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on WindowsCI/CD - Hosted runners on macOSCI/CD - Hosted runners for GitLab community contributionsCI/CD - Self-managed runnersCI/CD - Self-managed runners (Self-Managed Runner Connectivity)SAML SSO - GitLab SaaSBackground ProcessingGitLab Customers PortalSupport ServicesSupport Services (Zendesk)packages.gitlab.comversion.gitlab.comversion.gitlab.com (AWS)forum.gitlab.comforum.gitlab.com (Digital Ocean)docs.gitlab.comCanaryGitLab DuoGitLab agent server for KubernetesGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 11:03 AM UTC
- Resolved
- May 18, 2026, 12:41 PM UTC
- Duration
- 1h 37m
Affected: CI/CDCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on WindowsCI/CD - Hosted runners on macOSCI/CD - Hosted runners for GitLab community contributionsversion.gitlab.com (AWS)GitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 03:37 PM UTC
- Resolved
- May 15, 2026, 06:11 PM UTC
- Duration
- 2h 33m
Affected: GitLab DuoGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 04:23 PM UTC
- Resolved
- May 13, 2026, 05:33 PM UTC
- Duration
- 1h 9m
Affected: CI/CDGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 09:04 PM UTC
- Resolved
- May 12, 2026, 09:33 PM UTC
- Duration
- 28m
Affected: WebsiteGit OperationsCI/CDGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 05:37 PM UTC
- Resolved
- May 12, 2026, 09:08 PM UTC
- Duration
- 3h 31m
Affected: WebsiteAPIGit OperationsPackage RegistryContainer RegistryGitLab PagesCI/CDCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on WindowsCI/CD - Hosted runners on macOSCI/CD - Hosted runners for GitLab community contributionsCI/CD - Self-managed runnersCI/CD - Self-managed runners (Self-Managed Runner Connectivity)SAML SSO - GitLab SaaSBackground Processingversion.gitlab.com (AWS)GitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 13 updates
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 08:41 AM UTC
- Resolved
- May 11, 2026, 11:16 AM UTC
- Duration
- 2h 34m
Affected: WebsiteGit OperationsGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 3 updates
-
investigating May 11, 2026, 08:41 AM UTC
We are currently investigating 500 errors when accessing repositories and Gitaly errors when pushing to a repository. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041
-
monitoring May 11, 2026, 09:12 AM UTC
To restore the service, we restarted the Gitaly process. We will monitor for any recurrence. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041
-
resolved May 11, 2026, 11:16 AM UTC
The issue has been resolved. The 500 errors when accessing repositories should not seen anymore and affected Git operations should work as expected. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 03:44 PM UTC
- Resolved
- May 11, 2026, 11:56 PM UTC
- Duration
- 4d 8h
Affected: Background ProcessingGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 07:01 PM UTC
- Resolved
- May 06, 2026, 08:49 PM UTC
- Duration
- 1h 48m
Affected: CanaryGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 2 updates
-
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
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 03:51 PM UTC
- Resolved
- Apr 30, 2026, 05:10 PM UTC
- Duration
- 1h 19m
Affected: CI/CD - Hosted runners on LinuxGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 3 updates
-
investigating Apr 30, 2026, 03:51 PM UTC
We are currently investigating issues with hosted `saas-linux-small-amd64` GitLab runners. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21936
-
identified Apr 30, 2026, 04:10 PM UTC
Our team has identified a resource issue that has lead to a delay in pending jobs on Small GitLab Hosted Runners. Users with CI jobs tagged for small runners (saas-linux-small-amd64) might experience some delays. Our team is continuing to work on this.
-
identified Apr 30, 2026, 04:38 PM UTC
Our team is working on configuration changes to improve resourcing. We're still seeing a job backlog and are continuing to monitor with these changes.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 11:05 AM UTC
- Resolved
- Apr 28, 2026, 01:27 PM UTC
- Duration
- 2h 21m
Affected: WebsiteGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 2 updates
-
investigating Apr 28, 2026, 11:05 AM UTC
We are currently investigating issues with dependency scanning. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905`.
-
identified Apr 28, 2026, 12:02 PM UTC
We've identified cause of the issue and are working on resolving it. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905.
Read the full incident report →