What is GitLab's uptime?

Over the last 90 days, GitLab reported 97.64% 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 30 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 "Issue with background jobs", which started on August 6, 2026 and was resolved on August 6, 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 10.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 8m 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 8m ago; the most recent incident resolved 5d 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 30 incidents in the last 90 days (97.64% 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.64% uptime · past 90 days

Mon Wed Fri

MayJunJulAug

Less More

Recent outages & incidents

Past 90 days

Issue with background jobs

Resolved 2h 20m

Started Aug 06, 2026, 02:01 PM UTC · Resolved Aug 06, 2026, 04:22 PM UTC

WebsiteAPIGoogle Compute Engine
Timeline · 5 updates
- investigating · Aug 06, 2026, 02:01 PM UTC
  
  We are investigating an issue affecting background jobs, including webhook delivery and pipelines. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661 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 · Aug 06, 2026, 02:01 PM UTC
  
  We are investigating an issue affecting background jobs, including webhook delivery and pipelines. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661
- identified · Aug 06, 2026, 02:26 PM UTC
  
  We have identified the cause of the issue and we are taking action to mitigate customer impact. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661
- identified · Aug 06, 2026, 02:26 PM UTC
  
  We have identified the cause of the issue and we are taking action to mitigate customer impact. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22661
- resolved · Aug 06, 2026, 04:22 PM UTC
  
  We're seeing consistent background job and webhook delivery. The issue is now resolved.
Latest: We're seeing consistent background job and webhook delivery. The issue is now resolved.
Issues with pipelines

Resolved 1h 33m

Started Aug 05, 2026, 10:13 PM UTC · Resolved Aug 05, 2026, 11:47 PM UTC

CI/CDGoogle Compute Engine
Timeline · 7 updates
- investigating · Aug 05, 2026, 10:13 PM UTC
  
  We're investigating reports of pipelines failing and becoming stuck. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654. 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 · Aug 05, 2026, 10:13 PM UTC
  
  We're investigating reports of pipelines failing and becoming stuck. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
- investigating · Aug 05, 2026, 10:39 PM UTC
  
  We've disabled a worker, which should let the job queue begin recovering while we continue investigating the root cause. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
- investigating · Aug 05, 2026, 10:39 PM UTC
  
  We've disabled a worker, which should let the job queue begin recovering while we continue investigating the root cause. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
- identified · Aug 05, 2026, 11:26 PM UTC
  
  We've identified a likely root cause, and the job queue has remained healthy. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
- identified · Aug 05, 2026, 11:26 PM UTC
  
  We've identified a likely root cause, and the job queue has remained healthy. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
- resolved · Aug 05, 2026, 11:47 PM UTC
  
  We've applied mitigations that have stabilized the job queue. The issue is now resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
Latest: We've applied mitigations that have stabilized the job queue. The issue is now resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
Issues with webhook deliveries

Resolved 22h 36m

Started Aug 04, 2026, 04:42 PM UTC · Resolved Aug 05, 2026, 03:19 PM UTC

WebsiteAPIGoogle Compute Engine
Timeline · 11 updates
- investigating · Aug 04, 2026, 04:42 PM UTC
  
  We are investigating reports of webhook deliveries from GitLab.com originating from IP addresses outside our documented ranges. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637. 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 · Aug 04, 2026, 04:42 PM UTC
  
  We are investigating reports of webhook deliveries from GitLab.com originating from IP addresses outside our documented ranges. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.
- investigating · Aug 04, 2026, 06:49 PM UTC
  
  Our investigation is ongoing. We will provide another update by 21:00 UTC.
- investigating · Aug 04, 2026, 06:49 PM UTC
  
  Our investigation is ongoing. We will provide another update by 21:00 UTC.
- identified · Aug 04, 2026, 09:07 PM UTC
  
  We've traced the issue to a recent network change and are preparing a fix. Another update will be provided by 23:00 UTC.
- identified · Aug 04, 2026, 09:07 PM UTC
  
  We've traced the issue to a recent network change and are preparing a fix. Another update will be provided by 23:00 UTC.
- identified · Aug 04, 2026, 11:14 PM UTC
  
  Deployment of the fix is progressing steadily. Another update will be provided once deployed. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.
- identified · Aug 04, 2026, 11:14 PM UTC
  
  Deployment of the fix is progressing steadily. Another update will be provided once deployed. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.
- monitoring · Aug 05, 2026, 03:26 AM UTC
  
  A fix has been deployed and checks have confirmed that unexpected IP addresses are no longer being used.
- monitoring · Aug 05, 2026, 03:26 AM UTC
  
  A fix has been deployed and checks have confirmed that unexpected IP addresses are no longer being used.
- resolved · Aug 05, 2026, 03:19 PM UTC
  
  Webhook delivery failures have subsided in logs, and customer reports indicate no further errors. This incident is considered resolved.
Latest: Webhook delivery failures have subsided in logs, and customer reports indicate no further errors. This incident is considered resolved.
Issue with Duo Code Review Flows

Resolved 3h 57m

Started Aug 04, 2026, 01:56 PM UTC · Resolved Aug 04, 2026, 05:54 PM UTC

GitLab DuoGoogle Compute Engine
Timeline · 5 updates
- investigating · Aug 04, 2026, 01:56 PM UTC
  
  We are investigating an issue which may be affecting Duo Code Review Flows. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633 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 · Aug 04, 2026, 01:56 PM UTC
  
  We are investigating an issue which may be affecting Duo Code Review Flows. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633
- identified · Aug 04, 2026, 04:30 PM UTC
  
  We've identified the cause of the issue and have temporarily reverted the default Agentic Chat model to Sonnet 4.6 while we continue to investigate. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633.
- identified · Aug 04, 2026, 04:30 PM UTC
  
  We've identified the cause of the issue and have temporarily reverted the default Agentic Chat model to Sonnet 4.6 while we continue to investigate. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22633.
- resolved · Aug 04, 2026, 05:54 PM UTC
  
  Duo Code Review sessions on GitLab.com have returned to normal operation. This issue is now resolved.
Latest: Duo Code Review sessions on GitLab.com have returned to normal operation. This issue is now resolved.
Problems related to git operations

Resolved 9h 35m

Started Aug 03, 2026, 02:31 PM UTC · Resolved Aug 04, 2026, 12:07 AM UTC

WebsiteGit OperationsGoogle Compute Engine
Timeline · 9 updates
- investigating · Aug 03, 2026, 02:31 PM UTC
  
  The team is investigating an issue related to a Gitaly node. Customers may experience errors or slowness when performing git operations. For more info see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625 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 · Aug 03, 2026, 02:31 PM UTC
  
  The team is investigating an issue related to a Gitaly node. Customers may experience errors or slowness when performing git operations. For more info see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- investigating · Aug 03, 2026, 02:59 PM UTC
  
  Impact is limited to projects on a single Gitaly node. The team is currently focused on relieving pressure from the overloaded Gitaly node to mitigate impact in the affected projects. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- investigating · Aug 03, 2026, 02:59 PM UTC
  
  Impact is limited to projects on a single Gitaly node. The team is currently focused on relieving pressure from the overloaded Gitaly node to mitigate impact in the affected projects. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- investigating · Aug 03, 2026, 03:57 PM UTC
  
  The team is still working on actions to mitigate impact from the affected Gitaly node. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- investigating · Aug 03, 2026, 03:57 PM UTC
  
  The team is still working on actions to mitigate impact from the affected Gitaly node. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625
- monitoring · Aug 03, 2026, 05:25 PM UTC
  
  Restarting the affected Gitaly node relieved pressure on it, and error rates have dropped significantly. We're monitoring for continued stability. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.
- monitoring · Aug 03, 2026, 05:25 PM UTC
  
  Restarting the affected Gitaly node relieved pressure on it, and error rates have dropped significantly. We're monitoring for continued stability. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.
- resolved · Aug 04, 2026, 12:07 AM UTC
  
  After a period of monitoring we have seen continued Gitaly stability and consider the incident resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.
Latest: After a period of monitoring we have seen continued Gitaly stability and consider the incident resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/2…

See the full GitLab outage history

25 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 · 30 incidents View full outage history →

Issue with background jobs Resolved

Started Aug 06, 2026, 02:01 PM UTC · Resolved Aug 06, 2026, 04:22 PM UTC · 2h 20m
Issues with pipelines Resolved

Started Aug 05, 2026, 10:13 PM UTC · Resolved Aug 05, 2026, 11:47 PM UTC · 1h 33m
Issues with webhook deliveries Resolved

Started Aug 04, 2026, 04:42 PM UTC · Resolved Aug 05, 2026, 03:19 PM UTC · 22h 36m
Issue with Duo Code Review Flows Resolved

Started Aug 04, 2026, 01:56 PM UTC · Resolved Aug 04, 2026, 05:54 PM UTC · 3h 57m
Problems related to git operations Resolved

Started Aug 03, 2026, 02:31 PM UTC · Resolved Aug 04, 2026, 12:07 AM UTC · 9h 35m
Elevated error rates on GitLab.com Resolved

Started Jul 27, 2026, 08:09 PM UTC · Resolved Jul 27, 2026, 09:11 PM UTC · 1h 1m
Possible Issues Signing into GitLab.com Resolved

Started Jul 22, 2026, 09:47 PM UTC · Resolved Jul 24, 2026, 03:50 AM UTC · 1d 6h
Elevated Errors Affecting GitLab Duo Custom Agents Resolved

Started Jul 17, 2026, 04:10 PM UTC · Resolved Jul 17, 2026, 05:36 PM UTC · 1h 25m