2023-03-29: Degraded performance on Gitlab.com
Customer Impact
Gitlab.com experienced site-wide degradation between 14:15 and 17:57 UTC on 2023-03-29. All elements of the site were impacted during this time.
Current Status
We saw degraded performance on gitlab.com between 14:15 and 17:57 UTC (March 29, 2023). The root cause was identified and a revert was deployed to production as of 01:02 UTC (March 30, 2023). We are looking into how the identified cause could have been captured and mitigated earlier. No further updates will be posted to this issue.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact:
Site wide
- Service Impact: ServiceWeb ServiceCI Runners ServicePatroniCI ServiceSidekiq
- Impact Duration:
14:15 utc - 17:57 utc
- Root cause: Suspected: RootCauseSoftware-Change
📚 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 and/or Hot Patching | 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 out 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.