What is GitLab's uptime?

Over the last 90 days, GitLab reported 94.07% 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 42 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 "Upcoming maintenance for the Customers Portal", which started on October 31, 2026 and was resolved on October 31, 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 14.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 1m 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: status.gitlab.com
Checked every 5 minutes
47 components tracked

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

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

Users who monitor GitLab also follow these DevOps services:

RubyGems View all 8,000+ providers

GitLab uptime 94.07% uptime · past 90 days

Mon Wed Fri

AugSepOct

Less More

Recent outages & incidents

Past 90 days

General slowness on Gitlab.com

Resolved 31m

Started Oct 23, 2026, 04:32 PM UTC · Resolved Oct 23, 2026, 05:04 PM UTC

WebsiteGit OperationsGitLab agent server for Kubernetes — Google Compute Engine
Timeline · 3 updates
- monitoring · Oct 23, 2026, 04:32 PM UTC
  
  We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23320 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 · Oct 23, 2026, 04:32 PM UTC
  
  We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23320
- resolved · Oct 23, 2026, 05:04 PM UTC
  
  We have resolved the issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are continuing to monitor the platform. The impact may have included partial degradation to the web UI and Git operations.
Latest: We have resolved the issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are continuing to monitor the platform. The impact may have included partial…
404s on customers.gitlab.com

Resolved 3h 24m

Started Oct 20, 2026, 09:56 PM UTC · Resolved Oct 21, 2026, 01:21 AM UTC

GitLab Customers PortalGitLab agent server for Kubernetes — Google Compute Engine
Timeline · 9 updates
- investigating · Oct 20, 2026, 09:56 PM UTC
  
  We've investigating 404s on the customers panel. We'll update as we learn more 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 · Oct 20, 2026, 09:56 PM UTC
  
  We've investigating 404s on the customers panel. We'll update as we learn more
- investigating · Oct 20, 2026, 10:47 PM UTC
  
  We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.
- investigating · Oct 20, 2026, 10:47 PM UTC
  
  We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.
- investigating · Oct 20, 2026, 11:15 PM UTC
  
  We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.
- investigating · Oct 20, 2026, 11:15 PM UTC
  
  We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.
- monitoring · Oct 20, 2026, 11:51 PM UTC
  
  The Customers Portal is loading normally again, and we are no longer observing the intermittent 404 errors affecting sign-in and page loading. A redeployment has completed successfully, and we are monitoring the service for any recurrence before resolving the incident.
- monitoring · Oct 20, 2026, 11:51 PM UTC
  
  The Customers Portal is loading normally again, and we are no longer observing the intermittent 404 errors affecting sign-in and page loading. A redeployment has completed successfully, and we are monitoring the service for any recurrence before resolving the incident.
- resolved · Oct 21, 2026, 01:21 AM UTC
  
  The monitoring period has concluded, and the incident has been confirmed resolved. See the issue for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23297
Latest: The monitoring period has concluded, and the incident has been confirmed resolved. See the issue for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23…
Intermittent 500 on GitLab.com

Resolved 2h 46m

Started Oct 20, 2026, 07:08 AM UTC · Resolved Oct 20, 2026, 09:55 AM UTC

WebsiteGitLab agent server for Kubernetes — Google Compute Engine
Timeline · 6 updates
- investigating · Oct 20, 2026, 07:08 AM UTC
  
  We're investigating intermittent HTTP 503 errors when opening project pages. At this time, this issue only occurs in specific projects. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288 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 · Oct 20, 2026, 07:08 AM UTC
  
  We're investigating intermittent HTTP 503 errors when opening project pages. At this time, this issue only occurs in specific projects. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288
- monitoring · Oct 20, 2026, 07:37 AM UTC
  
  This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288
- monitoring · Oct 20, 2026, 07:37 AM UTC
  
  This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288
- monitoring · Oct 20, 2026, 07:37 AM UTC
  
  This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288
- resolved · Oct 20, 2026, 09:55 AM UTC
  
  We have not seen any more HTTP 500 errors for GitLab Secrets Manager since the mitigation was applied. This incident is now resolved. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288
Latest: We have not seen any more HTTP 500 errors for GitLab Secrets Manager since the mitigation was applied. This incident is now resolved. Details: https://gitlab.com/gitlab-com/gl-infr…
503s on GitLab.com

Resolved 1h 13m

Started Oct 16, 2026, 04:10 PM UTC · Resolved Oct 16, 2026, 05:24 PM UTC

WebsiteAPIGit OperationsPackage RegistryContainer RegistryGitLab PagesCI/CDCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on WindowsCI/CD - Hosted runners on macOS
Timeline · 11 updates
- investigating · Oct 16, 2026, 04:10 PM UTC
  
  We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details. 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 · Oct 16, 2026, 04:10 PM UTC
  
  We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.
