Is GitLab CI/CD - SaaS Private Runners Down? Check the current GitLab CI/CD - SaaS Private Runners status
GitLab CI/CD - SaaS Private Runners is operational
Updated
GitLab CI/CD - SaaS Private Runners is operational
Updated
Monitoring GitLab since March 2022. Learn more
Total Incidents in 2025
2 incidents
The best way to monitor GitLab and other dependencies
IsDown pulls data from GitLab's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.
This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.
No comments yet
IsDown has tracked 36 incidents for GitLab CI/CD - SaaS Private Runners since started monitoring GitLab status in March 2022.
20 days ago · lasted about 1 hour
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. More details
30 days ago · lasted about 1 hour
We saw elevated 500 errors on gitlab.com which have then decreased. We're continuing to monitor for further errors More details
about 2 months ago · lasted about 9 hours
We are seeing 500 errors with runner registrations. We have identified the cause, and are working on a fix. More details https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18984 More details
We've tracked and collected 36 incidents for GitLab CI/CD - SaaS Private Runners since started monitoring GitLab status
Number of Incidents
2 issues
Last incident
20 days ago
Get instant alerts when your cloud vendors experience downtime. Create an internal status page to keep your team in the loop and minimize the impact of service disruptions.
IsDown offers an easy way to monitor GitLab with maximum flexibility
IsDown monitors CI/CD - GitLab SaaS Private Runners for major outages. A major outage is when CI/CD - GitLab SaaS Private Runners experiences a critical issue that severely affects one or more services/regions. When GitLab marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.
IsDown monitors GitLab status page for minor outages. A minor outage is when CI/CD - GitLab SaaS Private Runners experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.
IsDown collects all information from the outages published in GitLab status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
IsDown monitors GitLab and all their 17 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
GitLab and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.
GitLab CI/CD - SaaS Private Runners isn't down. You can check GitLab CI/CD - SaaS Private Runners status and incident details on the top of the page. IsDown continuously monitors GitLab CI/CD - SaaS Private Runners official status page every few minutes. In the last 24 hours, there were 0 outages reported.
GitLab CI/CD - SaaS Private Runners is currently operational. You can check GitLab CI/CD - SaaS Private Runners status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.
No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.
Currently there's no report of GitLab CI/CD - SaaS Private Runners being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the GitLab CI/CD - SaaS Private Runners official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.
GitLab CI/CD - SaaS Private Runners last outage was on January 16, 2025 with the title "Runner 17.8.0 incorrectly tagged"
IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
14-day free trial · No credit card required · No code required
