We are using GitLab CI/CD and getting errors with artifacts being uploaded after a job completes successfully. Nothing has actually changed recently related to this (or the artifacts themselves), but the upload is failing as of today, so I think there is a service issue with GitLab rather than something in our project.
Can this please be investigated?
We have the same problem. Sometimes we get
524 Origin Time-out and others
502 Bad Gateway.
Thanks Tobias, has the issue just recently started for you too?
Our artifact size is just under 100MB of the maximum limit of 1GB. We normally use our own runners installed in Kubernetes, but I get the same issue when using GitLab’s shared runners, so I’m pretty sure this is an issue with GitLab.com
Any word from someone at GitLab?
Our problems started about the same time that you posted the initial post here. We’ve had some other problems with our pipeline since yesterday so I initially thought that it was related to that, but that was not the case.
We have our runner running on GCP (Europe West 3) Compute Engine on Docker.
We haven’t heard anything new yet.
We’re getting three kind of errors at the same stage.
502 Bad Gateway
520 Origin Error
524 Origin Time-out
Ah, it has appeared on their status page, so it seems that they’re finally aware
Thanks for replying so we knew it wasn’t just us
Ah, nice, thanks for the heads up and for the initial post!
As far as I can see, the latest update marked the incident issue as resolved.
Apologies for the inconvenience - I would recommend raising your concern directly in the incident issue so that our infrastructure and support team sees your question and can respond accordingly. If you do not want to post publicly, open a support ticket as an alternative please. In this forum topic, it is only me reading at the moment. I will link this topic in the issue though, I forgot about this yesterday.