GitLab incident

Errors Opening Repositories

GitLab is currently experiencing a minor incident affecting Website and Git Operations and 1 more component, which began 13h ago. The vendor's full update timeline is below.

Started
Sep 17, 2026, 08:44 PM UTC
Resolved
Ongoing
Duration
● 13h 13m
Detected by Pingoru
Sep 17, 2026, 08:44 PM UTC

Affected components

WebsiteGit OperationsGitLab agent server for Kubernetes (Google Compute Engine)

Update timeline

  1. investigating Sep 17, 2026, 08:44 PM UTC

    We're investigating reports of customers unable to open projects, receiving error 500 instead. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22925.

  2. investigating Sep 17, 2026, 09:32 PM UTC

    No material updates are available at this time. Our team continues to investigate the root cause of the issue.

  3. identified Sep 17, 2026, 09:56 PM UTC

    We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

  4. identified Sep 17, 2026, 11:23 PM UTC

    We’re continuing mitigation efforts and have observed some recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations when accessing certain projects.

  5. identified Sep 18, 2026, 12:29 AM UTC

    We are continuing mitigation and monitoring recovery. Customers may still encounter HTTP 500 errors in the UI and during Git operations for certain projects. We will provide a further update as mitigation progresses.

  6. investigating Sep 18, 2026, 01:25 AM UTC

    Mitigation has not yet fully restored the GitLab UI and Git operations in certain projects. We are still investigating HTTP 500 errors and will provide a further update as more information becomes available.

  7. investigating Sep 18, 2026, 02:01 AM UTC

    Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

  8. investigating Sep 18, 2026, 02:34 AM UTC

    The restart of the affected Gitaly node did not improve the issue; HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. We are investigating and will provide further updates as the situation changes.

  9. investigating Sep 18, 2026, 03:02 AM UTC

    Further mitigation is being rolled out while we continue to investigate HTTP 500 errors affecting the GitLab UI and Git operations. We will provide further updates as the mitigation progresses.

  10. investigating Sep 18, 2026, 04:00 AM UTC

    A further mitigation change has been applied, and we are assessing its impact. HTTP 500 errors continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.

  11. investigating Sep 18, 2026, 06:28 AM UTC

    Further mitigation change are currently being applied, and we are continuing to investigate the issue. HTTP 500 errors may continue affecting the GitLab UI and Git operations in certain projects. Further updates will follow.

  12. investigating Sep 18, 2026, 07:59 AM UTC

    We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation.

  13. monitoring Sep 18, 2026, 09:01 AM UTC

    A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation.