What is GitLab's uptime?

Over the last 90 days, GitLab reported 97.90% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.gitlab.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see GitLab's uptime history rolling forward in real time.

Has GitLab had outages in 2026?

Yes — GitLab has had 21 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last GitLab outage?

The most recent GitLab incident was "Claude Fable is not available through GitLab.com", which started on June 13, 2026 and was resolved on June 13, 2026. Pingoru captured this directly from https://status.gitlab.com. See the full incident card above for affected components and the update timeline.

How often does GitLab have outages?

Based on the last 90 days, GitLab averages 7.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is GitLab's status page?

GitLab's official status page is https://status.gitlab.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is GitLab down right now?

GitLab is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment GitLab reports a change. Current status is based on 47 tracked services.

How does Pingoru know if GitLab is down?

We read https://status.gitlab.com directly, using GitLab's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.

Where can I get notified when GitLab has an outage?

Create a free Pingoru account and add GitLab as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

GitLab's status page says the service is up, but I'm having issues — what's wrong?

Three common reasons: • A real GitLab incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real GitLab issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official GitLab status?

We use GitLab's own status page at https://status.gitlab.com and cross-reference their homepage (https://gitlab.com). Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

All tracked GitLab components are reporting operational. No incidents are currently affecting service.

Is GitLab down?

Last checked 6m ago

Current status

GitLab is up

No incidents right now.

Get alerts when GitLab breaks → View GitLab outage history →

Free · no credit card

Official status page: https://status.gitlab.com · Polled every 5 minutes · 47 components tracked

GitLab is operational right now. Last checked 6m ago; the most recent incident resolved 13h ago.

Real-time GitLab status, recent outages, and incident history — pulled directly from GitLab's official status page at https://status.gitlab.com every 5 minutes. Pingoru tracks 47 GitLab services and has captured 21 incidents in the last 90 days (97.90% uptime). Get email, Slack, Discord, or webhook alerts the moment GitLab reports a new incident — free for 5 monitors, no credit card.

Users who monitor GitLab also follow these DevOps services:

RubyGems View all 6,000+ providers

GitLab uptime 97.90% uptime · past 90 days

Mon Wed Fri

MarAprMayJun

Less More

Recent outages & incidents

Past 90 days

Claude Fable is not available through GitLab.com

Resolved 4h 2m

Started Jun 13, 2026, 03:53 AM UTC · Resolved Jun 13, 2026, 07:56 AM UTC

GitLab DuoGoogle Compute Engine
Timeline · 7 updates
- monitoring · Jun 13, 2026, 03:53 AM UTC
  
  Claude Fable is not available through GitLab.com. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- monitoring · Jun 13, 2026, 03:53 AM UTC
  
  Claude Fable is not available through GitLab.com. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9
- monitoring · Jun 13, 2026, 04:13 AM UTC
  
  Although Claude Fable is not available on GitLab.com, it still appears in the model selection menu. Customers who are currently using it should manually select a different model. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9
- monitoring · Jun 13, 2026, 04:13 AM UTC
  
  Although Claude Fable is not available on GitLab.com, it still appears in the model selection menu. Customers who are currently using it should manually select a different model. Please see the notice from the upstream provider: https://status.claude.com/incidents/s9w82lp9dcn9
- monitoring · Jun 13, 2026, 07:22 AM UTC
  
  The revert MR to remove the Claude Fable was merged and deployed to production. While the GitLab.com service is back to normal, Fable remains unavailable due to an upstream suspension. Customers need continue to select a different model. We are monitoring the situation closely.
- monitoring · Jun 13, 2026, 07:22 AM UTC
  
  The revert MR to remove the Claude Fable was merged and deployed to production. While the GitLab.com service is back to normal, Fable remains unavailable due to an upstream suspension. Customers need continue to select a different model. We are monitoring the situation closely.
- resolved · Jun 13, 2026, 07:56 AM UTC
  
  GitLab.com is currently operating normally. The issue has been resolved. For more info, please see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22308
Latest: GitLab.com is currently operating normally. The issue has been resolved. For more info, please see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22308
Intermittent 5XX errors accessing in GitLab.com

Resolved 13h 10m

