I debugged for one min at 11:59 trying to push, and then my eat-lunch notification came in at 12:00 and I opened hackernews with a tuna sandwich and this is super helpful because it means I wont need to debug it locally for 10 mins before figuring out Github is down.<p>Edit - Just want to clarify when I say "opened hackernews with a tuna sandwich" I want to clear up that I did indeed full on mash the keyboard letters with my sandwich. It's costing me a fortune in keyboards every day and it's ruining my sandwich most days as well, I think I have an issue.
The GitHub Status shows 14 incidents affecting Git Operations this year alone [1]. That's quite a lot, considering it's only May. I wonder if the outages were always this frequent and just get more publicity on here now, or whether there was a significant increase in outages fairly recently.<p>[1] <a href="https://www.githubstatus.com/history" rel="nofollow">https://www.githubstatus.com/history</a>
Interested to hear whether anyone actually managed getting some Client Credits as per their SLA [1]? Over the last quarter they probably went sub 99.9% in some services.<p>[1] <a href="https://github.com/customer-terms/github-online-services-sla">https://github.com/customer-terms/github-online-services-sla</a>
Once again another GitHub incident and 4 days later before the last one [0], GitHub Actions goes down.<p>You are better off self-hosting at this point, rather than centralizing everything to GitHub [1] as it is just chronically unreliable for years ever since the Microsoft acquisition.<p>[0] <a href="https://news.ycombinator.com/item?id=35817998" rel="nofollow">https://news.ycombinator.com/item?id=35817998</a><p>[1] <a href="https://news.ycombinator.com/item?id=22867803" rel="nofollow">https://news.ycombinator.com/item?id=22867803</a>
I'm the lone person at my team that still believes in keeping most of our stuff local, with online versions as primarily backup.<p>Every time some global service goes down, or internal internet/intranet goes down, there is a security breach, or a WFH person has a power outage I'm reminded I'm right.<p>I'm no luddite, these services make you dependent on them. The worst thing I'm dependent on here is a bad computer. We have backups and keep our files on our network, so it seems fine. We are slowly moving to an online system, and I'm constantly reminded all the problems shifting online.<p>Meanwhile, if I had a linux server, we would be in control of our own destiny.
Perhaps everyone should stop complaining and be thankful for a chill morning. You can't create a PR right now - go get a pastry and some fresh air. Be in the moment for once. It's beautiful outside*<p>* Where I am
From the outside, it appears GitHub doesn't have any internal sharding going on.
Outages always affect _all_ repos.<p>Architecturally this seems rather sub optimal?<p>EG AWS doesn't roll out changes globally - they start with an internal shard within a region and progressively roll out to more shards and more regions.<p>Why do GitHub not do the same?
If that makes you mad, I still need help with <a href="https://github.com/MichaelMure/git-bug">https://github.com/MichaelMure/git-bug</a> ;-)
Coming at some point, kanban and pull-request support, offline-first!
Can anyone from GH weigh in on this? We've had several major outages from GH over the last month or two, and the company has been completely silent on the causes, as well as any sort of remediation steps to fix stability.<p>As a somewhat large size org, we're now exploring other options for code hosting.
Was unable to merge PRs.<p>Earlier, I also got GitHub PR comment emails about 6 hours late.<p>Whatever it is, it’s been happening for more than 6 hours.
They are adding affected services to the status entry title (started with Issues, Actions, Operations). Can't even do a simple push due to this so-called "degraded performance".
"We gave ChatGPT root access to our infrastructure servers, and unexpectedly it crashed everything."<p>That's <i>almost</i> believable at this point. ;)