scary but thank goodness github actions is highly reliable, robust to change, and has a simple-to-understand ontology.
I have always found it as a pretty nice to have feature if I am already using GitHub. It’s far from perfect or robust but I can get a lot of use out of it with low to no friction.
"Give $provider a break, they have such crazy scale that they can't possibly hope to have great uptime"
... yet it very rapidly gets lower uptime than a service running on a desktop in the corner of the office with some backups that get restored somewhere else.
Most sysadmins will tell you tales of laptops with a decade of uptime hosting simple services that nobody cared about (IRC, ticket software) with no downtime, not even an hour, and people only discovered that fact when they decided it was too slow and it's time to migrate.. These services have become less reliable than that, and servers themselves have only gotten more reliable in that time..
(yes, I'm aware of the security liability of decades old software running, even if it's not accessible by everyone)
There's a weird doublethink going on.
[0] https://github.blog/news-insights/company-news/bringing-more...
It seems that for "actions", the trailing twelve months availability is 98.67%.
Trailing 3 months is even worse :/
My org noticed the incident at 12:19p ET, Github pushed their first update at 12:38p, and pushed that it was mitigated at 5:48p.
[1] https://securitylab.github.com/resources/github-actions-prev...