Errors Opening Repositories

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 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 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.

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 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 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 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 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 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 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 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 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.

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 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.

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

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 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. September 18, 2026 06:28 UTC Investigating - 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. September 18, 2026 07:59 UTC Investigating - We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation.

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 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. September 18, 2026 06:28 UTC Investigating - 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. September 18, 2026 07:59 UTC Investigating - We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation. September 18, 2026 09:01 UTC Monitoring - A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation.

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 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. September 18, 2026 06:28 UTC Investigating - 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. September 18, 2026 07:59 UTC Investigating - We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation. September 18, 2026 09:01 UTC Monitoring - A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation. September 18, 2026 11:07 UTC Monitoring - Gitaly nodes have stabilized following the completed rollback deployment. The incident has been mitigated and we remain focused on continued monitoring.

Errors Opening Repositories resolved