GitLab Status - Is GitLab Down?
GitLab is having a minor outage
Updated
GitLab is having a minor outage
Updated
We are aware that the current GPG public key for gitlab-runner packages has expired, we are working to refresh the key.
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.
Ricardo
503 Service Temporarily Unavailable
Emily
I am finding that after logging in, I am unable to access my account or the website at all. I am told it is not available
Nikhil
It shows the site can't be reaced
Ankit
HTTP 502: Waiting for GitLab to boot It can take up to a few minutes for GitLab to boot completely. This page will automatically reload every 5 seconds.
Alex
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.
Ezra
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."
Jelle
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"
Amiri
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:...
Nima
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'
Michael
I pushed code to gitlab, but I can see it on gitlab
Marcelo
I cant push my commits, all services are down
Hariharan
503 An internal server error occured.
guy
503 An internal server error occured.
Jessio
503 An internal server error occured.
Taha
request to https://gitlab.com/oauth/token failed, reason: getaddrinfo ENOTFOUND gitlab.com
mohamed
i get rpc error: code = Unknown desc = authorization failed if i use deploy tokens
Pradeep
Git is not able to connect. Not able to push and pull
Michail
Merge requests don't work.
malak
all merge requests are hanging and cant create a new merged or close old ones and the merges are disappearing from the list
Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.
IsDown has tracked 231 incidents since started monitoring GitLab status in March 2022.
12 days ago · lasted about 6 hours
We are investigating an issue causing users to receive 500 or 502 responses from API calls and CI jobs. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19675. More details
17 days ago · lasted about 3 hours
Customers might experience errors when purchasing add-ons in the customer portal. We have identified the root cause, and are waiting for an MR to revert the issue. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/19650 More details
We've tracked and collected 231 incidents since started monitoring GitLab status
Get notified on Slack, Datadog, Incident.io and more
Monitor all vendors status in one place
Create private or public status pages
Track uptime over time in all your vendors
Number of Incidents
5 issues
Last incident
1 days ago
AWS
Cloudflare
Azure
GitHub
Google Cloud
Slack
Google Workspace
Zoom
Datadog US1
Figma
HubSpot
Confluence
Jira Software
Microsoft 365
Salesforce
Why teams choose IsDown:
14-day free trial • No credit card required
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.
GitLab is 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.
GitLab seems to be having problems. 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.
Yes, there is an ongoing outage. You can check the details on the top of the page.
Yes, GitLab might be slow has there's an ongoing outage. You can check the details on the top of the page.
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.
GitLab last outage was on April 27, 2025 with the title "gitlab-runner package repository GPG public key expired"
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.
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.
IsDown offers an easy way to monitor GitLab with maximum flexibility
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.
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.
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.
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.
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.
“Very happy with isDown. Setting up and managing the monitoring is straightforward. The customer support team has been excellent, always quick to answer questions and provide assistance.
I definitely recommend IsDown.”
The data and notifications you need, in the tools you already use.
14-day free trial · No credit card required · No code required
