Postmortem of a Scaleway related not-too-critical downtime
pc-kombo.com
pc-kombo.com
That's better than expected. We've had multiple occasions of waiting greater than 24 hours for any kind of response from their support team for tickets with priority: High.
Including 2 instances where they migrated VMs to new underlying host - thereby changing their IP addresses - without any kind of notification. Was only picked up by our monitoring setup letting us know something was badly broken.
It's the reason we're currently in the process of migrating everything away from Scaleway.
Should have done it sooner, but was hoping they'd get their stuff together. The dropping of ARM64 ended that hope.
Their small DEV-instances seem to be comparable and to be a good alternative to the ARM64 offers, so I'm not sure how sad to be about that going away. It really was not 100% stable. I'll miss the bare metal aspect of the C2 instances though.
> I’m currently betting on AppImage being the best solution for that (starting point so far: a build script that provides ruby) and plan to invest more work there.
A simple Docker install is perfect for this case. Would recommend a try!
And yes, powering down is putting it up for grabs. You also stop paying for it, says the documentation I read afterwards. https://www.scaleway.com/en/docs/instances-shutdown-modes/. I think that's a mistake in the current situation. Harmless when there are enough instances going around, really dangerous now that none are left.