GitLab not working? Live outage status & reports
No reports in the last 24 hours.
GitLab current status
No recent reports
0 reports in the last 24 hours.
This does not confirm that GitLab is working.
Official website check: about.gitlab.com is reachable (HTTP 200) · 239 ms · measured (8 minutes ago) This does not confirm the app or sign-in.
Status calculated automatically from user reports (unofficial) — How it works? · Checked at
Having problems?
Help others by reporting if GitLab isn't working for you.
Is it just you? Pick your problem
support.gitlab.com: support.gitlab.com
Official status status.gitlab.com GitLab.com and its associated services, such as the website, API, Git operations, CI/CD hosted runners, registries, GitLab Pages, GitLab Duo, the Customers Portal and the docs and forum sites. It does not cover GitLab Dedicated, which uses support.gitlab.com, or your own Self-Managed instance.
📈 24h trend
0 reportsHours in UTC
🗺️ Where GitLab is having problems
live0 reports (24h)
No active reports right now.
When GitLab.com is down
Official checks and support optionsGitLab.com is down or not loading
Scope: GitLab.com and its associated services
Check the GitLab status page first: GitLab posts GitLab.com performance problems and service interruptions there.
- Open status.gitlab.com.
- Find the part of GitLab.com you use, such as the website, API, Git operations or CI/CD runners, and check its status.
- If an incident is posted, follow its updates on that page. GitLab's infrastructure team is on call 24/7 for GitLab.com.
GitLab is unusable for your whole organization (Premium or Ultimate)
When: You have a Premium or Ultimate plan and GitLab is down, shows errors on every page, or nobody in your organization can sign in
What it means: GitLab treats this as an emergency, with an engineer on call 24 hours a day, 7 days a week. A single user who cannot sign in is not an emergency.
- Open an emergency ticket with GitLab emergency support form (Global Support).
- If you have a US Government subscription, use US Government emergency support form instead.
- Include screenshots or logs in your first submission. If an open ticket has become an emergency, include its ticket number.
No incident is shown, or you use GitLab Dedicated
When: Your problem is not linked to an active GitLab.com incident, or you have an interruption on GitLab Dedicated
- Sign in at support.gitlab.com and submit a request.
Sign-in, account and billing
Official instructionsLocked out of your account by two-factor authentication
Scope: GitLab accounts; the support reset applies only to accounts with a GitLab.com subscription
Sign in with one of the recovery codes GitLab gave you when you set up two-factor authentication (2FA).
- On the GitLab.com sign-in page, enter your username or email, and password.
- On the two-factor verification screen, select Recover your account.
- On the Enter account recovery code screen, enter a recovery code, then select Verify code.
- Each code works once. Your other recovery codes stay valid.
You have no recovery codes but added an SSH key
When: You still have the private SSH key that matches the public key on your GitLab account
What it means: You can create new recovery codes over SSH. This does not work with gitlab-sshd. Your previous recovery codes stop working.
- In the terminal, check that the SSH agent is running on your device.
- macOS and Linux: run eval "$(ssh-agent -s)"
- Windows: in PowerShell, run Set-Service -Name ssh-agent -StartupType Automatic; Start-Service ssh-agent
- Load your private key into the SSH agent. macOS and Linux: ssh-add <path to private SSH key file>
- Open an SSH connection: ssh git@gitlab.com 2fa_recovery_codes (on GitLab Self-Managed, replace gitlab.com with your server hostname).
- At the confirmation message, enter yes.
- Save the new recovery codes. Your previous codes no longer work.
- Sign in with one of the new codes, using the main steps above.
- After signing in, set up 2FA with a new device straight away.
SSH says Permission denied (publickey)
When: You get this error while creating recovery codes over SSH
What it means: This happens when your SSH key is not stored at the default file path.
- Point SSH to your key's folder with ssh-agent: Use SSH keys in another directory (GitLab Docs).
Your authenticator app has its own backup
When: You turned on your authenticator app's backup before losing your device
What it means: GitLab Support cannot help with recovery in third-party authenticator apps.
- Sign in to your authenticator app on a new device to restore your codes.
Nothing works and you have a GitLab.com subscription
When: The recovery options above failed and your account has a paid GitLab.com subscription (Premium or Ultimate)
What it means: You can ask GitLab Support to disable 2FA on your account.
- Go to support.gitlab.com.
- Select Submit a Ticket.
- Sign in with your GitLab Support account. It is separate from your GitLab account and is not affected by your 2FA problem.
- In the issue dropdown list, select GitLab.com user accounts and login issues.
- Complete the fields in the support form.
- Select Submit.
- Once you are back in, turn 2FA on again as soon as possible.
Nothing works and you are on the Free plan
When: The recovery options above failed and your account is Free
What it means: GitLab Support cannot reset 2FA for Free accounts. If you cannot recover your 2FA method, you are permanently locked out and must create a new account.
You are an enterprise user
When: Your account is managed by your organization's top-level group on a paid plan
- Ask the Owner of your top-level group: they can disable 2FA for enterprise users.
You can still sign in but your recovery codes are lost or used up
When: You still have access to your account
What it means: Create new recovery codes now. Older codes stop working, so save the new ones.
- In the upper-right corner, select your avatar.
- Select Edit profile.
- In the left sidebar, select Access > Password and authentication.
- In the Recovery codes section, select Regenerate recovery codes.
- In the dialog, enter your current password and select Regenerate recovery codes.
- Save the new codes.
Official instructionsVerification code not received or rejected
Scope: GitLab accounts on GitLab.com, Self-Managed and Dedicated
Give the email code a minute and check your spam folder before you ask for a new one.
- Wait a minute for the email, then check your spam folder. On GitLab.com, codes come from gitlab@mg.gitlab.com.
- If the code does not arrive or has expired, select Resend code on the sign-in screen.
- Wait for each email before asking again: each resend creates a new code and cancels the previous one.
You cannot access your email address
When: You no longer have access to your primary email address
- Send the code to another email address linked to your account.
- If you set up SSO before, sign in with SSO instead of your username and password.
- If you are a GitLab.com enterprise user, ask your group owner to change your email address.
- On GitLab Self-Managed, contact your GitLab administrator.
- If none of these apply, contact GitLab Support at support.gitlab.com.
Your authenticator code shows invalid pin code
When: GitLab rejects the code from your authenticator app
What it means: The clock on the device that makes your codes may be out of sync with GitLab. Turn on automatic time on that device.
- Android: go to Settings > System > Date & time.
- Turn on Set time automatically. If it is already on, turn it off, wait a few seconds, and turn it on again.
You lost the device that makes your codes
When: Your phone or authenticator is lost or reset
What it means: Use your recovery codes as described in Locked out of your account by two-factor authentication.
Official instructionsGit says HTTP Basic: Access denied
Scope: Git, container registry and dependency proxy requests over HTTP(S)
Use a personal access token instead of your password: GitLab refuses your password when 2FA is on or required, which is the case on GitLab.com.
- Create a personal access tokens (GitLab Docs) with the right scopes.
- For Git over HTTP(S), give it read_repository or write_repository.
- For the GitLab container registry, give it read_registry or write_registry.
- For the dependency proxy, give it read_registry and write_registry.
- Use the token in place of your password.
You use a fine-grained personal access token
When: Your token is fine-grained rather than legacy
What it means: The scopes above apply to legacy tokens; fine-grained tokens use resources and permissions instead. You cannot push container images with a fine-grained token.
Other ways to sign in to Git
When: You do not want to use a personal access token
- If LDAP is set up, use your LDAP password.
- Or use an OAuth credential helpers (GitLab Docs).
Official checks and support optionsBilling, subscription or license problem
Scope: GitLab subscriptions, licenses, payments and GitLab.com compute minutes
Open a billing ticket with GitLab Support: it answers billing, subscription and license questions on every plan, including Free and trials.
- Open Support ticket: Subscription, License or Customers Portal Problems.
- Expect a reply within 8 hours on business days (24x5).
You want to change your plan, payments or seats
When: You manage a subscription yourself
- Sign in to the GitLab Customers Portal with your GitLab.com account.
- To upgrade, choose the plan that suits you.
- To add seats, add them there. The cost is prorated to the end of your subscription period.
Your Customers Portal account is not linked to GitLab.com
When: You cannot reach the Customers Portal with your GitLab.com account
- Create and link a GitLab.com account: Change the linked account (GitLab Docs).
You reached your compute minutes limit
When: Your pipelines stop on GitLab.com shared runners
What it means: Your own runners keep working even after you reach the limit.
- Manage your compute usage, Purchase additional compute minutes (GitLab Docs), or upgrade to Premium or Ultimate.
GitLab asks for a card to use shared runners
When: You want to use GitLab.com shared runners
What it means: GitLab checks the card with a one-dollar authorization. No charge is made and no money moves. You do not need a card if you bring your own runner or disable shared runners.
You do not renew a self-managed subscription
When: Your GitLab Enterprise Edition subscription ends without renewal
What it means: Your license key stops working and GitLab Enterprise Edition no longer works. You can downgrade to GitLab Community Edition, which is free.
Official checks and support optionsContact GitLab Support
Scope: GitLab Support, by plan
Your plan decides how you reach a person: Premium and Ultimate include ticket support, while the Free plan and trials do not.
- Search the GitLab Support Knowledge Base first, as GitLab Support recommends.
- On Premium or Ultimate, open a ticket with the GitLab Support Portal ticket form.
- Make sure your organization lists you as a support contact, or your ticket is rejected.
- Choose the Preferred Region for Support closest to your working hours.
- Engineers answer tickets from Sunday 3pm to Friday 5pm Pacific Time. Response times are for the first reply, not the fix.
You are on the Free plan
When: You use GitLab Free on GitLab.com or Self-Managed
What it means: The Free plan includes no support. Billing, subscription and license problems still get a ticket, as described in Billing, subscription or license problem.
- Open a thread on forum.gitlab.com.
You are on a trial
When: You use a free Ultimate trial on GitLab.com or Self-Managed
What it means: Trials include no support.
- If you want to evaluate GitLab support, use Contact GitLab Sales.
GitLab Support offers a call or screen share
When: An engineer suggests a call on your ticket
What it means: The invitation is a single-use link sent through your ticket. A Support Engineer never asks to control your computer or to access your GitLab installation.
About
GitLab is a DevSecOps platform for planning, source control and CI/CD. You can use it on GitLab.com, the multi-tenant service run by GitLab, or self-managed in your own environment.
Still not working? Report it
If none of the help above fixed it, tell others: your report helps them see that GitLab is having a problem.
Where this status comes from
- The verdict comes from user reports, counted above a small threshold. The check of the official website (about.gitlab.com) is shown for information and does not change the verdict. An incident announced on the official status page can mark an outage as confirmed.
- GitLab's own status page →
Contact options
Emergencies on Premium and Ultimate
- Global SupportGitLab emergency support form (Global Support)Premium and Ultimate plans (Priority Support)Emergencies onlyEngineer on call 24x7
- US Government SupportUS Government emergency support formUS Government subscriptionEmergencies only
Support tickets
- Open a Support Ticket on the GitLab Support Portal for GitLab.com and Self-ManagedGitLab Support Portal ticket formPremium and Ultimate plansYou must be a listed support contact of a subscribed organizationReplies 24x5
- support.gitlab.comsupport.gitlab.comSign in to submit a ticket
Billing and subscriptions
- Subscription, License or Customers Portal ProblemsSupport ticket: Subscription, License or Customers Portal ProblemsAny plan, including Free and trialsReply within 8 hours on business days (24x5)
- Sign in with GitLab.com accountGitLab Customers PortalSign in with your GitLab.com account
Help without a ticket
- Knowledge BaseGitLab Support Knowledge Base
- GitLab Community Forumforum.gitlab.comThe Free plan does not include GitLab support
Sales
- contacting SalesContact GitLab SalesTrials do not include support
Still having trouble with GitLab? Add your report: it helps others see whether it is down.
User comments
No comments yet. Be the first!
Share your experience with GitLab
Leave a comment on GitLab
0/1000
Comments are published right away if they pass an automatic filter (insults, links and spam are hidden). Report illegal content.