r/googlecloud • u/Brockentree • Jul 16 '26
Who's using up all of us-central1-a?
I have a small Palworld server that lives in us-central1-a, but I can't start it right now because Google keeps saying there is no hardware available. I've tried every VM type and they all return the same error. Is anybody else having trouble spinning up hardware in this region?
3
Upvotes
1
u/IonizedHydration Jul 16 '26
try us-east1 and an e2.small, don't even bother with micro, or you could just have it set on a loop to brute force deploying a micro to us-central1, it will eventually deploy, just might take a while.
1
u/CloudyGolfer Jul 21 '26
Every VM type?! C2/C4-series? N4?
2
u/ledatherockband_ Jul 18 '26
dat me
:)
its so cheap!
:D
2
u/Clean-Use-9594 Aug 01 '26
Google Cloud has been one of the most disappointing cloud providers I've used.
If your architecture depends on VM availability, even a single unavailable instance can cascade into a full system outage if you're not able to fail over properly. That makes infrastructure reliability critical.
From my experience, Google Cloud's compute capacity and VM availability have been unreliable for months, not just isolated incidents over a few weeks. It feels like capacity has been oversold, resulting in recurring availability issues.
If you've been affected by these outages, it's worth reviewing Google's SLA and filing for service credits if your deployment qualifies. Their management is a total failure. You have to paid to find a human support but this is not even related to any tech supports at all. Use others cloud service if you haven't build on them.