← Mon, Oct 5 digest

Incident with Actions

read article ↗ hn thread ↗

GitHub experienced an incident causing degraded performance and availability across Actions, Pages, and core repository management features.

summary is enough The status report is brief, but the comment thread provides valuable insights into self-hosted runners and GitHub reliability alternatives.

summary

GitHub suffered an outage affecting Actions, Pages, billing, and repository lists, which has since been mitigated with queued jobs clearing. The recurring instability sparked widespread user frustration in the comments regarding frequent downtime. Commenters debated moving to self-hosted runners or alternative platforms, though many noted that GitHub's control plane bottlenecks still impact custom setups.

key points

  1. GitHub Actions and Pages experienced degraded availability alongside issues accessing repository lists, licensing, and billing pages.
  2. Mitigations have been successfully applied and queued jobs are currently clearing across runners.
  3. Frequent outages are driving developers toward self-hosted runners and alternative CI platforms like GitLab or Forgejo.

who should read it

Software engineers and DevOps professionals managing CI/CD pipelines and platform dependencies.

discussion skeptical

consensus

Commenters widely agree that GitHub Actions outages are increasingly frequent, prompting heavy criticism of platform reliability.

pushback

Some point out that even with self-hosted runners, users remain vulnerable to GitHub's central control plane failures.

best comment by bushido ↗

I recently got annoyed with the amount I was paying on actions for a single repo. And decided to use a Mac mini that I had lying around to become the sole self-hosted runner for that repository instead.

It was ridiculously easy to set up, reduced my issues with GitHub significantly and the mini will literally pay for itself 3-4x over this year with the $$$ I'm saving not paying for GH actions.

The most surprising part for me was not the cost savings, but that all my workflow runtimes went down by about 70-80%.

Switching to a local Mac mini runner eliminated cloud costs, improved reliability, and slashed workflow runtimes by 70 to 80 percent.

Generated by an LLM from the article and thread. Check the sources before relying on it.