GitHub degraded performance – resolved
githubstatus.com
GitHub degraded performance – resolved
1–10 of 58 posts
Re: GitHub degraded performance – resolved
#2Re: GitHub degraded performance – resolved
#3Re: GitHub degraded performance – resolved
#4Oh boy, this is going to be a fun day.
Re: GitHub degraded performance – resolved
#5Re: GitHub degraded performance – resolved
#6When 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.
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.
Re: GitHub degraded performance – resolved
#7In the middle of onboarding with a new company. We're at a critical point of training that requires GitHub. Oh boy, this is going to be a fun day.
Re: GitHub degraded performance – resolved
#8Re: GitHub degraded performance – resolved
#9This 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. 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 y…
Re: GitHub degraded performance – resolved
#10This 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. 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 y…
That by itself would be ridiculous, but there's more to it than that. Your GHE server won't have new code deployed to it hundreds of times per day the way github.com does. You probably won't be the target of ddos attacks either.
Very few of github.com outages are the result of maintenance errors.