Search

Changes / GitLab / The gitlab-org group is experiencing 500 errors

GitLab: Major incident: The gitlab-org group is experiencing 500 errors

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: status.gitlab.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: The gitlab-org group is experiencing 500 errors
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-09-10 16:02 UTC
AddedResolved time#5
Before: not present
After: 2025-09-10 16:56 UTC
AddedAffected components#6
Before: not present
After: Canary, Git Operations, Website
AddedUpdateinvestigating#7
Before: not present
After: The gitlab-org group is experiencing 500s. This issue is not widespread. Customers interacting with any gitlab-org repos might be affected. More information about the incident: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20510
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate the root cause of the issue. Customers whose pipelines interact with artifacts hosted in gitlab-org may see 500 errors. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20510.
AddedUpdateresolved#9
Before: not present
After: After a brief monitoring period we've confirmed that Gitaly is once again available. Clones and operations involving gitlab-org projects are now operational, so we're considering the incident resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: The gitlab-org group is experiencing 500 errors (this change)Major incident

All GitLab changes → · GitLab profile · Markdown · JSON