← Back to GitLab.com History
unknown✓ Resolved

503s on GitLab.com

GitLab.com•
Status
resolved
Duration
1h 14m
Updates
6
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
The issue is fully resolved and operations on GitLab.com and GitLab Duo are operating normally. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
monitoring
We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
identified
Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
identified
We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
investigating
We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
investigating
We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

📊 TECHNICAL DETAILS

Internal ID
d42ae9dd-7f08-4059-a056-c1d72be55294
External ID
6ad24c7acb21fb05a5db963c
🕐 First reported
🔄 Last Updated
✓ Resolved
UNKNOWN
Impact Level
1h 14m
Total Duration
6
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed