GitLab Service Disruption

mritzmann wrote: post #3

> Pipelines are being processed, but delays are still expected for up to 2 hours. Jobs may still be stuck in pending state during this time. This made me realize how dependent I am on GitLab CI/CD. I don't even know how I would perform a new deployment without it.

> Background processing remains degraded, however the revert MR has been merged a short time ago. We are monitoring performance to see if the MR results in performance returning to optimal levels.

16 hours in, still degraded performance

Re: GitLab Service Disruption

#5

Post by _1tan » Wed, Feb 04, 2026, 12:16 PM UTC

deveesh_shetty wrote: post #4

mritzmann wrote: post #3

> Pipelines are being processed, but delays are still expected for up to 2 hours. Jobs may still be stuck in pending state during this time. This made me realize how dependent I am on GitLab CI/CD. I don't even know how I would perform a new deployment without it.

> Background processing remains degraded, however the revert MR has been merged a short time ago. We are monitoring performance to see if the MR results in performance returning to optimal levels. 16 hours in, still degraded performance

Still no worky for us.