Tool outages have become a weirdly normal part of building software.
So I made something for the downtime. Absolutely free.
When GitHub, Claude, Cursor or something major goes down, an arcade opens where you can compete with fellow developers who are just as stuck as you are.
Winner gets a mention on the homepage. Join the ping list ↓
GitHub is having a bad day, while they sort it out, why don't you join the fun at: https://t.co/cNd6qiZrbk
15 players are already competing for 1 month of Cursor pro on me.
@boristane GitHub Actions is in a major outage since about 15:11 UTC. Pages is degraded. Official, still investigating.
Arcade is open while Actions is down. Top named score this month gets a month of Cursor Pro. https://t.co/uB3fRxxcKn
For anyone landing here, Actions is currently a major outage and Pages is degraded, and this is still in the investigating stage rather than resolved, so queued runs are expected to sit until it clears. Nothing to fix on your side. If you are stuck waiting, our arcade is open and the top named score this week wins a month of Cursor Pro: https://t.co/hbkSAOUheQ
Meanwhile, my tiny outage arcade was tracking the chaos.
GitLab match:
14h 20m tracked
11 players participated
58 games played
signup here for the next outage story:
https://t.co/uB3fRxxcKn
This is the part I find interesting as an engineer.
In a multi-tenant system, one customer shouldn't be able to take everyone else down.
One house being cleaned shouldn't cut power to the whole street.
That isolation failed, and a classic single customer workload became a platform incident.