2024-12-16: Timeout errors from Utah based IP addresses
Customer Impact
Some customers based in Salt Lake City, UT are experiencing intermittent timeouts while communicating with Gitlab.com over SSH, HTTPS, and also communicating with Registry.
Those experiencing issues may be able to utilise runners as a temporary workaround.
Current Status
December 19th 04:00 UTC:
The Google network ops team has identified a BGP flapping issue in the us-west3
region causing misrouting to Cloudflare's SLC (Salt Lake City) PoP (Point of Presence) on the GCP end. The issue has been fixed since around 2024-12-18 22:00 UTC and the routing errors in this region appear to be resolved.
We have received confirmation from customers in the affected region that the issue has been resolved.
For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.

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.