- Their network ranges are very likely to be blacklisted by essentially everything that employs blacklisting.
- The disks/volumes should be treated as ephemeral. There is no redundancy.
- Their SLA is a joke. I had a mailserver crash in the night and not booting, sent a ticket in the morning, resolved next evening. "SLA does not apply because problem was not a power
failure". There is no SLA anywhere in their T&C, it's just mentioned on their marketing site without any detail.
- Turning off systems takes 30+ minutes. They mirror the entire disk to their storage system (very slowly) and free the entire machine (and you're still billed for it). This even applies if you resize the machine or add a volume. Turning on systems is a bit faster, but still in the 20+ minutes area. Oh, and you have a chance of not being able to boot again because although yes, you are billed, they're not reserving a machine for you.
- Can't pick own kernel on some machines. Arbitrary restrictions on number of volumes / addon services that aren't documented anywhere. They tell you when you try to hit save.
- Their network stack is crap. No machine gets an assignable public IP. If you attach an IP you still have the private IP on the NIC, but some firewall NATs traffic to you. It's also just slow in general.
First of all, thanks a lot for your feedbacks, we greatly appreciate you taking time to provide details about your experience with our platform!
I would make sure to understand the problems you are describing as most of the issue you faced seems to be related to our first generation of platforms.
I will try to provide a factual update of the situation:
1 - Are you speaking of SMTP? We have suffered a lot from fraudster in the past (~2017) but we have now more strict process toward SMTP opening and a complete team dedicated to fighting abuse.
2 - That's totally true for all generations prior to the General Purpose range. We do not guarantee local data and our users are responsible of doing backups. The new General Purpose Range is backed by replicated local storage but this doesn’t mean we can 100% guarantee the storage as simultaneous SSD failure do happen. We now have a backup feature and support hot snapshots, which means backup can be performed with no downtime.
3 - The answer you’ve got to your issue is inappropriate and abnormal as we provide refund toward outages and a power failure is of course an outage. I would like to further investigate if you can share more information in private.
4 - I’m not sure to follow you here. If you archive your server, we will indeed save your server to long term storage. You are only billed for the storage when your server is archived, not for the machine itself. A new server starts in about a minute but servers with large volumes might indeed take longer as we do copy your data locally on the hypervisor to reduce
5 - Our C1 and C2 BareMetal server indeed have a network served kernel. On all new server range, including our START, GPU and General Purpose instances, the kernel is locally installed and is the distribution provided kernel.
6 - There is no firewall NAT but a stateless NAT system which lets us transparently migrate IPs between servers in one API call. We have no offer providing less than 100Mbit/s with one of the largest network backbone capacity in Europe. Our network map is available online (http://netmap.scaleway.com/), we have an open peering policy and over 5Tb/s of network capacity. If you have specific destination with bandwidth issue, I would be happy to let our network team investigate as I’m pretty sure we have no internal congestion.
Source : I'm managing the Compute Scaleway business since 2014, so I'm aware of the issue we faced in the past and which one are now resolved.
I’m available on twitter (@yann_eu) if you’re available to discuss the issue you faced as I truly believe our last platform generations solve the issue you encountered.
To add to the network stack comment - they assign _single_ IPv6 address to your server. Not a /64 block, just a single /128 address. I have no idea what they were thinking.
Also, that single IPv6 address changes if you shut down then start up the server again. eg it's not a stable address, like the IPv4 one is.
Can be a problem, until you figure out what's going on. ;)
To add to your list, their C1 instances do not support IPv6. And never will because something something routers incompatible. It’s a shame.