Started to get 503’s this morning from registry.gitlab.com:
Pulling docker image registry.gitlab.com/omg-technology/omg-development/oneform:latest …
9ERROR: Preparation failed: Error response from daemon: received unexpected HTTP status: 503 Service Unavailable (executor_docker.go:168:21s)
Hey @miles-omg, welcome to the GitLab Community Forum! 
Unfortunately, we are experiencing issues with the registry on GitLab.com at the moment. Our status page has more information and will contain the updates we make towards resolving the situation.
As that issue references, our infrastructure team is working the incident out of this issue if you’d like more information.
me too
Hi,
everyone is affected, users and GitLab team members. We’re keeping our fingers crossed for our engineers to mitigate and fix the load balancer problems highlighted in the infrastructure issue 
Cheers,
Michael
It’s very unreliable and sadly it happens too often that the registry is not usable.
Currently I’m working on a CI pipeline and so I have to stop working for today.
In the future, such a problem would result in a deployment being no longer possible.
Hi,
I have approved your post just now, the original author time was yesterday. Agreed that problems are always bad when they hinder productivity and use case, on the other hand we are human beings. The most valuable thing is that you can follow incident resolving “live” in the infrastructure issues being publicly created.
Cheers,
Michael
We just did a few manual deploys for stuff we needed yesterday morning. It wasn’t a big deal for us at least once we realized what the issue was. Thanks for getting it fixed!