|
| ▲ | simoesd 2 days ago | parent | next [-] |
| 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... |
| |
| ▲ | rschiavone 2 days ago | parent | next [-] | | Of course they hide behind corporate speak like "Bringing more transparency". | |
| ▲ | 2 days ago | parent | prev [-] | | [deleted] |
|
|
| ▲ | PunchyHamster 2 days ago | parent | prev | next [-] |
| Sometimes both nines are even in the front! |
| |
| ▲ | nimbius 2 days ago | parent [-] | | Cursed by mighty Redmond to roam the market wasteland until death, one of the seventy some odd beleaguered CoPilot products is now being lashed like a haggard burro to the dying light of a once prominent development platform that, upon itself, were pinned the hopes and dreams of a commercial software juggernaut to capture the hearts and minds of developers all around the world. | | |
|
|
| ▲ | gen220 2 days ago | parent | prev | next [-] |
| https://isgithubcooked.com/?services=actions It seems that for "actions", the trailing twelve months availability is 98.67%. Trailing 3 months is even worse :/ |
|
| ▲ | deathanatos 2 days ago | parent | prev | next [-] |
| 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. |
|
| ▲ | seanhunter 2 days ago | parent | prev | next [-] |
| …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... |
|
| ▲ | infecto 2 days ago | parent | prev | next [-] |
| 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. |
| |
| ▲ | maccard 2 days ago | parent [-] | | We had more build failures in 2025 due to Actions outages or degraded service than any other reason. | | |
| ▲ | infecto 2 days ago | parent [-] | | Which is fair but inversely we do many builds throughout the day most business days and have not had an impact where we noticed it. Could also be that we deploy often and frequently and have setup our builds to be as quick as possible so any issues would likely go unnoticed. | | |
| ▲ | maccard 2 days ago | parent [-] | | Yeah totally. We use GitHub + actions for backend, and self host Perforce + TeamCity for our main game codebase. We had 0 downtime in 12 months on our TC as a comparison. I know there’s a difference between running an internal service and developing a global scale platform that is abused, but as a user I don’t care about those concerns, I care about the platform being up! | | |
| ▲ | dijit 2 days ago | parent [-] | | "You can't possibly hope to have as many resources caring about uptime as $provider, you should outsource to them" "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. |
|
|
|
|
|
| ▲ | tom1337 2 days ago | parent | prev [-] |
| And now it has an outage https://www.githubstatus.com/incidents/dbypmw7h77l5 |
