2025-01-18: WebServiceLoadbalancerErrorSLOViolation - increased error rate on GPRD cny and main stage
Customer Impact
Malformed git clone
commands return a 500 error instead of a 404 error.
$ git clone https://gitlab.com/gitlab-org/gitlab-runner/tree/v17.3.0.git
Cloning into 'v17.3.0'...
remote: Internal Server Error
fatal: unable to access 'https://gitlab.com/gitlab-org/gitlab-runner/tree/v17.3.0.git/': The requested URL returned error: 500
Current Status
All URLs seem to be malformed URLs ran from git clone
for example:
$ git clone https://gitlab.com/gitlab-org/gitlab-runner/tree/v17.3.0.git
Cloning into 'v17.3.0'...
remote: Internal Server Error
fatal: unable to access 'https://gitlab.com/gitlab-org/gitlab-runner/tree/v17.3.0.git/': The requested URL returned error: 500
We identified that these seem to be coming from a single user requesting a bunch of public projects
These shouldn't be a 500 error but should be a 404 or 4xx error when developing a fix we identified that in GDK (local development) is works as expected making it seem like an issue with GitLab.com
$ git clone http://gdk.test:3000/root/gitlab-runner/-/tree/v17.8.1.git
Cloning into 'v17.8.1'...
fatal: repository 'http://gdk.test:3000/root/gitlab-runner/-/tree/v17.8.1.git/' not found
$ git clone https://gitlab.com/gitlab-org/gitlab-runner/tree/v17.3.0.git
Cloning into 'v17.3.0'...
remote: Internal Server Error
fatal: unable to access 'https://gitlab.com/gitlab-org/gitlab-runner/tree/v17.3.0.git/': The requested URL returned error: 500
Next Items
- Investigate why on GDK we get 404 and we get a 500 error. This might be how we route requests.

References and helpful links

Recent Events (available internally only):
- Feature Flag Log - Chatops to toggle Feature Flags Documentation
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Deployment Guidance
- Deployments Log | Gitlab.com Latest Updates
- Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in our handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.
Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.