Is GitLab down?
No, GitLab is up right now.
It answered in 424 ms. If it isn't working for you, the problem is probably on your side, so see what to try below.
Checked from EU (Falkenstein)
- Response time
- 424msHTTP 200 OK
- Uptime, 24 hours
- 100%288 checks
- Uptime, 30 days
- 99.79%1,457 checks
- SSL certificate
- 19daysValid until Nov 10, 2026
Last 24 hours
Checks around the world
| Location | Result | Response | Checked |
|---|---|---|---|
| EU (Falkenstein)primary | Up | 424 ms |
Countries light up as visitors run the connection test below or report problems.
Last 15 checks
| Time | Result | Answer | Response | From |
|---|---|---|---|---|
| Scheduled | Up | 200 OK | 424 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 458 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 312 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 385 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 432 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 603 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 393 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 363 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 412 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 408 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 405 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 377 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 410 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 363 ms | EU (Falkenstein) |
| Scheduled | Up | 200 OK | 357 ms | EU (Falkenstein) |
Test from your connection
Your browser tries to reach gitlab.com directly, the same way it would if you opened it. We compare that with our own check to tell whether the problem is the site or your connection.
We record only whether the test worked, how long it took and your country. Ad blockers can block the test for some sites.
Official status
Recently resolved, as reported by GitLab
- 404s on customers.gitlab.com, 3 h 28 min
- Intermittent 500 on GitLab.com, 2 h 49 min
Problem reports
Is GitLab working for you?
If not, tell others what's wrong. Reports are anonymous; we don't store IP addresses.
Nobody has reported a problem with GitLab in the last 24 hours.
Comments
No comments yet
GitLab outage history
Down for 11 min
Could not connect to the server within 6 seconds.
Down in one check
502 Bad Gateway
If GitLab isn't working for you
Reload without the cache
Press Ctrl+F5 on Windows or Cmd+Shift+R on a Mac, or open the site in a private window.
Try another network
Switch between Wi-Fi and mobile data. If it works on one, the problem is your network or provider.
Pause extensions and VPN
Ad blockers, VPNs and proxies are common causes of sites failing to load.
Restart the app or device
For mobile apps, also check for an update.
Check your clock
A wrong date or time on your device breaks secure connections.
Refresh your DNS
If only GitLab fails, restart your router or switch to a public DNS resolver.
Common questions about GitLab
- Is GitLab down for everyone or just for me?
- Most likely just you. GitLab answered our server in EU (Falkenstein) on its last check. Use "Test from your connection" on this page to see whether your own browser can reach gitlab.com.
- What problems do people report with GitLab?
- Nobody has reported a problem in the last 24 hours. If GitLab isn't working for you, add a report above so the next visitor knows.
- How often does GitLab go down?
- Over the last 30 days GitLab was reachable in 99.79% of our 1,457 scheduled checks. The latest outage we logged began on Oct 21, 2026 and lasted 11 min.
- How do you check whether GitLab is down?
- Every 5 minutes our server in EU (Falkenstein) looks up gitlab.com, connects to it and times how long the homepage takes to start answering. A failed check is repeated before it counts as an outage.
- Does GitLab have an official status page?
- Yes, GitLab posts its own updates at status.gitlab.com. We read it every few minutes; at the moment it says "Operational".