←back to thread

Days since last GitHub incident

(github-incidents.pages.dev)
212 points AquiGorka | 8 comments | 11 Dec 25 16:52 UTC | HN request time: 0.013s | source | bottom
1. TuxPowered ◴[11 Dec 25 19:15 UTC] No.46235798[source]▶
It should always be at 0, because GitHub is unreachable over IPv6, which in 2025 should be considered an incident.
replies(3): >>46236056 #>>46236428 #>>46239223 #
2. tonymet ◴[11 Dec 25 19:32 UTC] No.46236056[source]▶
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.

replies(2): >>46239172 #>>46241141 #
3. fragmede ◴[11 Dec 25 20:06 UTC] No.46236428[source]▶
"yeah but when I turn on ipv6 everything breaks"
4. pas ◴[12 Dec 25 00:03 UTC] No.46239172[source]▶
just a few hours ago we found a pretty nice residential desktop use case for proper v6 (with prefix delegation), due to no need for NAT the old router (2013) became less of a bottleneck!
replies(1): >>46241322 #
5. doubled112 ◴[12 Dec 25 00:08 UTC] No.46239223[source]▶
I haven’t had a residential ISP that provided IPv6 yet.
6. kalleboo ◴[12 Dec 25 05:27 UTC] No.46241141[source]▶
Aren't there serveral hosts now where IPv6 access is included but you have to pay for each attached IPv4? E.g. AWS and Hetzner
replies(1): >>46241314 #
7. tonymet ◴[12 Dec 25 06:04 UTC] No.46241314{3}[source]▶
Yep
8. tonymet ◴[12 Dec 25 06:05 UTC] No.46241322{3}[source]▶
Double check (I mean by remote port scan) that your firewall is working. I’ve seen routers with no IPv6 firewall . And it actually matters