- investigating · Oct 16, 2026, 04:25 PM UTC
  
  We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- investigating · Oct 16, 2026, 04:25 PM UTC
  
  We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- identified · Oct 16, 2026, 04:40 PM UTC
  
  We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- identified · Oct 16, 2026, 04:40 PM UTC
  
  We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- identified · Oct 16, 2026, 04:52 PM UTC
  
  Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- identified · Oct 16, 2026, 04:52 PM UTC
  
  Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- monitoring · Oct 16, 2026, 05:05 PM UTC
  
  We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- monitoring · Oct 16, 2026, 05:05 PM UTC
  
  We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- resolved · Oct 16, 2026, 05:24 PM UTC
  
  The issue is fully resolved and operations on GitLab.com and GitLab Duo are operating normally. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
Latest: The issue is fully resolved and operations on GitLab.com and GitLab Duo are operating normally. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/2326…
GitLab.com CI/CD Incident

Resolved 1h 48m

Started Oct 16, 2026, 11:33 AM UTC · Resolved Oct 16, 2026, 01:21 PM UTC

CI/CDGitLab agent server for Kubernetes — Google Compute Engine
Timeline · 5 updates
- investigating · Oct 16, 2026, 11:33 AM UTC
  
  We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error, and the UI may be slow: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow. 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 · Oct 16, 2026, 11:33 AM UTC
  
  We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow.
- monitoring · Oct 16, 2026, 12:28 PM UTC
  
  We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com customers. We're monitoring recovery while working on a longer-term solution.
- monitoring · Oct 16, 2026, 12:28 PM UTC
  
  We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com customers. We're monitoring recovery while working on a longer-term solution.
- resolved · Oct 16, 2026, 01:21 PM UTC
  
  The issue causing CI/CD failures and UI slowness for a limited number of GitLab.com customers has been resolved. Thank you for your patience.
Latest: The issue causing CI/CD failures and UI slowness for a limited number of GitLab.com customers has been resolved. Thank you for your patience.

See the full GitLab outage history

36 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

Incident record

Since April 2026 · Status.io · 47 components checked every 5 minutes

74incidents recorded

74last 12 months

41last 90 days

8 hourstypical duration, 12 months

The longest incident in the last year, Background processing delays on May 7, 2026, ran for 4 days. 1 maintenance window announced in the same period.

Most affected components, last 12 months

GitLab agent server for Kubernetes — Google Compute Engine74
Website30
CI/CD29
Git Operations17
GitLab Duo16

Latest incidents

General slowness on Gitlab.com October 23, 2026 · 31 minutes · degraded service
We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the…
404s on customers.gitlab.com October 20, 2026 · 3 hours · major outage
We've investigating 404s on the customers panel. We'll update as we learn more Back to current status Status History Subscribe to receive status updates by…
Intermittent 500 on GitLab.com October 20, 2026 · 3 hours · degraded service
We're investigating intermittent HTTP 503 errors when opening project pages. At this time, this issue only occurs in specific projects. More details at…

Outage history

Past 90 days · 41 incidents View full outage history →

General slowness on Gitlab.com Resolved

Started Oct 23, 2026, 04:32 PM UTC · Resolved Oct 23, 2026, 05:04 PM UTC · 31m
404s on customers.gitlab.com Resolved

Started Oct 20, 2026, 09:56 PM UTC · Resolved Oct 21, 2026, 01:21 AM UTC · 3h 24m
Intermittent 500 on GitLab.com Resolved

Started Oct 20, 2026, 07:08 AM UTC · Resolved Oct 20, 2026, 09:55 AM UTC · 2h 46m
503s on GitLab.com Resolved

Started Oct 16, 2026, 04:10 PM UTC · Resolved Oct 16, 2026, 05:24 PM UTC · 1h 13m
GitLab.com CI/CD Incident Resolved

Started Oct 16, 2026, 11:33 AM UTC · Resolved Oct 16, 2026, 01:21 PM UTC · 1h 48m
CI/CD Job Delays on GitLab.com Resolved

Started Oct 15, 2026, 04:18 PM UTC · Resolved Oct 15, 2026, 07:50 PM UTC · 3h 32m
Error loading GitLab.com and customers.gitlab.com Resolved

Started Oct 15, 2026, 04:43 AM UTC · Resolved Oct 15, 2026, 09:02 AM UTC · 4h 18m
GitLab.com CI/CD pipelines delayed or not starting Resolved

Started Oct 14, 2026, 02:33 PM UTC · Resolved Oct 14, 2026, 06:30 PM UTC · 3h 57m