Started Jun 11, 2026, 07:08 AM UTC · Resolved Jun 11, 2026, 08:19 PM UTC

WebsiteGoogle Compute Engine
Timeline · 11 updates
- investigating · Jun 11, 2026, 07:08 AM UTC
  
  We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- investigating · Jun 11, 2026, 07:08 AM UTC
  
  We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.
- investigating · Jun 11, 2026, 07:11 AM UTC
  
  We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.
- investigating · Jun 11, 2026, 07:11 AM UTC
  
  We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.
- investigating · Jun 11, 2026, 07:23 AM UTC
  
  We changed the status title to reflect the intermittent nature of this incident. We'll share another update as soon as we have more information.
- investigating · Jun 11, 2026, 07:23 AM UTC
  
  We changed the status title to reflect the intermittent nature of this incident. We'll share another update as soon as we have more information.
- monitoring · Jun 11, 2026, 08:06 AM UTC
  
  The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently.
- monitoring · Jun 11, 2026, 08:06 AM UTC
  
  The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently.
- monitoring · Jun 11, 2026, 12:16 PM UTC
  
  GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database, and we are continuing to monitor closely.
- monitoring · Jun 11, 2026, 12:16 PM UTC
  
  GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database, and we are continuing to monitor closely.
- resolved · Jun 11, 2026, 08:19 PM UTC
  
  GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database and the issue should be resolved now.
Latest: GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database and the issue should be res…
Credits Dashboard Disruption

Resolved 4h 4m

Started Jun 08, 2026, 09:17 AM UTC · Resolved Jun 08, 2026, 01:22 PM UTC

WebsiteGoogle Compute Engine
Timeline · 5 updates
- investigating · Jun 08, 2026, 09:17 AM UTC
  
  The GitLab.com credit dashboard fails to load, displaying the error message: "An error occurred while fetching data". This issue is under investigation. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- investigating · Jun 08, 2026, 09:17 AM UTC
  
  The GitLab.com credit dashboard fails to load, displaying the error message: "An error occurred while fetching data". This issue is under investigation.
- monitoring · Jun 08, 2026, 12:15 PM UTC
  
  Mitigation has been applied and GitLab Credits dashboards appear to be loading again. We’ll leave affected components marked as Partial Service Disruption as we monitor error rates closely to ensure the service remains stable.
- monitoring · Jun 08, 2026, 12:15 PM UTC
  
  Mitigation has been applied and GitLab Credits dashboards appear to be loading again. We’ll leave affected components marked as Partial Service Disruption as we monitor error rates closely to ensure the service remains stable.
- resolved · Jun 08, 2026, 01:22 PM UTC
  
  GitLab Credits dashboards are operating normally again. The issue has been resolved.
Latest: GitLab Credits dashboards are operating normally again. The issue has been resolved.
Issue with processing CI jobs

Resolved 1h 47m

Started Jun 05, 2026, 11:58 AM UTC · Resolved Jun 05, 2026, 01:46 PM UTC

CI/CDCI/CD - Hosted runners on LinuxGoogle Compute Engine
Timeline · 13 updates
- investigating · Jun 05, 2026, 11:58 AM UTC
  
  We are investigating an issue where CI jobs are not processing. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- investigating · Jun 05, 2026, 11:58 AM UTC
  
  We are investigating an issue where CI jobs are not processing. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- identified · Jun 05, 2026, 12:08 PM UTC
  
  We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- identified · Jun 05, 2026, 12:08 PM UTC
  
  We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- identified · Jun 05, 2026, 12:51 PM UTC
  
  We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- identified · Jun 05, 2026, 12:51 PM UTC
  
  We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- identified · Jun 05, 2026, 12:53 PM UTC
  
  We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- identified · Jun 05, 2026, 12:53 PM UTC
  
  We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- identified · Jun 05, 2026, 01:04 PM UTC
  
  The change has been reverted and we are seeing that error rates are recovering. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- identified · Jun 05, 2026, 01:04 PM UTC
  
  The change has been reverted and we are seeing that error rates are recovering. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- monitoring · Jun 05, 2026, 01:15 PM UTC
  
  Error rates have recovered back to normal levels and we started processing jobs again. We expect that the job queue should be processed over the next 30 minutes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- monitoring · Jun 05, 2026, 01:15 PM UTC
  
  Error rates have recovered back to normal levels and we started processing jobs again. We expect that the job queue should be processed over the next 30 minutes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
