Is GitLab Container registry down for everyone or just for me?

Most likely just you. GitLab Container registry 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 registry.gitlab.com.

What problems do people report with GitLab Container registry?

Nobody has reported a problem in the last 24 hours. If GitLab Container registry isn't working for you, add a report above so the next visitor knows.

How often does GitLab Container registry go down?

Over the last 30 days GitLab Container registry was reachable in 99.86% of our 1,458 scheduled checks. The latest outage we logged began on Oct 21, 2026, seen in a single check.

How do you check whether GitLab Container registry is down?

Every 5 minutes our server in EU (Falkenstein) looks up registry.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 Container registry have an official status page?

Yes, GitLab Container registry posts its own updates at status.gitlab.com. We read it every few minutes; at the moment it says "Operational".

Is GitLab Container registry down?

registry.gitlab.comDeveloper toolsChecked every 5 minutes

Official status

No, GitLab Container registry is up right now.

It answered in 324 ms. If it isn't working for you, the problem is probably on your side, so see what to try below.

Checked 3 minutes ago from EU (Falkenstein)

Response time: 324msHTTP 200 OK
Uptime, 24 hours: 100%288 checks
Uptime, 30 days: 99.86%1,458 checks
SSL certificate: 30daysValid until Nov 21, 2026

Last 24 hours

UpProblemsDownNo data

24h agoNo problems detectedNow

Typical 329 msFastest 320 msSlowest 376 ms

500 ms250 ms

24h ago18h12h6hNow

Checks around the world

ReachableMixed or reportsUnreachable

Latest result from each check location
Location	Result	Response	Checked
EU (Falkenstein)primary	Up	324 ms	3 minutes ago

Countries light up as visitors run the connection test below or report problems.

Last 15 checks

Newest first

The latest checks of GitLab Container registry
Time	Result	Answer	Response	From
Oct 22, 21:47 UTCScheduled	Up	200 OK	324 ms	EU (Falkenstein)
Oct 22, 21:42 UTCScheduled	Up	200 OK	332 ms	EU (Falkenstein)
Oct 22, 21:37 UTCScheduled	Up	200 OK	320 ms	EU (Falkenstein)
Oct 22, 21:32 UTCScheduled	Up	200 OK	347 ms	EU (Falkenstein)
Oct 22, 21:27 UTCScheduled	Up	200 OK	344 ms	EU (Falkenstein)
Oct 22, 21:22 UTCScheduled	Up	200 OK	332 ms	EU (Falkenstein)
Oct 22, 21:17 UTCScheduled	Up	200 OK	323 ms	EU (Falkenstein)
Oct 22, 21:12 UTCScheduled	Up	200 OK	345 ms	EU (Falkenstein)
Oct 22, 21:07 UTCScheduled	Up	200 OK	334 ms	EU (Falkenstein)
Oct 22, 21:02 UTCScheduled	Up	200 OK	320 ms	EU (Falkenstein)
Oct 22, 20:57 UTCScheduled	Up	200 OK	322 ms	EU (Falkenstein)
Oct 22, 20:52 UTCScheduled	Up	200 OK	326 ms	EU (Falkenstein)
Oct 22, 20:47 UTCScheduled	Up	200 OK	335 ms	EU (Falkenstein)
Oct 22, 20:42 UTCScheduled	Up	200 OK	355 ms	EU (Falkenstein)
Oct 22, 20:37 UTCScheduled	Up	200 OK	320 ms	EU (Falkenstein)

Test from your connection

Your browser tries to reach registry.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

GitLab status page

OperationalFrom GitLab's own status page, read 2 minutes ago

This endpoint shares GitLab's status page. Official updates and history are on the main service page.

Problem reports

Is GitLab Container registry 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 Container registry in the last 24 hours.

Comments

No comments yet

Describe what isn't working with GitLab Container registry to help the next person.

GitLab Container registry outage history

Last 90 days

Down in one check
Oct 21, 10:35 UTC
Could not connect to the server within 6 seconds.
Down in one check
Oct 21, 10:24 UTC
Could not connect to the server within 6 seconds.

If GitLab Container registry 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 Container registry fails, restart your router or switch to a public DNS resolver.

Common questions about GitLab Container registry

Is GitLab Container registry down for everyone or just for me?: Most likely just you. GitLab Container registry 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 registry.gitlab.com.
What problems do people report with GitLab Container registry?: Nobody has reported a problem in the last 24 hours. If GitLab Container registry isn't working for you, add a report above so the next visitor knows.
How often does GitLab Container registry go down?: Over the last 30 days GitLab Container registry was reachable in 99.86% of our 1,458 scheduled checks. The latest outage we logged began on Oct 21, 2026, seen in a single check.
How do you check whether GitLab Container registry is down?: Every 5 minutes our server in EU (Falkenstein) looks up registry.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 Container registry have an official status page?: Yes, GitLab Container registry posts its own updates at status.gitlab.com. We read it every few minutes; at the moment it says "Operational".