Every service, ranked by real customers

Has used DigitalOcean for years, finds it very reliable and has never needed to contact support because it has always just worked.

Stopped using Railway after security incidents and because prices skyrocketed once there was some traffic; now on cheaper Hetzner servers.

They could not open a support ticket during the outage even as owner and creator of the subscription, getting through automated support agents only to be told to ask their provider to open it.

Liked not thinking about infrastructure on Railway, but recent downtime is a blocker and they are looking at self-hosting.

They had about an hour of trouble with their SQL elastic pool in West Europe where the server was reachable but no tables were accessible.

They saw not only SQL problems but also disconnected virtual machines during the West Europe incident, all of which came back later.

Their AKS VMs were live migrated several times a week, which exposed a Redis client config issue causing latency and pod restarts. After tuning pings and keep-alives they have had no VM freeze in months.

They ran a cluster of 40 then 120 nodes on Azure and hit network backplane flooding, fixed by bigger VMs and then API refactoring. They say Azure documents these best practices poorly.

They found the Azure health history still showed no event for their subscriptions during the West Europe incident and felt the status and health reporting is lacking.

They chose Railway for its managed setup and infrastructure visualizer at a price close to a VPS, and say it is far cheaper than AWS for them, despite its reliability issues.

They saw no problem during the West Europe outage because their Azure SQL server is only privately accessible, which they suspect explains why others were hit.

They had to restart a stuck elastic pool with eight databases during the incident, with SSMS not showing logins and a job looping on authentication.

Their VMs sat on full servers with no capacity, so every small hiccup shuffled the whole rack slowly, and they eventually moved region.

Their Windows VMs crashed right after provisioning with disk hardware errors and a month of work with support, including kernel dumps, got no result. They switched from spot to on-demand VMs at higher cost.

They hit an Azure SQL outage in West Europe where connections failed intermittently and tables could not be listed in SSMS on the primary of their failover group, while the read-only failover copy looked fine.

They could connect to their server but not browse the databases in their Azure SQL elastic pool, and restarting the pool failed with an internal server error while service health showed nothing.

They lost metrics and databases during the West Europe elastic pool outage, a restore failed, and support gave no response for two hours beyond generic automated replies.

For a month their AKS Linux VMs froze together with connectivity issues and support was not useful. Switching from Dasv6 to Dsv7 stopped the freezes but costs more.

They report essentially zero downtime in the 5 years their team has used Render.

AI API key stolen via Railway; an Anthropic alert, not Railway, revealed it, and a spend cap limited the loss.

They lost invoice access entirely, and after weeks support told them to create another subscription for billing. First-line support just follows a script until a senior engineer gets involved.

As a student they used the $300 trial to host a Minecraft server on virtual machines and ended up with a $157 charge. Their billing account is closed and support redirects them to an automated assistant.

Railway is insanely fast to deploy with a nice UI, but security and reliability let them down; switching permanently.

With about a decade in cloud, they ran two startups on GCP and never had a billing or alerting issue.

After an earlier outage they moved their services from Railway to AWS. After the latest incident they cancelled their subscription, saying even the support page would not load.

Their team spent a full day rotating secrets after the Railway incident and lost count of the complaints in their chat.

Beta site on Railway: Gemini key abused for about $2k in two hours, no notice from Railway, deleted all accounts.

Started on Railway because it was easy and cheap, but two years of outages and the breach handling are pushing them off.

On a 7-day Railway trial, could not deploy on day 3 and is not happy.

Moved everything to Cloudflare; Railway's infrastructure stability was not consistent.

API credits drained despite usage limits after the Railway breach, and they could not redeploy for 30+ hours.

Revoked an OpenAI key before it was used, but says Railway has had too many issues and will use a better-known host for sensitive apps.

They had downtime during the Railway incident while they redeployed their app on DigitalOcean, and do not plan to return.

They moved their Rails apps to DigitalOcean Kubernetes a few years ago using the Cuber gem and say it works perfectly.

They use Heroku for all their client work and say elsewhere they have had no issues in about 10 years.

After the Railway incident, migrating to Fly.io was far easier than expected, about 30 minutes.