Same. It's weird how I always find out that GitHub is down before GitHub does. Took 15 minutes before it appeared on githubstatus.com
All these monitoring rules are of the format "when 500 errors > baseline for x minutes". Otherwise you'd have monitoring alerts every second. So it is normal for users to already see errors before github officially counts it as an outage.
loading story #48280325
loading story #48279368
In a high performance service with good maintenance and upkeep, you page for all 500s. A noisy pager forces the team to fix the 500s.
Maybe the Github Actions infrastructure isn't run like that.
edit: my oncall rotation notified on all 500s, 24/7, not just rates - https://news.ycombinator.com/item?id=48279262
loading story #48280000
loading story #48280046
loading story #48280088
loading story #48279130
loading story #48279088
loading story #48279134
loading story #48279934
loading story #48279345
loading story #48281136
More likely that 'update the Status site' lives a long way down their incident response plan, and they have alarms going off well before that
loading story #48279324
loading story #48279926
> It's weird how I always find out that GitHub is down before GitHub does
No, it's not. Official updates = potential SLA penalties. Always requires approval.
loading story #48281483
{"deleted":true,"id":48282191,"parent":48278828,"time":1779813773,"type":"comment"}
> githubstatus.com
There's a threshold. It shows only once 1000 users complain.
/i
{"dead":true,"deleted":true,"id":48279515,"parent":48278828,"time":1779801796,"type":"comment"}