I noticed earlier this week that my URL bar now pre-fills githubstatus.com instead of github.com when I type "gith"
Disruption with Some GitHub Services – Resolved
11–20 of 176 posts
Re: Disruption with Some GitHub Services – Resolved
#12Notice odd behavior on GitHub. Get gaslit by a green status page. Notice more odd behavior on GitHub. Think it must be me this time. See unusual action queuing. Ah, an incident on the status page. Go for a walk and check HN on my phone. The AI SDLC.
The status page is the last one to get the update. Reddit, HN, X, company chat are all always reporting it sooner.
Re: Disruption with Some GitHub Services – Resolved
#13So a normal Wednesday
Re: Disruption with Some GitHub Services – Resolved
#14> We've identified an issue with a database primary and are failing over to a replica immediately
This is why it's hard to take GitHub seriously. How can a single database cause an outage for everyone? This is amateur stuff. Have they no sharding or partitioning internally? Paying customers should not be impacted in the same way as free ones are.
Re: Disruption with Some GitHub Services – Resolved
#15> We've identified an issue with a database primary and are failing over to a replica immediately This is why it's hard to take GitHub seriously. How can a single database cause an outage for everyone? This is amateur stuff. Have they no sharding or partitioning internally? Paying customers should not be impacted in the same way as free ones are.
I wonder what is this database, and why it is hard to fall-over automatically.
Re: Disruption with Some GitHub Services – Resolved
#16> We've identified an issue with a database primary and are failing over to a replica immediately This is why it's hard to take GitHub seriously. How can a single database cause an outage for everyone? This is amateur stuff. Have they no sharding or partitioning internally? Paying customers should not be impacted in the same way as free ones are.
Why shouldn't it? Most companies run on a single database server. If they can immediately fail over to a replica, that's doing it right.
Maybe you expect that part of GitHub to have a scale where a single database can't handle it, but evidently that isn't true.
We can criticise them for not splitting up free and paid customers but again, most companies don't do that.
Re: Disruption with Some GitHub Services – Resolved
#17GitHub needs to completely bifurcate their enterprise/paid services from their free services at the infra level.
That's what I don't understand. They could mitigate their name so much if they just split free/paid/enterprise. It's already shown that enterprise is much more estable and is largely unaffected from service disruptions. Why don't they go one more layer? For sure it's worth the extra complexity.
Re: Disruption with Some GitHub Services – Resolved
#18> We've identified an issue with a database primary and are failing over to a replica immediately This is why it's hard to take GitHub seriously. How can a single database cause an outage for everyone? This is amateur stuff. Have they no sharding or partitioning internally? Paying customers should not be impacted in the same way as free ones are.
Did you not read it? Just because there's a database primary doesn't mean there is 1 primary database. There's likely man redundancies and they have issue with how they're allocating traffic to them which is in turn causing an issue with how much traffic redundancies are receiving.
Re: Disruption with Some GitHub Services – Resolved
#19GitHub needs to completely bifurcate their enterprise/paid services from their free services at the infra level.
According to their status pages (e.g. https://eu.githubstatus.com/, https://us.githubstatus.com/), their Enterprise Cloud uptime for Actions is significantly higher.
Re: Disruption with Some GitHub Services – Resolved
#20We can't keep living like this.