Unofficial GitLab Status

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

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

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

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

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

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

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

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

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

Investigating September 18, 2026 04:00 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.

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

Investigating September 18, 2026 07:59 UTC
We are currently rolling back the deployment of Gitaly. We're waiting for the deploy to land, and we are continuing the investigation.

Monitoring September 18, 2026 09:01 UTC
A rollback release has been deployed to all Gitaly nodes. They are stable at present. However, we are continuing to monitor the situation.

Monitoring September 18, 2026 11:07 UTC
Gitaly nodes have stabilized following the completed rollback deployment. The incident has been mitigated and we remain focused on continued monitoring.

Resolved September 18, 2026 13:45 UTC
The incident has been resolved following the completion of the rollback deployment across the Gitaly nodes. All nodes have returned to a stable state, repository access has been restored. Incident team is currently investigating the root cause.

Investigating September 11, 2026 05:50 UTC
We’ve detected issues affecting a small subset of users attempting artifact uploads. The team is actively investigating to identify the full scope of the impact, and we’ll provide another update as soon as we have findings to share. Thank you for your patience.

Monitoring September 11, 2026 12:16 UTC
We are still seeing cases but tat a much less frequent rate. We will continue looking for the root cause and monitor the error rate.

Resolved September 11, 2026 19:22 UTC
We are no longer observing elevated error rates and have identified the root cause. We are marking this incident as resolved while we implement additional fixes behind the scenes.

Investigating September 10, 2026 15:24 UTC
We are seeing delays in Security Policy Evaluation which are affecting MR approvals. The cause is under investigation. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904.

Investigating September 10, 2026 16:02 UTC
Our product team is still working on finding the cause and potential mitigation steps for this issue. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904.

Investigating September 10, 2026 16:34 UTC
We are still investigating this issue. Users may still experience delays in Security Policy Evaluations, impacting MR approvals. Details in: More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

Identified September 10, 2026 17:20 UTC
We believe we have identified the underlying problem and are working to implement mitigating changes. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

Monitoring September 10, 2026 19:21 UTC
Policy evaluations and MR approvals are executing normally. We're continuing to monitor the situation while working on improvements to prevent this in the future. More: http://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

Resolved September 10, 2026 20:10 UTC
We'll now mark this as resolved while we look at additional changes as preventative measures for the future.

Investigating September 9, 2026 16:32 UTC
We're observing an increase in CI job queues. Users may see jobs stuck in a pending state for longer than usual. Jobs may not fire their associated webhooks or integrations. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897

Investigating September 9, 2026 16:58 UTC
We're still observing elevated CI job queues and are working to address the problem. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897

Monitoring September 9, 2026 17:35 UTC
CI job execution delays have improved significantly, and the backlog of pending jobs is shrinking. We're continuing to monitor the situation.

Resolved September 9, 2026 18:12 UTC
We are no longer observing delays in CI job execution and the backlog of pending jobs has been worked through. We'll now be marking this as resolved.

Identified September 8, 2026 08:54 UTC
Starting a new chat with an agent from the AI catalog does not work, and the websocket connection is immediately dropped. We are reverting the merge request that introduced the failure. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880.

Resolved September 8, 2026 09:57 UTC
The merge request that introduced the failure was reverted, and custom/catalog agents are working again. More information is available in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880.

Identified September 2, 2026 11:54 UTC
We are investigating an incident affecting GitLab.com CI/CD jobs using instance runners. Some jobs may remain pending longer than expected or may not be picked up by a runner, which can delay pipelines and deployments. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845

Resolved September 2, 2026 12:43 UTC
The incident affecting GitLab.com CI/CD jobs using instance runners is now resolved. Some jobs were delayed or remained pending while a manually initiated pg_repack database maintenance operation caused contention on the CI database, affecting runner communication and job pickup. The maintenance operation was terminated and runner metrics recovered. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845

Investigating August 27, 2026 11:46 UTC
There are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to restore normal service.

Monitoring August 27, 2026 11:53 UTC
The issue has been identified and resolved. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807

Resolved August 27, 2026 15:34 UTC
Performance remains stable and prevention steps are being implemented. Find more information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807

Investigating August 27, 2026 07:12 UTC
We are currently investigating reports of connectivity issues affecting some users accessing GitLab.com.

Monitoring August 27, 2026 07:41 UTC
We have identified a temporary filtering event by an upstream provider that affected some traffic to GitLab.com. The event has ended, and we are working with our service provider to investigate the cause and prevent recurrence. We are monitoring the situation to ensure that services have returned to normal.

Resolved August 27, 2026 09:35 UTC
Our upstream provider mitigated a genuine distributed HTTP DDoS attack against gitlab.com, but incorrectly blocked a small amount of legitimate traffic. This has now been resolved.

Investigating August 25, 2026 09:59 UTC
We are currently investigating reports of slowness and 502 errors. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

Investigating August 25, 2026 13:43 UTC
Slowness & 502s have been bursty with not much impact. A revert MR is under way while we are investigating other possible root causes. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

Monitoring August 25, 2026 14:48 UTC
We have not seen active user impact for several hours and we have identified the possible root cause. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

Monitoring August 25, 2026 18:34 UTC
We continue to monitor and have not observed any active user impact. We are working towards a permanent fix and will provide our next update once it has been implemented. More information here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

Resolved August 26, 2026 00:12 UTC
The fix has been implemented and the issue is now resolved. We have not observed any active user impact. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22783

Investigating August 24, 2026 21:22 UTC
We are currently investigating reports of deployment failures affecting GitLab Agent for Kubernetes (KAS). Our team is actively looking into the root cause and will provide updates as the investigation progresses. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

Identified August 24, 2026 21:37 UTC
We have identified a recent change believed to be contributing to the deployment failures affecting KAS. We are actively reverting this change and will provide an update once complete. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

Monitoring August 24, 2026 22:28 UTC
The rollback has been completed and we are actively monitoring to confirm resolution of the deployment failures affecting KAS. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777

Resolved August 24, 2026 22:45 UTC
The deployment failures affecting the GitLab Agent for Kubernetes (KAS) have been resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777