2024-06-20: 502 Bad Gateway on gitlab.com
Customer Impact
Some users may see 502 response errors via API, web, or git access to GitLab.com.
Current Status
Cloudflare has reported that the problem is identified and repaired.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: Web, api, and git connections to GitLab.com may fail with a 502 error.
- Service Impact: Any service behind Cloudflare.
- Impact Duration: 16:50 - 19:59 (189)
- Root cause: Cloudflare Degradation
📚 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.