Show HN: Red Squares – GitHub outages as contributions

· privacy · Source ↗

TLDR

  • Satirical heatmap mirrors GitHub’s contribution graph but maps platform outages: 35.1 days of downtime across 170 incident days in the past year.

Key Takeaways

  • Data sourced live from mrshu/github-statuses, which reconstructs incident history from githubstatus.com; scheduled maintenance excluded.
  • Worst single day: Thu, Nov 20, 2025, logged as 1.1 days of outage duration.
  • Heatmap built with Mantine; darker squares indicate longer outage duration per day.
  • 170 days with at least one incident recorded over the trailing 12 months.

Hacker News Comment Review

  • Commenters dispute scope: several incidents flagged as “GitHub outages” are actually third-party AI provider degradations (Gemini, Grok, Claude Opus 4 via Copilot), which GitHub cannot control.
  • A commenter’s independent analysis found GitHub is up 96.5% on weekends vs 89.3% on weekdays; incidents touch 62% of weekdays but only 11% of weekends, with Tuesday-Thursday as the worst window.
  • Tension exists between official githubstatus.com (which historically shows green during real degradations) and third-party trackers; commenters flag the gap as an SLA credibility problem.

Notable Comments

  • @natty: Highlights the stark contrast between official and third-party status pages and questions whether GitHub’s SLA terms are legally defensible given the discrepancy.
  • @jve: Flags data accuracy issues: the Nov 20 worst-day tooltip shows only 1.3 hours, not 1.1 days, and Nov 19 lists a 1.3-day outage whose tooltip shows 8.1 hours.
  • @whirlwin: Just migrated 300+ pipelines from Azure DevOps to GitHub Actions and is now asking for alternatives.

Original | Discuss on HN