Is GitLab Down? Check the current GitLab status

GitLab is operational

Updated

GitLab not working for you?
IsDown Logo The best way to monitor all your vendor outages

Need to know when vendors go down? You’re in the right place

3,250+ third-party services monitored in real-time
Get custom alerts via Slack, Teams, Datadog, etc.
Public or private status pages available
14-day free trial · No credit card required
Trusted by 500+ teams worldwide

Current GitLab official ongoing incidents

No ongoing outages reported in GitLab's status page

IsDown pulls data from GitLab's status page every few minutes. Refresh the page every few minutes to see if there are any updates.

GitLab issues reported by users in the last 24 hours

This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.

Latest user comments about GitLab problems

  • A

    Alex

    10 days ago

    Can't push or pull via SSH protocol, port 22: Connection closed by 172.65.251.78 port 22 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

  • E

    Ezra

    24 days ago

    API None of my pipelines run I am hit a message in the UI saying: "Pipeline cannot be run. Something went wrong on our end. Please try again."

  • J

    Jelle

    24 days ago

    Not able to push any changes. "send-pack: unexpected disconnect while reading sideband packet Connection to gitlab.com closed by remote host. fatal: the remote end hung up unexpectedly"

  • A

    Amiri

    about 2 months ago

    Container Registry gitlab error: ERROR: Job failed: failed to pull image "registry.gitlab.com/gitlab-org/terraform-images/releases/1.5:v1.7.1" with specified policies [always]: Error response from daemon: Get "https://registry.gitlab.com/v2/": dial tcp 35.227.35.254:443: connect: network is unreachable (manager.go:...

  • N

    Nima

    3 months ago

    To https://gitlab.com/dk-external-project/backend/dk-gold_project.git ! [remote rejected] temp-branch -> temp-branch (pre-receive hook declined) error: failed to push some refs to 'https://gitlab.com/dk-external-project/backend/dk-gold_project.git'

  • M

    Michael

    4 months ago

    I pushed code to gitlab, but I can see it on gitlab

  • M

    Marcelo

    4 months ago

    I cant push my commits, all services are down

  • H

    Hariharan

    4 months ago

    503 An internal server error occured.

  • G

    guy

    4 months ago

    503 An internal server error occured.

  • J

    Jessio

    4 months ago

    503 An internal server error occured.

  • T

    Taha

    6 months ago

    request to https://gitlab.com/oauth/token failed, reason: getaddrinfo ENOTFOUND gitlab.com

  • M

    mohamed

    8 months ago

    i get rpc error: code = Unknown desc = authorization failed if i use deploy tokens

  • P

    Pradeep

    8 months ago

    Git is not able to connect. Not able to push and pull

  • M

    Michail

    8 months ago

    Merge requests don't work.

  • M

    malak

    8 months ago

    all merge requests are hanging and cant create a new merged or close old ones and the merges are disappearing from the list

GitLab outage history

IsDown has tracked 201 incidents since started monitoring GitLab status in March 2022.

  • Dec 19 2024

    7 days ago · lasted about 7 hours

    We are investigating reports of intermittent errors across GitLab.com and GitLab Pages. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19033 More details

  • Dec 18 2024

    8 days ago · lasted 43 minutes

    We're experiencing saturation in our Redis cluster. The investigation is still ongoing. Users might get 500 errors intermittently. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19025 More details

  • Dec 16 2024

    We have received some reports of requests timing out for IP addresses originating in Salt Lake City, Utah. We are working with a third party vendor to identify the issue. Details to follow in: https://gitlab.com/gitlab-com/gl-infra/production/-/is... More details

  • Mar 2022 ...
    IsDown started monitoring GitLab status

    We've tracked and collected 201 incidents since started monitoring GitLab status

Sign up and check all outage history

GitLab outages in the last 30 days

Number of Incidents

11 issues

Last incident

7 days ago

Need to know when vendors go down? You’re in the right place

Get instant alerts when your cloud vendors experience downtime. Create an internal status page to keep your team in the loop and minimize the impact of service disruptions.

Start Free Trial 14-day free trial · No credit card required · 3200+ cloud vendors available

Check the status of GitLab alternatives & related services

GitHub OK
9 incidents in the last 30 days
Compare GitLab vs. GitHub
1 incidents in the last 30 days
Compare GitLab vs. Bitbucket

Stay informed about GitLab status changes

IsDown offers an easy way to monitor GitLab with maximum flexibility

Major Outages Notifications

IsDown monitors GitLab for major outages. A major outage is when GitLab experiences a critical issue that severely affects one or more services/regions. When GitLab marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.

Minor Outages Notifications

IsDown monitors GitLab status page for minor outages. A minor outage is when GitLab experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.

Outage Details

IsDown collects all information from the outages published in GitLab status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.

Component Filtering

IsDown monitors GitLab and all their 17 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.

Early Outage Indicators

GitLab and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.

Frequently Asked Questions

Is GitLab down today?

GitLab isn't down. You can check GitLab status and incident details on the top of the page. IsDown continuously monitors GitLab official status page every few minutes. In the last 24 hours, there were 0 outages reported.

What is the current GitLab status?

GitLab is currently operational. You can check GitLab status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.

Is there a GitLab outage now?

No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.

Is GitLab slow today?

Currently there's no report of GitLab being slow. Check on the top of the page if there are any reported problems by other users.

How are GitLab outages detected?

IsDown monitors the GitLab official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.

When was the last GitLab outage?

GitLab last outage was on December 19, 2024 with the title "Intermittent errors across GitLab.com"

GitLab not working for you? How do I know if GitLab is down?
How can I check GitLab status and outages?
Why use IsDown to monitor GitLab instead of the official status page?

Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor GitLab and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.

How IsDown compares to DownDetector?

IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.

Get GitLab outage notifications where you need them the most

The data and notifications you need, in the tools you already use.

Latest Articles from our Blog

See all the blog articles

Setup in 5 minutes or less

How much time you'll save your team, by having the outages information close to them?

14-day free trial · No credit card required · Cancel anytime