Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Red Squares – GitHub outages as contributions

red-squares.cian.lol

Post reply on HN
Print view View original

61–70 of 175 posts

Re: Red Squares – GitHub outages as contributions

#61

Post by u_fucking_dork »

Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc.

Just compare the GitHub status page for public GitHub vs the enterprise cloud pages.

Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevented me from doing work.

If the problems didn’t revolve around load, I’d expect to see the same uptime problems reflected on the enterprise offering.

Re: Red Squares – GitHub outages as contributions

#62

Post by rufo »

bharxhav wrote: post #6

Would be interesting to see if this correlated with their release cycles.

At least as of when I left the company, GitHub was being deployed to fairly close to once every 60-90 minutes (the frequency of a deploy train/merge queue batch going out) 24 hours a day, at least during weekdays… there are a fair number of international engineers and deploy trains get crowded during main US business hours, so while there are fewer PRs going out at odd hours US time, there were typically still some. There aren’t dedicated releases as such for GitHub-hosted instances - everything you release needs to be gated behind a feature flag or other mechanism if it’s not going live immediately, and your code either needs to handle the database in both its pre- and post-migrated state, or you need to run the migration in advance of your code shipping out.

Fun fact: it used to be the case that GitHub was actually _less_ reliable if nobody deployed to it… there used to be various resource leaks that we didn’t see when people were deploying all day, since then the app wasn’t getting restarted constantly. After GitHub went down during a holiday break we had volunteers to deploy GitHub once a day during holiday breaks, until the underlying issues were eventually fixed.

Re: Red Squares – GitHub outages as contributions

#63

Post by freakynit »

tealpod wrote: post #60

If anyone wants a aggregated status page for github, cloud & AI services. https://status-page.org/

You can let people organize/filter them into groups based on the stack they use and provide email/discord/slack notifications if any of these form their groups change their status.

Re: Red Squares – GitHub outages as contributions

#64

Post by dijit »

dvh wrote: post #56

I didn't know azure was this bad, completely changed my opinion on their cloud offerings

Really? A 10 minute interaction with the platform was enough to inform me that no serious engineer is in charge, and no serious engineer chooses this platform.

It is a platform for CFOs to avoid having another vendor relationship.

Re: Red Squares – GitHub outages as contributions

#65

Post by philipwhiuk »

__natty__ wrote: post #57

Contrast between official [0] and third party status pages [1] is huge. How their terms of service for SLA are legal if they are so different from real world usage of their product? I really like GitHub and their services but every time when it’s broken and their status page is green something screams inside me. [0] https://www.githubstatus.com/ [1] https://mrshu.github.io/github-statuses/

> How their terms of service for SLA are legal if they are so different from real world usage of their product?

Because the SLA likely doesn't consider some features of GitHub under the SLA, whereas an outage/issues for a single model is seen as problem on the Third Party page.

Re: Red Squares – GitHub outages as contributions

#67

Post by Anoian »

u_fucking_dork wrote: post #61

Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…

Why cannot both sides be right?

Meaning that the load is crazy high but also that the tech stack and everything else is bad?

Re: Red Squares – GitHub outages as contributions

#68

Post by philipwhiuk »

korrectional wrote: post #20

I don't really understand why this is happening at this scale, it's not like they just became broke and can't afford a proper server... can someone explain?

Most of the outages are actually the unavailability of single AI models, not the core service.

Re: Red Squares – GitHub outages as contributions

#69

Post by nojonestownpls »

lnenad wrote: post #4

The memes are really painful now. I feel for the team that's is trying to survive underwater.

$250k can do a good job of easing meme-induced pain.

"survive underwater" what a joke. Yes, there will be good engineers there who will be sad to see it go this way, but they choose to be there, get paid better than 99% of humanity for that.

Re: Red Squares – GitHub outages as contributions

#70

Post by Anoian »

freakynit wrote: post #63
tealpod wrote: post #60

If anyone wants a aggregated status page for github, cloud & AI services. https://status-page.org/

You can let people organize/filter them into groups based on the stack they use and provide email/discord/slack notifications if any of these form their groups change their status.

That would actually be a product one might buy
Post reply on HN