Outage in GitLab
Runner 17.8.0 incorrectly tagged
Resolved Minor
January 16, 2025 - Started 12 months ago
- Lasted about 1 hour
Incident Report
GitLab is investigating an issue where the image for Runner 17.8.0 was not tagged correctly when uploaded to the Container Registry. We recommend continuing to use the Runner 17.7 image until the Runner 17.8 image can be tagged correctly.
Components affected
GitLab Website GitLab CI/CD - SaaS Shared Runners GitLab CI/CD - SaaS Private Runners GitLab CI/CD - Windows Shared Runners (Beta)Need to monitor GitLab outages?
- Monitor all your external dependencies in one place
- Get instant alerts when outages are detected
- Be the first to know if service is down
- Show real-time status on private or public status page
- Keep your team informed
Latest Updates ( sorted recent to last )
12 months ago - at 01/16/2025 07:38PM
GitLab is investigating an issue where the image for Runner 17.8.0 was not tagged correctly when uploaded to the Container Registry. We recommend continuing to use the Runner 17.7 image until the Runner 17.8 image can be tagged correctly.
12 months ago - at 01/16/2025 08:04PM
GitLab is working on uploading a corrected version of the 17.8.0 Runner image. We will provide an update once we have confirmed the update has been deployed.
Latest GitLab outages
Pipelines failing with 502 error - about 8 hours ago
Degraded performance for classic Duo chat - 9 days ago
GitLab.com Slow Performance - 10 days ago
Increased error rate for GitLab Duo Classic - 25 days ago
GitLab Duo Experiencing Response Errors - about 1 month ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 5420 services available
Integrations with
