Scaleway has terrible hardware and is not reliable at all. You can turn off an instance and not be able to turn it on again because they've run out of resources. IPv6 addresses change every time your instance is stopped and started.
Online.net owns scaleway so I assume their level of service is similar but with better hardware.
First, you only get a /127. Second, IPv6 is not activated by default, and for a good reason: when you do activate it, basic things like a apt-get update of a their vanilla distribution are broken.
Basically, their IPv6 peering seems so bad you can't even ping6 some ASN.
Practical example: on their Amsterdam DC, I couldn't even reach ftp.nl.debian.org (and before you ask, DNS worked just fine - I got the correct AAAA records)
When I asked for explanations and provided them a detailed ping6 and traceroute analysis showing where the problem was (and the same analysis from another server I had nearby that confirmed the problem was on online.net end), I was told to try the "rescue mode".
Lol no. I tried another company instead.
I've had a handful of nodes on their $20 tier for 10+ years, and I think I've had two or three unannounced reboots in that time.