GitLab incident

500 errors while accessing projects

Resolved after 7 hours 2 minutes, affecting Website and Git Operations and 1 more, on September 24, 2026.

resolved Sep 24, 2026, 08:50 PM UTC

We're no longer seeing elevated errors, so we are resolving this incident. If you continue to experience any errors on GitLab.com, please open a ticket. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

Started
Sep 24, 2026, 01:48 PM UTC
Resolved
Sep 24, 2026, 08:50 PM UTC
Duration
7h 2m
Detected by Pingoru
Sep 24, 2026, 01:48 PM UTC

Affected components

WebsiteGit OperationsGitLab agent server for Kubernetes (GitLab agent server for Kubernetes — Google Compute Engine)

Update timeline

  1. investigating Sep 24, 2026, 01:48 PM UTC

    We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause. You can follow developments here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

  2. investigating Sep 24, 2026, 01:48 PM UTC

    We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause.

  3. investigating Sep 24, 2026, 02:10 PM UTC

    A temporary mitigation has been implemented however the cause of the incident is still being investigated.

  4. investigating Sep 24, 2026, 02:44 PM UTC

    The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution.

  5. investigating Sep 24, 2026, 02:44 PM UTC

    The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution.

  6. investigating Sep 24, 2026, 03:17 PM UTC

    The incident team continues to investigate the cause of this incident. In the meantime, we are seeing intermittent improvements in the ability to access projects.

  7. investigating Sep 24, 2026, 03:17 PM UTC

    The incident team continues to investigate the cause of this incident. In the meantime, we are seeing intermittent improvements in the ability to access projects.

  8. investigating Sep 24, 2026, 04:13 PM UTC

    No material updates at this time. We are continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

  9. investigating Sep 24, 2026, 04:13 PM UTC

    No material updates at this time. We are continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

  10. investigating Sep 24, 2026, 05:21 PM UTC

    We're continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

  11. investigating Sep 24, 2026, 05:21 PM UTC

    We're continuing our investigation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

  12. identified Sep 24, 2026, 06:32 PM UTC

    The team has identified the potential cause of the spike in 500 errors and is working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

  13. identified Sep 24, 2026, 06:32 PM UTC

    The team has identified the potential cause of the spike in 500 errors and is working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

  14. identified Sep 24, 2026, 08:03 PM UTC

    The team is still working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

  15. identified Sep 24, 2026, 08:03 PM UTC

    The team is still working on the fix. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

  16. resolved Sep 24, 2026, 08:50 PM UTC

    We're no longer seeing elevated errors, so we are resolving this incident. If you continue to experience any errors on GitLab.com, please open a ticket. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015

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.

Add your stack →