Outage in GitLab
Runner 17.8.0 incorrectly tagged
Resolved Minor
January 16, 2025 - Started 10 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?
One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.
Latest Updates ( sorted recent to last )
10 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.
10 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
Unable to confirm secondary email address - 1 day ago
Slowness and delays on GitLab.com - 10 days ago
GitLab Duo Chat - 401 Errors - 18 days ago
Multiple services impacted by AWS degradation - 20 days ago
Code search errors on GitLab.com - about 1 month ago
The Status Page Aggregator Built for IT Teams
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 · 4522 services available
Integrations with
