This one is pretty nasty. Getting tired of the disengagement this causes for the team. It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process.<p>When I get back from vacation we are moving our shit to the enterprise plan. $21/user-month is really not that big of a deal when you are running basically your entire business through the product.<p>I do agree that it's ridiculous to assume that we can manage Github's software better than their own engineers, but at the same time our infrastructure has proven itself to be extremely reliable over the last 4-5 years. Even hosting GH enterprise on public AWS/Azure is more ideal in my eyes now, because I can control the physical region and tenancy. There is an Azure datacenter within 100 miles of many of our home offices and I can ensure that our Github stack spins up there. Minimizing the amount of internet you have to transit to get to your applications can sidestep a lot of this stormy public cloud/internet weather bullshit.
In the middle of onboarding with a new company. We're at a critical point of training that requires GitHub.<p>Oh boy, this is going to be a fun day.
This incident has been marked as resolved. You guys could check how often Github notable incidents that really captures the audience's attention in HN [0] [1]:<p>[0]<a href="https://news.ycombinator.com/from?site=githubstatus.com" rel="nofollow">https://news.ycombinator.com/from?site=githubstatus.com</a><p>[1]<a href="https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=false&query=githubstatus.com&sort=byPopularity&type=story" rel="nofollow">https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=fal...</a>
They were down at least a solid hour last week and didn't even post to their status page. I put in a query and got no response. They then unilaterally closed the ticket asked me how my support experience was. Time to move to Gitlab. <a href="https://news.ycombinator.com/item?id=28874751" rel="nofollow">https://news.ycombinator.com/item?id=28874751</a>
I'm surprised they don't have a couple of separate clusters that they roll things out to and monitor. Seems like you could have a very stable "high paying customers" cluster that is at the very end of your deployment cycle after a ton of canary checks on the way get through.