Yearly reminder that github still does not have an IPv6 address (2023)

Comments

• GoodKingElliot@feddit.uk ⁨1⁩ ⁨year⁩ ago

  comment from the forum:

  New ISPs in my country are IPv6-only because there is no new IPv4 space to be provided to them. They do have a over-shared IPv4 address by CGNAT but due to the oversharing, it is unstable and not rare to be offline. For these companies, the internet access is stable only in IPv6.

  Thinking about the server-side, some cloud providers are making extra charges for IPv4 addresses (e.g.: Vultr.com) so most of the servers in my company are IPv6-only. Cloning github repositories is very cumbersome due to the lack of IPv6 support and this issue affects me and my team mates on a daily basis.

  The math is simple: there are 4.88 billion internet users in the world but the IPv4 space only provides 4 billion addresses. It’s over: IPv4 is obsolete and is provided in a legacy mode. Current applications and services must be IPv6 enabled otherwise it should be seen as obsolete. For that matter, Github.com is an obsolete service because it relies on obsolete technology as IPv4.

  source

  • VonReposti@feddit.dk ⁨1⁩ ⁨year⁩ ago

    Funny how different situations can be. I can’t get an IPv6 address unless I pay for insanely expensive business tiers.

    source

    • Mubelotix@jlai.lu ⁨1⁩ ⁨year⁩ ago

      I had a very small cheap ISP in France (Quantic Telecom) and they didn’t monitor their network for ipv6 issues. I had to report problems myself every other week. They had less than 90% uptime in 2023, so I ended up getting a refund

      source
    • orangeboats@lemmy.world ⁨1⁩ ⁨year⁩ ago

      The IPv4 exhaustion is far more gnarly in developing countries. Something on the scale of hundreds of people sharing one IPv4 address.

      If I want to get a public IPv4 address from my ISP, I have to spend extra. Some ISPs in my country simply don’t give public IPv4 addresses anymore. They have completely exhausted their pool.

      source
  • Sigmatics@lemmy.ca ⁨1⁩ ⁨year⁩ ago

    Roasted

    source
  • Kissaki@feddit.de ⁨1⁩ ⁨year⁩ ago

    I wonder if they ever contacted github support, and what their answer was - rather than only posting on a public forum github doesn’t feel compelled to answer or make official responses to.

    source
• lowleveldata@programming.dev ⁨1⁩ ⁨year⁩ ago

  How hard is it to support IPv6? Does it require new hardware?

  source

  • knower@lemmy.blahaj.zone ⁨1⁩ ⁨year⁩ ago

    I used to study networking, albeit at a pretty beginner level. IPv6 has been around for nearly 30 years at this point, so I’d be surprised if the hardware github uses doesn’t support it. The impression I got was that it’s pretty easy to extend an IPv4 address space so there isn’t any rush to make a large scale move to IPv6 everywhere.

    source
• eternaldeiwos@lm.qtt.no ⁨1⁩ ⁨year⁩ ago

  Microsoft aren’t exactly big on implementing “the latest” stuff. Not at a keyboard currently but I’d be willing to bet GH doesn’t support TLS1.3 either.

  source

  • FredericChopin_@feddit.uk ⁨1⁩ ⁨year⁩ ago

    here

    source

    • atheken@programming.dev ⁨1⁩ ⁨year⁩ ago

      Here: www.ssllabs.com/ssltest/analyze.html?d=github.com

      source

      • -> View More Comments
• kresten@feddit.dk ⁨1⁩ ⁨year⁩ ago

  Does gitlab.com have it?

  source

  • kelvie@lemmy.ca ⁨1⁩ ⁨year⁩ ago

    Name:   gitlab.com
    Address: 172.65.251.78
    Name:   gitlab.com
    Address: 2606:4700:90:0:f22e:fbec:5bed:a9b9
    

    source
• astral_avocado@programming.dev ⁨1⁩ ⁨year⁩ ago

  I’ve talked to several network engineers over the years about IPv6, engineers that worked just about as hands on with actual production infrastructure as you can get. And they all said that IPv6 would likely never be fully adopted.

  source

  • Wats0ns@programming.dev ⁨1⁩ ⁨year⁩ ago

    But why ?

    source

    • astral_avocado@programming.dev ⁨1⁩ ⁨year⁩ ago

      I am not a full network engineer so take my opinion with a grain of salt. From what I understand, NAT with IPv4 works really really well to mitigate IPv4 address exhaustion. Then there’s an issue with the amount of extra processing switches and routers need to do IPv6, we’re going from 32 bits to 128 bits which is a huge increase and for switches and routers that are handling packets as fast as technically possible with a low amount of resources typically, that’s a not insignificant hurdle.

      It’s just easier to do IPv4 in every way, plus that’s what the world’s been using and is used to.

      source

      • -> View More Comments
    • whoisearth@lemmy.ca ⁨1⁩ ⁨year⁩ ago

      My understanding is it’s no longer that critical. The sky is no longer falling on IPv4

      source

      • -> View More Comments
• wagesj45@kbin.social ⁨1⁩ ⁨year⁩ ago

  Neither do I.

  source
• suckmyspez@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Ok 🤷‍♂️

  source