GitHub Actions is also degraded, coincidence?
For me, pipelines are queuing and not even scheduling jobs on self hosted runners.
For me, pipelines are queuing and not even scheduling jobs on self hosted runners.
https://bitbucket.org/blog/announcing-our-new-ci-cd-runtime-...
Come check out some of our cool new features while you're at it:
- https://bitbucket.org/blog/introducing-dynamic-pipelines-a-n...
- https://bitbucket.org/blog/custom-merge-checks-are-now-gener...
From the "self-hosted" perspectively, interestingly what we're seeing at Depot (https://status.depot.dev/clyrvud6i57402igofm6jtb7id) is API requests to provision new runners or receive runner jobs are receiving rate limit errors, but without the regular rate limit status HTTP headers[1].
I imagine the GitHub API / Actions control plane is rather overloaded at the moment with the outage.
[1] https://docs.github.com/en/rest/using-the-rest-api/rate-limi...
Dallas, STL, KC, Chicago all count as central. More or less equidistant for east/west coast markets. Seems like natural edge node coordinates along the scale ladder.