Maybe we should get rid of IPv6 once and for all

Public Cloud
1

From about 20:05 to 23:00 UTC on July 6, there was an IPv6 issue at OVH (intermittent routing or something else).

Obviously I created a ticket before even an incident, likely related, appeared on the OVH maintenance page.

And so I thought, what’s the point of enabling IPv6… since even the main OVH website doesn’t have IPv6.

ipv6-ovh

Why are we still bothering with this when IPv4 is still around? I suggest moving directly to IPv8.

2

IPv6 is great when you deploy virtual machines on a host, or at home when you self‑host certain services (different subnet, dedicated IP per VM, etc.). The fact that each VM can easily have its own public IP is really awesome.
Otherwise, yes, I feel that OVH’s IPv6 is a bit flaky at times...

3

I’d seen this draft; there are many, but I don’t think IPv6 will be abandoned.
Personally, I don’t use IPv6 as long as OVH doesn’t allow moving them off a server/instance.

4

You need to get a /64 on the vRack, and in that case you can allocate your IPv6 to different servers. But vRack is mandatory in this scenario, which isn’t compatible with VPS.

5

You’re absolutely right—if a provider promotes a technology, it’s logical to expect them to use it themselves. However, the reality for large service providers is that migrating a complex infrastructure, such as the web and support systems, is a process that’s done in phases and with care.

They prioritize stability for their customers (usually :sweat_smile: ), so sometimes their own ‘showcase’ is updated at the end of the process.

6

Hi.
This noon also (13:29 Paris) IPv6 packets are not passing AS16276 :

$ sudo traceroute6 -n gitlab.com
traceroute to gitlab.com (2606:4700:90:0:f22e:fbec:5bed:a9b9), 30 hops max, 80 byte packets
1 2001:41d0:302:1100::1 1.295 ms 1.206 ms 1.156 ms
2 fd00::ffe 1.674 ms 1.623 ms 1.574 ms
3 2001:41d0:0:1:3::aabf 2.577 ms 2.524 ms 2.478 ms
4 2001:41d0:0:1:3::aac0 2.427 ms 2.381 ms 2001:41d0:0:1:3::a73e 2.332 ms
5 * * *

$ sudo traceroute6 -n ipv6.google.com
traceroute to ipv6.google.com (2a00:1450:4007:809::200e), 30 hops max, 80 byte packets
1 2001:41d0:302:1100::1 0.480 ms 0.422 ms 0.384 ms
2 fd00::ffe 0.353 ms 1.099 ms 1.060 ms
3 2001:41d0:0:1:3::aabf 1.030 ms 0.999 ms 0.969 ms
4 2001:41d0:0:1:3::aac0 0.938 ms 0.898 ms 2001:41d0:0:1:3::a73e 0.856 ms
5 2001:41d0:0:1:3::a13e 1.350 ms * *
6 * * *

Grrrr...