To the naysayers, I would point out that actions has not only one but TWO 9s of uptime. [1]
https://isgithubcooked.com/?services=actions
It seems that for "actions", the trailing twelve months availability is 98.67%.
Trailing 3 months is even worse :/
Yesterday's ≈5h long incident with the Pull Requests page being blank is listed as 1h 47m.
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.
…And at this point probably not one but two 9s (or possibly more) of security vulnerabilities [1]
[1] https://securitylab.github.com/resources/github-actions-prev...
For all the hate it gets, I use them regularly with little to no complaints.
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.
And now it has an outage https://www.githubstatus.com/incidents/dbypmw7h77l5
Github has recently changed the way their status page tracks uptime in the name of "transparency"[0]. "Partial Outages" are now only worth 30% of their duration, and "Degraded Performance" is worth none, so their uptime values are now wildly inflated.
[0] https://github.blog/news-insights/company-news/bringing-more...