Is GitLab down?

Last checked 4m ago
Current status
GitLab is up

No incidents right now.

Get alerts when GitLab breaks →

Free · no credit card

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

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 1 incident in the last 90 days (99.95% 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: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 6,000+ providers
GitLab uptime 99.95% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. parsing error in the vulnerability reports
    Resolved 2h 21m
    Started Apr 28, 2026, 11:05 AM UTC · Resolved Apr 28, 2026, 01:27 PM UTC
    WebsiteGoogle Compute Engine
    2 updates · show timeline
    • investigating · Apr 28, 2026, 11:05 AM UTC

      We are currently investigating issues with dependency scanning. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905`.

    • identified · Apr 28, 2026, 12:02 PM UTC

      We've identified cause of the issue and are working on resolving it. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905.

    Latest: We've identified cause of the issue and are working on resolving it. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905.

Outage history

Past 30 days · 1 incident
  • parsing error in the vulnerability reports Resolved
    Started Apr 28, 2026, 11:05 AM UTC · Resolved Apr 28, 2026, 01:27 PM UTC · 2h 21m

See GitLab in your Pingoru dashboard

Monitor GitLab alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add GitLab to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every GitLab incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just GitLab or see every provider at once.

Maintenance calendar

Scheduled GitLab maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every GitLab status change, one inbox

Pingoru watches GitLab's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

GitLab reports on 47 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route GitLab alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming GitLab maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy GitLab services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching GitLab from the same account, with per-user notification preferences for any monitor.

Get notified on GitLab status changes

Pingoru watches GitLab's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring GitLab free

Monitor GitLab along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add GitLab and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track GitLab uptime & incident history

See 90 days of GitLab uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See GitLab uptime history

Frequently asked questions

What is GitLab's uptime?
Over the last 90 days, GitLab reported 99.95% 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 1 incident 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 "parsing error in the vulnerability reports", which started on April 28, 2026 and was resolved on April 28, 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 0.3 reported incident 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.
What does "Up" mean?
All tracked GitLab components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch GitLab's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor GitLab free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →