Google Cloud Suspended Customer's Account 3 Times, for 3 Different Reasons

I also had the same thing when testing Azure personally so I made sure to recommend against using them at every single company I've been at.

He didn't want to (and didn't use for core functionality) - this was a an integration specifically to help customers who already used GCP.

Isn't their business model largely centered around the concept of scaling up business without scaling up staff proportionately? A big part of their innovation was getting people to tolerate nonexistent/automated customer service.

The Register version* is missing one of the worst parts --- this is with active engagement from support, each time. And the automated system(s) kept doing their thing on multiple levels - not just re-suspending the same account for the same reason.

Only pointing it out because that shook me: for years I've been thinking "if only there was active support" or "if only they could flag 'this account is getting screwed by mistake, take no automated action'...and both of those things were there, and that doesn't even help. The flaw is so fundamental :\

* discussion yesterday, on author's original blog post: https://news.ycombinator.com/item?id=45798827

And not increase profits? SOCIALIST!

I wouldn't even use them for personal stuff. Too unreliable.

eBay/Paypal were one of the worst when they were merged. It was so bad I wound up having a new account every 6 months or so. I learned that when they started asking for personal details your chances of being reinstated were nearly zero. The lesson was I had an acct suspended, and they asked for DL, then birth certificate, then a lease, then a power bill, then a phone bill, every time I gave them the document they asked for something else. Then finally they said they needed my passport. I said I didn't have one, suddenly THAT was the only thing that could solve this, and I understood that this was just the plan. They keep asking for different things until you can't provide it or the info they have is wrong and they'll never believe you.

I had to do exactly this with Oracle. They couldn't fix my account to be able to change my billing, but I still had access to my resources. But I couldn't change anything and I figured it was just a sign that breaking my rule of never dealing with Oracle was a bad idea so I shut it down. Then had to cancel the card to get the billing stopped because multiple long calls and chats with CS couldn't get that fixed.

The AWS subreddit regularly has people who can't recover their account because their email's DNS is handled by and the domain is registered… with AWS.