idkasam

Agree, and it's already happening. Mostly smaller orgs so far though, they can just swap the runner label and move on. Larger orgs are starting to look into it but it's slow, lots of red tape (security review, procurement, "we're already paying GitHub").

Try other runners that have smart Caching instead.

You should try different runner solution. We use Avrea.com and works super well for our workflows.

Yeah, that’s brutal. And really interesting that you were seeing the symptoms intermittently for 15+ hours before the full outage.

You should check out Avrea — they’re building around exactly this problem, with a lot more control and reliability than relying entirely on GitHub Actions. New player, but insanely fast. You can even move your existing runners over with one line, so pretty easy to try.

Avrea.com is a great alternative — a new player, but insanely fast and reliable. You get a ton of control and flexibility, and they’re building with insane velocity. I’d definitely give them a try if I were you.