We continuously monitor the official GitLab CI/CD - Windows Shared Runners (Beta) status page for updates on any ongoing outages. Check the stats for the latest 30 days and a list of the last GitLab CI/CD - Windows Shared Runners (Beta) outages.
Minor · started 3 days ago
License Scanning temporarily disabled
No licenses will be detected unless the license scanning template is explicitly included in your .gitlab-ci.yml file. Our engineering team is working to restore full functionality. Details in this issue: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8593
Minor Resolved · 12 days ago · lasted about 4 hours
There is an ongoing incident with our CI Postgres cluster. Some CI jobs are getting delayed. For more information please see the incident (https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8541)
14 day free trial · No credit card required
Minor Resolved · 27 days ago · lasted about 5 hours
Degraded performance on Gitlab.com
Users may encounter degraded performance or intermittent errors on GitLab.com. We are currently investigating. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8471
Minor Resolved · 3 months ago · lasted 31 minutes
Elevated error rates on CI Runner
Starting at 15:20 UTC, we started having elevated error rates for runners trying to write to job logs or status. The error rates have since stabilized and our engineers continue to investigate the root cause. For more details, please check https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8204
Minor Resolved · 3 months ago · lasted about 3 hours
High Error Rate on Select GitLab.com
We are currently seeing a high rate of errors on GitLab.com. Our infrastructure team is currently investigating. More information can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8201
Major Resolved · 4 months ago · lasted about 1 hour
GitLab.com is unavailable
We have detected a problem related to GitLab.com services and are actively investigating. More details to follow.
Minor Resolved · 7 months ago · lasted 12 minutes
GitLab.com slow to respond
We are noticing some slow response issues with GitLab.com.
Yser-reported problems for GitLab CI/CD - Windows Shared Runners (Beta) in the last 12 hours. It's a collection of user reports from different sources.
From planning to production, bring teams together in one application. Ship secure code more efficiently to deliver value faster.
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 trial
No credit card required · Cancel anytime · 2509 services available
Quickly identify external outages that impact your business. We are monitoring more than 2500 services in real time.
Your team on top of problems
IsDown aggregates the information from the status pages of all your services, making it easy to monitor the health of all your services in one place. Say goodbye to managing each status page individually - our service simplifies the process.
No more wasting time. Uptime monitoring in real time
Say goodbye to wasting time trying to diagnose issues with your services - our 24/7 monitoring service does the work for you. We'll notify you if there is an incident, so you can focus on other tasks.
Receive alerts in your preferred channels
Our outage monitoring keeps you informed, no matter where you are. Get instant notifications in your email, Slack, Teams, or Discord when an outage is detected, so you can take action quickly.
Easily integrate with your current tools and workflows
Enhance your processes with more information using our integration of Zapier, Webhooks, PagerDuty, and Datadog. Stay notified and in control. Upgrade your operations today.
Avoid notifications clutter
Maximize your control with customizable notifications from each service. Filter by components and severity to only receive the most important updates. Streamline your processes and stay informed with our advanced notification features.
Multiple dashboards, shareable with the world
Create one dashboard for each of your teams/clients/projects and monitor only the services that each uses. Have a dedicated dashboard with custom notification settings. Easily make your dashboard public and share it with the world.
Prepare for scheduled maintenances
Never again be caught off guard by unexpected maintenance from your services. A feed of the next scheduled maintenances is available.
Weekly Digest of the services' outages
Every Monday, you'll receive a weekly summary of what happened the previous week as well as the maintenance schedule for the following week.
The data and notifications you need, in the tools you already use.
DevOps & On-Call Teams
You already monitor your internal systems. What about the external services? Monitor the services your business depends on. Don't waste time looking elsewhere when external outages are the cause of issues.
IT Support Teams
Detect external outages before your clients tell you. Anticipate possible issues and make the necessary arrangements. Having proactive communication, builds trust over clients and prevents flow of support tickets.
5 minute setup,
instant value for your team
Start with a trial account that will allow you to try and monitor up to 40 services for 14 days.
There are 2509 services to choose from and you can start monitoring, and we're adding more every week.
You can get notifications by email, Slack, and Discord. You can also use Zapier or Webhooks to build your workflows.
You'll start getting alerts when we detect outages in your external dependencies! No more wasting time looking in the wrong place!
Best practices when managing an outage
There’s never a good time for a service outage. And, from the moment it hits, it starts affecting your stakeholders. Suddenly, essential daily tasks are curtailed while your team enters emergency response mode. However, the surest way to mitigate damages and recover quickly is to follow a set of best practices.
Try it out! How much time you'll save your team, by having the outages information close to them?