Global IT infrastructure status

GITLAB

🟡 Degraded

Errors Opening Repositories

Investigating

Started
2026-09-17 20:44 UTC
4 days ago
Last update
2026-09-18 13:45 UTC
3 days ago
Running for
4d 3h

Timeline

  1. 18 Sep · 13:45 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

    September 18, 2026 02:34 UTC
    Investigating - 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.

    September 18, 2026 03:02 UTC
    Investigating - 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.

    September 18, 2026 04:00 UTC
    Investigating - A further mitigation c

  2. 18 Sep · 11:07 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

    September 18, 2026 02:34 UTC
    Investigating - 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.

    September 18, 2026 03:02 UTC
    Investigating - 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.

    September 18, 2026 04:00 UTC
    Investigating - A further mitigation c

  3. 18 Sep · 09:01 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

    September 18, 2026 02:34 UTC
    Investigating - 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.

    September 18, 2026 03:02 UTC
    Investigating - 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.

    September 18, 2026 04:00 UTC
    Investigating - A further mitigation c

  4. 18 Sep · 07:59 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

    September 18, 2026 02:34 UTC
    Investigating - 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.

    September 18, 2026 03:02 UTC
    Investigating - 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.

    September 18, 2026 04:00 UTC
    Investigating - A further mitigation c

  5. 18 Sep · 06:28 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

    September 18, 2026 02:34 UTC
    Investigating - 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.

    September 18, 2026 03:02 UTC
    Investigating - 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.

    September 18, 2026 04:00 UTC
    Investigating - A further mitigation c

  6. 18 Sep · 04:00 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

    September 18, 2026 02:34 UTC
    Investigating - 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.

    September 18, 2026 03:02 UTC
    Investigating - 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.

    September 18, 2026 04:00 UTC
    Investigating - A further mitigation c

  7. 18 Sep · 04:00 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

    September 18, 2026 02:34 UTC
    Investigating - 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.

    September 18, 2026 03:02 UTC
    Investigating - 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.

    September 18, 2026 04:00 UTC
    Investigating - A further mitigation c

  8. 18 Sep · 03:02 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

    September 18, 2026 02:34 UTC
    Investigating - 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.

    September 18, 2026 03:02 UTC
    Investigating - 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.

  9. 18 Sep · 02:34 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

    September 18, 2026 02:34 UTC
    Investigating - 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.

  10. 18 Sep · 02:01 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

    September 18, 2026 02:01 UTC
    Investigating - Investigation continues. We will shortly be restarting the affected Gitaly node after reconfiguration. Further updates will be provided accordingly.

  11. 18 Sep · 01:25 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

    September 18, 2026 01:25 UTC
    Investigating - 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.

  12. 18 Sep · 00:29 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

    September 18, 2026 00:29 UTC
    Identified - 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.

  13. 17 Sep · 23:23 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

    September 17, 2026 23:23 UTC
    Identified - 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.

  14. 17 Sep · 21:56 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - We're investigating reports of customers unable to open projects, receiving error 500 instead.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

  15. 17 Sep · 21:56 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - 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.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

    September 17, 2026 21:56 UTC
    Identified - We’ve identified an abuse vector as the root cause and begun mitigation efforts. Early signs indicate that the service is recovering.

  16. 17 Sep · 21:32 UTC 🟡 Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - 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.

    September 17, 2026 21:32 UTC
    Investigating - No material updates are available at this time. Our team continues to investigate the root cause of the issue.

  17. 17 Sep · 20:44 UTC ⚪ Investigating rss

    September 17, 2026 20:44 UTC
    Investigating - 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.

Source

Official GitLab status — view original incident ↗

IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.