- resolved · Jun 05, 2026, 01:46 PM UTC
  
  The job queue is now cleared and we do not expect any further customer impact. This is considered resolved. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256
Latest: The job queue is now cleared and we do not expect any further customer impact. This is considered resolved. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/…
Duo Agent Platform Flows not working for some projects

Resolved 15h 45m

Started Jun 04, 2026, 04:05 PM UTC · Resolved Jun 05, 2026, 07:51 AM UTC

GitLab DuoGoogle Compute Engine
Timeline · 9 updates
- investigating · Jun 04, 2026, 04:05 PM UTC
  
  We are investigating an issue where Duo Agent Platform Flows, including Duo Code Review, are not working on some projects. See issue for more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- investigating · Jun 04, 2026, 04:05 PM UTC
  
  We are investigating an issue where Duo Agent Platform Flows, including Duo Code Review, are not working on some projects. See issue for more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
- identified · Jun 04, 2026, 04:23 PM UTC
  
  We have identified the root cause of the recent Duo Agent Platform Flow failures and are deploying a fix. Customers should begin seeing improvements as the deployment completes. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
- identified · Jun 04, 2026, 04:23 PM UTC
  
  We have identified the root cause of the recent Duo Agent Platform Flow failures and are deploying a fix. Customers should begin seeing improvements as the deployment completes. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
- identified · Jun 04, 2026, 04:52 PM UTC
  
  We have merged a fix for the Duo Agent Platform Flow failures and it is awaiting deployment. Deployment is expected to take several hours. We will share our next update once the deployment is complete. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
- identified · Jun 04, 2026, 04:52 PM UTC
  
  We have merged a fix for the Duo Agent Platform Flow failures and it is awaiting deployment. Deployment is expected to take several hours. We will share our next update once the deployment is complete. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
- monitoring · Jun 05, 2026, 05:37 AM UTC
  
  Error rates have decreased significantly following the fix. We are continuing to monitor the situation. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
- monitoring · Jun 05, 2026, 05:37 AM UTC
  
  Error rates have decreased significantly following the fix. We are continuing to monitor the situation. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
- resolved · Jun 05, 2026, 07:51 AM UTC
  
  This issue has been resolved and error rates have returned to normal. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251
Latest: This issue has been resolved and error rates have returned to normal. For more info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22251

See the full GitLab outage history

16 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse GitLab outage history →

Or sign up free to get alerts when GitLab breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 21 incidents View full outage history →

Claude Fable is not available through GitLab.com Resolved

Started Jun 13, 2026, 03:53 AM UTC · Resolved Jun 13, 2026, 07:56 AM UTC · 4h 2m
Intermittent 5XX errors accessing in GitLab.com Resolved

Started Jun 11, 2026, 07:08 AM UTC · Resolved Jun 11, 2026, 08:19 PM UTC · 13h 10m
Credits Dashboard Disruption Resolved

Started Jun 08, 2026, 09:17 AM UTC · Resolved Jun 08, 2026, 01:22 PM UTC · 4h 4m
Issue with processing CI jobs Resolved

Started Jun 05, 2026, 11:58 AM UTC · Resolved Jun 05, 2026, 01:46 PM UTC · 1h 47m
Duo Agent Platform Flows not working for some projects Resolved

Started Jun 04, 2026, 04:05 PM UTC · Resolved Jun 05, 2026, 07:51 AM UTC · 15h 45m
Problem with Duo Agent Platform Flows Resolved

Started Jun 03, 2026, 02:39 PM UTC · Resolved Jun 03, 2026, 05:53 PM UTC · 3h 13m
Issues with GitLab Duo in merge requests Resolved

Started May 29, 2026, 12:50 PM UTC · Resolved May 29, 2026, 11:41 PM UTC · 10h 50m
Git operation failed Resolved

Started May 27, 2026, 07:31 AM UTC · Resolved May 27, 2026, 09:55 AM UTC · 2h 23m