GitHub is down again

Original Article ↗ Hacker News Discussion ↗

Outage symptoms and status reporting

  • Users report widespread 500 errors, “Unicorn” pages, failing JSON APIs returning HTML, and broken git operations, Actions, PRs, issues, Pages, webhooks, and notifications.
  • Several note that GitHub’s status page lagged reality, initially listing only minor delays (notifications, PRs) while the main site was effectively unusable.
  • Links to external latency/uptime monitors and visualizations of GitHub’s incident history suggest a sharp increase in incidents, with some estimating they’re effectively down to “one nine” of uptime across services.
  • Some criticize the cute “Unicorn” error page as tone‑deaf when a critical service is repeatedly failing.

Operational causes and Azure migration

  • Multiple comments tie the growing instability to GitHub’s ongoing migration from its legacy infrastructure to Azure; Actions, Copilot, Pages, and Packages are already migrated, core platform is mid‑move.
  • Prior incidents have been explicitly attributed to Azure, and Azure itself has had recent multi‑hour outages.
  • Debate over migration strategy: incremental piecewise migration (current approach) vs. “shadow” copies; several note stateful systems and long timelines make any approach hard.
  • Some argue the underlying architecture and code quality (especially in the enterprise product) were already messy, and the lift‑and‑shift plus new features is exposing that.

Impact on workflows and expectations

  • Teams report being blocked on: urgent production fixes, high‑severity security reports, CI/CD via Actions, compliance‑required PR review trails, and dependency fetching.
  • There’s tension between “git is distributed, you can work offline” and the reality that many organizations centralize issues, reviews, CI/CD, and governance on GitHub.
  • Some argue 99.99% uptime isn’t strictly necessary for development; others counter that for paid services and production pipelines, this level of downtime is unacceptable.

Lock‑in and alternatives

  • Many organizations are actively considering or already migrating to alternatives: self‑hosted Forgejo/Gitea/GitLab, Codeberg, SourceHut, Bitbucket, Radicle, Tangled, raw git+ssh + custom CI.
  • Common pattern: internal forge as the source of truth, mirrored to GitHub for discoverability (stars, forks, community).
  • For popular open source projects, network effects and contributor habits make moving off GitHub “expensive,” so most stay despite outages.

Microsoft, AI, and broader trends

  • Several see a correlation between Microsoft’s AI push (Copilot, “agentic coding”) and declining reliability across GitHub, Windows 11, and other products; this is framed as speculation, not confirmed fact.
  • Others attribute outages partly to dramatically increased automated usage (agents hammering GitHub APIs) and accumulated technical debt.
  • A broader concern emerges that big tech now prioritizes shipping AI features and growth over stability and quality—“enshittification” applied to infrastructure.

Monopoly, policy, and resilience ideas

  • Debate whether Microsoft’s ownership of GitHub is an antitrust issue: some point to strong competition (GitLab, Bitbucket, Fossil, etc.), others emphasize network effects akin to social media.
  • Proposals include mandated mirror APIs for public repos and more standardized, repo‑native formats for issues/PRs/CI to reduce platform lock‑in.
  • Some maintainers share strategies: independent monitoring, mirroring, and self‑hosting critical components to avoid being fully blocked by GitHub outages.