New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Nobody ever got fired for going with IBM AWS.
Isn't the whole point of cloud services to run your app in multiple availability zones so that you can more easily fail over if one zone goes down?
I thought it was Cisco..
Per Google Cisco is a "Cisco is an American multinational technology conglomerate"
I don't think I've ever heard that about Cisco.
Colocrossing works
I have noticed this shift first hand and it is significant. AWS is still growing, but it isn't sucking all the air out of the room like it was 5 years ago.
The only constant is change.
Crazy stuff can happen in the clouds -- lightning, hail, hurricances, some would say UFOs, too, etc. Clouds can't suck the air from colo space because space is a vacuum.
The bigger difference isn't uptime, but whether or not your LowEndProvider has an SLA. AWS has an SLA for all paying customers, while most providers here don't. We've all seen stories here of servers going down or providers deadpooling and not giving any compensation whatsoever.
But
But
But
This is lowend
Providers need to provide fir the HA/ Backup/ DR
At $7/yy prices
Shit post by @jbiloh
It's not an apples to apples comparison
If one provider in lowendtalk.com experiences downtime does aws or other providers start a comparison?
No.
Real immature @jbiloh
This is place is nothing more but providers paying you the tax and flout rules and constantly shit spam and nothing, literally happens... even your post and comments said it was already in works to get a better solution, and nothing.
As it gets you more clicks... like the half assed serververify.com you built with Ai and vibe coded the shit out and faked reviews and then asking users here to help fix your codename and find genuine suggestions.
Now really tell us how you feel.
Good grief, someone give @plumberg a hug.
Y dont you do the honors?
Nobody is making you use this website. If you don't like lowendtalk, just stop using it.
Well, no system is perfect. Hardware fails, humans fail... it's only a matter of time until something goes wrong.
Oh, and it's always DNS.
amusingly i was reading this https://news.ycombinator.com/item?id=45614922 (Migrating from AWS to Hetzner) just a few days ago and chortling to myself about how it turned out that all the reasons you went big cloud were actually negatives that you can fix by going bare metal.
yea i know i'm exaggerating but humor.
It's surprisingly difficult to build real disaster recovery on any decently sized business across multiple regions. A lot of these issues are people who have everything in us-east-1. It's been years since I did devops, but all our plans for multi-region (and even "multi-cloud" with some things in Azure) always got pushed to the backlog or forgotten about with all the other crap we had to get done. In my three years there, I think we got as far as having full S3 replication to another region ... and it was kinda flaky. (Refactoring terraform is a bitch).
It doesn't help that AWS puts all their latest tools people want to try in that one region. For smaller projects and even startups, I'd say avoid the big players as long as possible. When you start getting locked in, it's difficult to even stand up a second region, much less switch providers.
This is real and it's happening at scale.
I suspect AWS is much more fragile than it seems.
It is.
Quite frankly AWS startup credits are a bad idea: it prevents OVH and DigitalOcean from becoming rivals by winning startups, many of which become big (and others which fail).
AWS is basically IBM at this point: nobody ever gets fired for buying AWS. And we get startups addicted so they don't leave.
Until a new wave of startups skip over AWS for some simpler, cheaper and newer solution. After all, Chase probably uses IBM but PayPal likely uses x86 servers and Robinhood is cloud-native.
Literal billions was lost:
https://arstechnica.com/tech-policy/2025/10/amazons-dns-problem-knocked-out-half-the-web-likely-costing-billions/
And again, less than a week later... WHY IS IT ALWAYS DNS?!?!?
https://abcnews.go.com/Business/wireStory/microsoft-azure-experiencing-outage-due-dns-issue-126985916
AWS uptime? Please, even a Colocrossing backed summer host disappearing with LET users’ funds is more predictable.
Another day and another major outage at the hyperscale clouds. Has been brutal lately.