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

Days since last GitHub incident

github-incidents.pages.dev

Post reply on HN
Print view View original

91–100 of 142 posts

Re: Days since last GitHub incident

#91

Post by llbbdd »

smcleod wrote: post #87
colechristensen wrote: post #41

Earlier quoted context omitted.

An NVIDIA DGX Spark is $4000, pair that with a relatively cheap second box to run GitLab in the corner and you would have pretty good local AI inference setup. (you'd probably have to write a nontrivial amount of software to get your setup where you want) The local models are just right on the edge of being really useful, there's a tipping point to where accuracy is high enough so that getting things done is easy vs…

The DGX Spark is not good for inference though it's very bandwidth limited - around the same as a lower end MacBook Pro. You're much better off with a Apple silicon for performance and memory size at the moment but I'd recommend holding off until the M5 Max comes out early in the early as the M5 has vastly superior performance to any other Apple silicon chip thanks to its matmul instruction set.

Oof, I was already considering an upgrade from the M1 but was hoping I couldn't be convinced to go for the top of the line. Is the performance jump from the M# -> M# Max chips that substantial?

Re: Days since last GitHub incident

#92

Post by tonymet »

TuxPowered wrote: post #88

It should always be at 0, because GitHub is unreachable over IPv6, which in 2025 should be considered an incident.

mobile adoption is high, desktop (residential and corporate) is still quite low.

I'm a big advocate for github to add ipv6 support , but let's not pretend it's critical for their business.

Re: Days since last GitHub incident

#93

Post by 0cf8612b2e1e »

Oakwhisper wrote: post #71
geophph wrote: post #12

Is GitHub deployed using GitHub Actions?

I was talking with some GH sales/marketing engineers last month and they said it deploys with actions, but they have a custom deploy queue

It is a fun bootstrapping problem. How do you firewall enough dedicated resources to stand up your infrastructure if you dogfood your own product. Probably insidiously easy to have a dependency on the production service.

Re: Days since last GitHub incident

#94

Post by llbbdd »

nightpool wrote: post #86
llbbdd wrote: post #6

Earlier quoted context omitted.

I don't work at Github but I'd read here recently that they've been undergoing a herculean migration from whichever cloud provider they were on to Azure since their Microsoft acquisition, and that it coincides with an increase in outages. I'm guessing that the solution here was probably just to not do that and it's too late.

They weren't on any cloud provider previously. They famously had their own "metal cloud" of managed servers with everything being containerized and managed by Kubernetes. It seemed like it's worked pretty well, especially for their complex git operation tasks which had specific hardware requirements, but the official word is that apparently they're running into scaling limits with finding new datacenter capacity.

Yikes, that's worse, I thought the migration was at least a little politically motivated to reduce a dependency on a competitor like AWS or something. It's not exactly a great advertisement in any case to know that bare metal was more reliable for them than their own infrastructure when they now own it all the way through.

Re: Days since last GitHub incident

#95

Post by shakna »

cassidoo wrote: post #74
matheusmoreira wrote: post #61

I've been getting some weird cryptocurrency spam notifications on GitHub and they can't be cleared for some reason. Blue dot is gonna be there forever apparently. Some users made an issue out of it but nobody cared to fix it.

This should have been fixed here: https://github.blog/changelog/2025-12-04-notifications-trigg... Are you still seeing it, would you mind checking? Our team will get on it if so.

I had the same. The dot is cleared on the mobile site. It is present on the desktop site.

Re: Days since last GitHub incident

#97

Post by shakna »

0cf8612b2e1e wrote: post #93
Oakwhisper wrote: post #71

Earlier quoted context omitted.

I was talking with some GH sales/marketing engineers last month and they said it deploys with actions, but they have a custom deploy queue

It is a fun bootstrapping problem. How do you firewall enough dedicated resources to stand up your infrastructure if you dogfood your own product. Probably insidiously easy to have a dependency on the production service.

An Azure outage took out Office365 the day before CrowdStrike happened. I would not trust Microsoft to get this balance right.

Re: Days since last GitHub incident

#98

Post by llbbdd »

blahyawnblah wrote: post #26
llbbdd wrote: post #6

Earlier quoted context omitted.

I don't work at Github but I'd read here recently that they've been undergoing a herculean migration from whichever cloud provider they were on to Azure since their Microsoft acquisition, and that it coincides with an increase in outages. I'm guessing that the solution here was probably just to not do that and it's too late.

Yes I would image the issues are due to doing a migration period. Not the fact that it's moving to Azure in and of itself.

I won't blame Azure directly without a direct reason to, but as a developer often in the market for cloud providers it's definitely not the most reassuring that they're seemingly having so many migration pains.

A bit of an aside, I've only personally used Azure on one project at one company but their console UI had some bizarre footguns that caused us problems more than once. They have a habit of hiding any controls and options that your current logged-in user doesn't have permissions to use. In some cases that manifested as important warnings or tools that I wasn't even aware of (and were important to me!), but the owner of the company and other global admins could see. AWS, at least for a lot of the services last time I used it, was comfortable greying most things out with a tooltip telling you your user is missing X permission, which was way more actionable and the Azure version gave me whiplash by comparison.

Re: Days since last GitHub incident

#100

Post by [deleted] »

loloquwowndueo wrote: post #60
echelon wrote: post #43

Earlier quoted context omitted.

For any ESL folks here - "Friendly reminder" is typically used for reminding people of common knowledge. Especially for beneficial but inconvenient things that some or most people neglect to do, either because they're annoying, inconvenient, or time consuming. Things for which busy people might need a "wink wink, nudge nudge". Friendly reminder to floss. Friendly reminder to have your cancer screening. Friendly remin…

You’re assuming that no native speaker is unfamiliar with the idiom and also that no ESL speaker is familiar with it.

[deleted]
Post reply on HN