2024-09-10: Increased errors on GitLab.com
Customer Impact
Main Gitlab (Web and API) services were unavailable for a 5 minute period due to a database unavailability.
Services are recovered after that, and stable since then.
Current Status
We had issues with Bad Gateway errors on GitLab.com and services across Gitlab becoming unresponsive. The issue was resolved after ~5 minutes and services went back to normal.
We traced back the issue to a failing database disk. We'll continue to investigate underlying reasons.
More information will be added as we investigate the issue.
For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: Gitlab down / slow to respond during a short period around 12:55 - 13:00 UTC
- Service Impact: ServicePatroniCi
- Impact Duration: ~12:55 - 13:00 UTC ~5 minutes
- Root cause: Failing disk on a database host. We're continuing to investigate the whether there was a reason for the failing disk.
📚 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.