Shared CI runner unable to clone source code

Summary

My CI runner is no longer able to run clone my project initially. It appears as though GitLab.com is encountering an internal server error. This began after the EE upgrade that took place earlier today.

Steps to reproduce

https://gitlab.com/more-cores/bot/-/jobs/36451802

In the above build you'll see that earlier today this build ran fine, but now it's failing. Retrying the same build or pushing a new commit produces a consistent problem (the 500 error).

What is the current bug behavior?

The docker-auto-scale runner fails to clone my repository due to a 500 error within GitLab.

What is the expected correct behavior?

Successfully cloning the source code so the build can be run.

Relevant logs and/or screenshots

Running with gitlab-runner 10.1.0-rc.1 (946e835b)
  on docker-auto-scale (e11ae361)
Using Docker executor with image registry.gitlab.com/citygro/docker-and-compose ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image docker:dind ID=sha256:a3087974c87e56318d6b702e9f1f4f3558198826c0a1f3e2b844432491c1a565 for docker service...
Waiting for services to be up and running...
Using docker image sha256:0ae51fcb9e088551e890d9be08de06a5862d9169c02ff0c18cef68ffb00170de for predefined container...
Pulling docker image registry.gitlab.com/citygro/docker-and-compose ...
Using docker image registry.gitlab.com/citygro/docker-and-compose ID=sha256:a524ed5b35ee4aeb27ce5329e213d49c91a54a74255b7d2e9e8d7410f414d6ea for build container...
Running on runner-e11ae361-project-4400510-concurrent-0 via runner-e11ae361-srm-1508193258-b3048d31...
Cloning repository...
Cloning into '/builds/more-cores/bot'...
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 Internal Server Error
fatal: The remote end hung up unexpectedly
ERROR: Job failed: exit code 1

Output of checks

This bug happens on GitLab.com