Why does the main page show all green when there is an ongoing incident? All green here -> https://www.githubstatus.com/
This is normal for Microsoft. It's as though status is owned and controlled by either marketing or accounting, not engineering.
GitHub partial outage
51–60 of 88 posts
Re: GitHub partial outage
#52Re: GitHub partial outage
#53Earlier quoted context omitted.
Wow. It wasn't already running on Azure? What was it (or is it) running on?
iirc (it's been a while) they where on rackspace when Microsoft bought them out - there was an article a few months ago saying they where moving to Azure and freezing new features while they do the move[1]. [1] https://thenewstack.io/github-will-prioritize-migrating-to-a... Honestly I don't know half the features they have added because the surface is huge at this point everyone seems to be using a (different) subset…
A team of us moved it off Rackspace in 2013, it’s been mostly in a set of GitHub operated colo since then. Used to be there was some workloads on AWS and a bit of DirectConnect. Now it’s some workloads on Azure.
To the best of my knowledge there’s been no Rackspace in the picture since about 2013, the details behind that are fuzzy as it’s been 10+ years since I worked on infrastructure at GitHub.
Re: GitHub partial outage
#54Earlier quoted context omitted.
iirc (it's been a while) they where on rackspace when Microsoft bought them out - there was an article a few months ago saying they where moving to Azure and freezing new features while they do the move[1]. [1] https://thenewstack.io/github-will-prioritize-migrating-to-a... Honestly I don't know half the features they have added because the surface is huge at this point everyone seems to be using a (different) subset…
A team of us moved it off Rackspace in 2013, it’s been mostly in a set of GitHub operated colo since then. Used to be there was some workloads on AWS and a bit of DirectConnect. Now it’s some workloads on Azure. To the best of my knowledge there’s been no Rackspace in the picture since about 2013, the details behind that are fuzzy as it’s been 10+ years since I worked on infrastructure at GitHub.
yeah, we did not have anything in Rackspace for many years before the Microsoft acquisition. I remember having to migrate some tiny internal things off of Heroku, though!
Re: GitHub partial outage
#55It's possible that Microsoft buying GitHub was a large-scale psyop intended to reduce the productivity of the competition. Any time their startup competitors are making too much progress they can just push the "GitHub incident" button and slow everyone down.
We used to obsessively care about 500s. Like I would make a change that caused a 0.1% spike in 500s and I would silently say I'm sorry to the folks who got the unicorn page. I'm not sure the new school cares nearly as much. But then again this is how companies change as they mature. I saw this with StubHub as well.. The people who care the most are the initial employees, employee #7291 usually dgaf
I fall into the new school gen z category, and I think you're right. We don't care. We don't care about the problems started before us, and we owe nothing to no one (but our employers, must increase value for shareholders of course).
I simply want to survive. I'll kiss ass where I have to, but not to people I don't work on behalf of.
Re: GitHub partial outage
#56Looking forward to the postmortem. Are they using AI agents this time to resolve the outage? Probably not. But this time, there is no CEO of GitHub to contact and good luck contacting Satya to solve the outage.
The postmortem will be simple since Github goes down so consistently every week you can almost use it as an alternative timekeeping system.
The pulsar of web services
Re: GitHub partial outage
#57Earlier quoted context omitted.
We used to obsessively care about 500s. Like I would make a change that caused a 0.1% spike in 500s and I would silently say I'm sorry to the folks who got the unicorn page. I'm not sure the new school cares nearly as much. But then again this is how companies change as they mature. I saw this with StubHub as well.. The people who care the most are the initial employees, employee #7291 usually dgaf
I fall into the new school gen z category, and I think you're right. We don't care. We don't care about the problems started before us, and we owe nothing to no one (but our employers, must increase value for shareholders of course). I simply want to survive. I'll kiss ass where I have to, but not to people I don't work on behalf of.
Hell yeah
Re: GitHub partial outage
#58Earlier quoted context omitted.
Wow. It wasn't already running on Azure? What was it (or is it) running on?
In the Pragmatic Engineer podcast episode with the former CEO of Github, the latter mentioned that they had their own infra for everything. If I remember correctly, this was due to the fact that Github is quite old and at the time when Github Actions became a thing, cloud providers were not really offering the kind of infra that was necessary to support the feature.
GitHub is old, but GitHub Actions are not. Indeed, GitHub Actions launched two months after the Microsoft acquisition was announced [0], and it is a half-assed clone of Azure Pipelines.
Re: GitHub partial outage
#59Earlier quoted context omitted.
We used to obsessively care about 500s. Like I would make a change that caused a 0.1% spike in 500s and I would silently say I'm sorry to the folks who got the unicorn page. I'm not sure the new school cares nearly as much. But then again this is how companies change as they mature. I saw this with StubHub as well.. The people who care the most are the initial employees, employee #7291 usually dgaf
I fall into the new school gen z category, and I think you're right. We don't care. We don't care about the problems started before us, and we owe nothing to no one (but our employers, must increase value for shareholders of course). I simply want to survive. I'll kiss ass where I have to, but not to people I don't work on behalf of.
Can't say that's entirely true for me ('02). If my [ employer, supervisor, ... ] provides me with logical, traceable tasks with their context properly laid out, I can totally put a ton of effort into providing meticulous, well thought out solutions, that are as good as it gets under the provided constraints. It's the non-sensical (be it actually non-sensical or just not understood enough because of unprovided context) tasks that make me not care.
Re: GitHub partial outage
#60Github is owned by Microsoft, so this is a pretty small time indie operation, you need to give them a break.
Just your casual $3.8T company. There were so many severe Github Actions outages (10+ ?) in the past year. Cause: Migration to the disaster zone also known as Azure, I assume. Most of them happened during (morning) CET working hours, as to not inconvenience the americans and/or make headlines. Money doesn't buy competency. It's a long-term culture thing. You can never let go on maintaining competency in your organiza…
I thought GitHub Actions (in particular; not the rest of GitHub) was always Azure, because it was initially a fork of Azure Pipelines?
GitHub as a whole, including the previously non-Azure bits, does seem flakier than a few years ago though, for sure.