Scheduled maintenance on their network, notified 1 week in advance. "No action required", they said. My IPv6-only VPS stopped to be reachable from outside and I could not get the web console. I opened a ticket and after some ineffective suggestions (trying to switch the machine on and off or go into recovery mode) as I was sure there was a problem in their new network, I found a workaround by myself: buying a floating IPv4 address, attaching it to the machine and using Cloudflare for IPv6. Today, after 16 days since the high priority ticket has been created, I got a reply with a solution: create a new instance, one month of refund.
Tip: there are many good alternatives to be considered even if you are looking for <= 5 $ VPS that have way less shortcomings and many times the cheapest VPS on Scaleway is above 10 $/month because of prolonged shortages. I would consider it only for hobby projects which require a lot of network traffic (VPS network is not capped).
The images run on the machines might be binaries licensed from vendors which are ARM. Have fun calling every vendor and saying "Yeah, I know you completed your contract with us 4 years ago, but would you mind recompiling the whole project as x64?".
But really the answer is "enough people for Amazon to invest heavily in manufacturing custom CPUs"
Scaleway just decided that you're not shipping any code today, you're retooling your configuration.
I don't think it's that bad, but it's not something a platform you trust to run anything valuable on would ever do.
Scaleway gave zero notice of the removal of the ability to start ARM64 instances. That means if you had a CI pipeline or automated system which started those instances, it just broke on you. Hope your clients don't mind random downtime!
You're going to have to port all your code to x64 or another cloud provider to restore service. That could take weeks. Weeks of downtime!
Don't touch Scaleway, ever, especially if you want an SLA.