6 ms·
And still, in the year of our lord 2026, GitHub does not support IPv6. https://github.com/orgs/community/discussions/10539 https://github.com/orgs/community/di
by rtdq 6mo ago
And still, in the year of our lord 2026, GitHub does not support IPv6.
https://github.com/orgs/community/discussions/10539 https://github.com/orgs/community/discussions/10539
- growse 6mo agoA non-trivial minority of the time, they don't support IPv4 either!
- hsbauauvhabzb 6mo agoWhat? One nine isn’t good enough for you?
- lambda 6mo agoExcuse me. Zero nines. Or two nines if you relax your definition of where they are in the number. https://infosec.exchange/@0xabad1dea/116334321751266751 https://infosec.exchange/@0xabad1dea/116334321751266751
- bdangubic 6mo agowe shut down our production every day from 2pm till 5pm for a siesta :)
- Zancarius 6mo agoYou jest... (but probably not!) I remember when I was first using my alma mater's online sign up for classes in the very early 2000s, their class sign up site had office hours.
- AlienRobot 6mo agoExcuse me, but I see 4 nines. 95 incidents in last 90 days, 89.91% uptime.
- fogllgldl 6mo agoYou guys have nines?
- wiredfool 6mo agoPersonally I’d look for the coveted 5 eights uptime.
- MarsIronPI 6mo ago66.6% uptime anyone?
- doubled112 6mo agoStill better than five eighths.
- wildylion 6mo agoOnly if it's Australia.
- Ekaros 6mo agoAs long as it is after the decimal separator I can try for that...
- sidewndr46 6mo agoshould we try going back to IPX ?
- MikeNotThePope 6mo agoOnly if we're bringing back Token Ring, too.
- synalx 6mo agoThat might be challenging, I hear people are pretty short on tokens these days.
- MikeNotThePope 6mo agoThere's only one token! It's just very popular.
- bluGill 6mo agoArcnet for me.
- sidewndr46 6mo agoWhile we're at what about older physical layers? Coaxial based stuff seems cool in 2026
- jonhohle 6mo agoIsn’t that what MoCa is for?
- rayiner 6mo agoIsn’t twinax just “I heard you like coax so I put coax in your coax.”
- sidewndr46 6mo ago
- CupricTea 6mo agoGitHub is at the point where it immediately rate limits me if I try to look at a project's commit history without being logged in, as in the first time I even open a single URL to the commit history, I get "Too Many Requests" from GitHub thrown at me. I don't know if my work's antivirus stack is causing GitHub to be suspicious of me, but it's definitely egregious.
- vhcr 6mo agoMy theory is that they rate limit that URL aggressively due to AI scrapers. At this point it's faster to just clone the repo and do your searching locally.
- colechristensen 6mo agoYour work is probably all exiting through the same IP, you competing with others on the same IP is causing the rate limit.
- CupricTea 6mo agoI've considered this, but the company is small enough that the number of people who would be on GitHub at any moment (instead of our internal git forge) can be counted on one hand, and when I'm the first one there in the morning it still rate limits me.
- growse 6mo agoMaybe your company's ISP is CGNat'ting you?
- NewJazz 6mo agoDo you have any on-prem cicd jobs that access github? Our's kept failing, had to move over to the ECR release of some stuff.
- colechristensen 6mo agoHm, I've also noticed sites being more aggressive about verifications after I started using LLMs locally. They think I'm a bot (which... fair), even on completely unrelated sites I seem to be getting prompted for human verification much more often.
- nailer 6mo agoIPv1, IPv2, and IPv3 were very early experimental versions of the Internet Protocol developed in the 1970s during the ARPANET era (the precursor to the modern internet). Has anyone tried to find out if GitHub is reliable on those?
- sandeepkd 6mo agoCame here to exactly check on this to see if there are any changes on Github side too
- globular-toast 6mo agoDo we know any technical reason for this? Or are we left to think this is somehow a political thing?
- denkmoon 6mo agoOutdated beliefs probably. When I talk about v6 support in our b2b saas, PM laughs and says nobody uses that shit. Big tech are massive laggards on this funnily enough.
- ViscountPenguin 6mo agoIt's because big tech is USA based mostly, where there's still a glut of ipv4 available.
- FuriouslyAdrift 6mo agoIPv4 was exhausted at ARIN in 2011. Last time I bought a /24 on the open market, it was around $6k. I assume it is much more, now.
- Dylan16807 6mo agoIt's close to that right now. Prices more than doubled as covid set in, then dropped back down to about where they were before.
- paulddraper 6mo agoWhere can I get it, asking for a friend?
- 10000truths 6mo agoDefinitely not for the biggest ones. Google and Meta have so many machines in their data centers that IPv6 addressing becomes a technical necessity due to the risk of exhausting the RFC 1918 address space. Naturally, they were early adopters of IPv6.
- jeroenhd 6mo agoThey supported IPv6 for a short time, but then stopped their experiment. An excellent reason to move away from Github, I find.
- literalAardvark 6mo agoI've been there. Management was fine with the testing but it added too much overhead for nearly no benefit to us. One more thing to troubleshoot at 3 am, one more thing to teach to a disinterested tier 1 support team, one more thing for Chrome to be weird about, hundreds more rules to manage in a hostile load balancer, logging tools that don't understand ipv6. Turned it off. End customer asked why the site got a little slower (CGN) and when we can turn ipv6 back on. As far as I know it's still on the backlog.
- nextaccountic 6mo agoThat's why ipv6 migration should be government mandated. Then it becomes just the cost of doing business
- deleted 6mo ago[deleted]
- throw0101a 6mo agoFacebook is (AIUI) 100% IPv6-only on their internal network, and has been for many years: * https://engineering.fb.com/2017/01/17/production-engineering/legacy-support-on-ipv6-only-infra/ https://engineering.fb.com/2017/01/17/production-engineering... * https://www.internetsociety.org/blog/2014/09/facebook-launches-ipv6-only-data-cluster/ https://www.internetsociety.org/blog/2014/09/facebook-launch... IPv4 is actually the "leftover" stuff they have to deal with at the front end. But they are an eye-balls heavy service, with a lot of mobile devices, which also tend to be IPv6-native.
- tialaramex 6mo agoIt also just takes actual policy will. Somebody has to actually say "No" when the supplier who promised an IPv6 product says afterwards actually they meant IPv6 "ready" and they should have put an asterisk because really only the next version will be "ready", and er, so the product they've delivered doesn't actually work with IPv6 but that's fine right? "No". Not every human is psychologically prepared to do that. They want to acquiesce, to go along to get along, you need somebody to be firm. "No".
- sschueller 6mo agoJust found this little site. https://isgithubipv6.web.app/ https://isgithubipv6.web.app/ Maybe we shouldn't even measure percentage adoption and instead just if github has finally adopted..
- tonymet 6mo agonice!
- Landing7610 6mo agoOur university has bad problems with ipv4. Every few days you'll notice some websites being unreachable, including github. Although with their uptime recently, you never know who's to blame...
- missingdays 6mo agoMost websites still don't
- farfatched 6mo agoGitHub should absolutely support IPv6, but until then... transip.eu provide IPv6 addresses which transparently proxy to github.com: https://www.transip.eu/knowledgebase/5277-using-transip-github-ipv6-proxy https://www.transip.eu/knowledgebase/5277-using-transip-gith... You'll need to update your DNS server to include those as AAAA records. Do providers like NextDNS or RethinkDNS allow these sorts of overrides?
- voltagex_ 6mo ago>The Github IPv6 Proxy can only be used for traffic to Github using a VPS from TransIP which uses IPv6.
- farfatched 6mo agoGood spot. Sorry to disappoint!
- ignoramous 6mo agordns dev here > Do providers like NextDNS or RethinkDNS allow these sorts of overrides Not on the resolver, but on the Android client (Rethink DNS + Firewall) we do (if enabled) manipulate DNS answers to implement an opportunistic 464xlat (over Kasper Dupont's public relays [0]). [0] https://github.com/celzero/firestack/blob/c10c155464e0d4a81a1e4e0204c6b15914f73b43/intra/ipn/exit64.go#L257-L312 https://github.com/celzero/firestack/blob/c10c155464e0d4a81a...
- jiggawatts 6mo agoThe irony of this is that pretty much all they'd have to do to enable IPv6 support is to use Azure Front Door as their CDN. Or... use any other CDN, they pretty much all default to providing IPv6!
- aetimmes 6mo agoLast I checked, they're on Fastly who already support IPv6.
- throw0101a 6mo ago> And still, in the year of our lord 2026, GitHub does not support IPv6. Especially given that it is now owned by Microsoft, which has been working on IPv6-only (at least on their corporate network) for almost a decade: * https://blog.apnic.net/2017/01/19/ipv6-only-at-microsoft/ https://blog.apnic.net/2017/01/19/ipv6-only-at-microsoft/ * https://www.arin.net/blog/2019/04/03/microsoft-works-toward-ipv6-only-single-stack-network/ https://www.arin.net/blog/2019/04/03/microsoft-works-toward-...
- rekoil 6mo agoI mean Azure doesn't really support IPv6 well either for a lot of the big-ticket services.
- fogllgldl 6mo agoMore importantly, it doesn’t support uptime well.
- sidewndr46 6mo agowe could meet in the middle: Azure support IPv6 with 0% uptime
- Twirrim 6mo agoThat seems weird given NIST, and the US Government, set a requirement for IPv6 Only back several years ago, and it sort-of became part of the JWCC requirements (It wasn't in the requirements, IIRC, because it came after those were set, but the government wouldn't fully approve use for JWCC if you didn't meet it). You'd think they'd have sprinted for that feature as fast as they could go.
- bigfatkitten 6mo agoMicrosoft gets special treatment. USG also set a whole bunch of security requirements under FedRAMP that Microsoft can never meet, but they received an ATO anyway because they are so heavily entrenched in government.
- jermaustin1 6mo agoSame with Twilio. We have an internal server that does system alerts. We recently moved it to an IPv6 only host, and a few weeks went by and noticed there were no longer receiving alerts. Turns out we could not connect to Twilio's API which is IPv4 only.
- tbrownaw 6mo agoSo zero validation after that change?
- vlovich123 6mo agoZero observability and alerting too. Seems like they’re planning to be a productive future member of that team.
- jermaustin1 6mo agoWho? The infrastructure team that did the move didn't even tell anyone. They were decommissioning old servers, and moving the VMs to new hardware. I'm just a lowly developer that had to troubleshoot why SMSes stopped going out.
- vlovich123 6mo agoObservability and alerting is pretty standard devops. Both the dev and infrastructure teams dropped the ball here. But at least as part of remediating this you added alerting to make sure you’d notice when your twillio connection fails in the future, right?
- jermaustin1 6mo agoEven better, infrastructure enabled IPv6, and the issue was closed. In corporate software development, we work the tickets assigned, and keep our KPIs up so that we don't face the wrath of the bean counters.
- 6mo ago
- strenholme 6mo agoKinda sorta. github.com doesn’t have an IPv6 address. github.io does have an IPv6 address. Indeed, one workaround for getting rate limited when using a carrier NAT with github.com is to have a github.io page and pull data from github.io instead of github.com. Edit: About a decade ago, all of my hosting had full IPv6 support, and I tried to move over to IPv6. However, there was an issue with Letsencrypt certs not validating over IPv6, so I made my web pages IPv4 only. Recently, I gave IPv6 a go again, and the cert issue has been fixed, so now my webpages finally have both IPv4 and IPv6 addresses.
- GoblinSlayer 6mo ago>github.io does have an IPv6 address Are you sure? I don't see it. Name: github.io Addresses: 185.199.111.153 185.199.110.153 185.199.108.153 185.199.109.153
- strenholme 6mo agogithub.io doesn’t have an IPv6 address. {name}.github.io does, e.g. mats-winther.github.io resolves to 2606:50c0:8001::153:
- codethief 6mo agoAt least HN supports IPv6 now, which I remember was not the case last time I checked.