GitLab service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Is GitLab Down? Check gitlab.com Status and Outages
Run a live reachability check for gitlab.com. Compare the regional responses with the problem you see in GitLab.
Find GitLab help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked-
Verdict-
Response Time-
Final URL-
Regional checks
Is GitLab working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding GitLab connection and service problems
GitLab.com's public status does not automatically describe a self-managed GitLab instance.
The checker above requests gitlab.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual GitLab action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse developer service checks.
GitLab status information and official help
GitLab help and reporting
This status dashboard covers GitLab.com, not every self-managed installation.
Open gitlab.com
Open the website in your browser and compare it with the result above.
Where to report problems with GitLab
Open GitLab help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Details to include in your report
Instance hostname, project, Git/CI action, runner or job ID and first error line.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to GitLab.
What to check when GitLab is not working
These are troubleshooting comparisons, not claims that GitLab is currently experiencing a particular incident.
Start with the action that failed
Identify whether your repository is on GitLab.com or an organisation-hosted domain and test that actual host.
Narrow down the affected service
Compare web access, Git transport and CI jobs separately; inspect the runner/job stage for CI failures.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if GitLab is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the gitlab.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open GitLab status and check whether the named service and incident time fit your error.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If GitLab Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when GitLab seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open gitlab.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader GitLab issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting GitLab support.
Frequently asked questions about GitLab problems
Is GitLab down, or is the problem limited to one feature?
Run the gitlab.com check and compare its original timestamps and responses with your actual error. GitLab.com's public status does not automatically describe a self-managed GitLab instance.
Where can I report a problem with GitLab?
Use the community buttons on this page to share whether the service works for you. For help from GitLab, use the official help/reporting resource linked above. This status dashboard covers GitLab.com, not every self-managed installation.
What should I check first when GitLab is not working?
Identify whether your repository is on GitLab.com or an organisation-hosted domain and test that actual host. Compare web access, Git transport and CI jobs separately; inspect the runner/job stage for CI failures.
What information helps GitLab support investigate?
Instance hostname, project, Git/CI action, runner or job ID and first error line.