I'm not a was costumer. What's their usual SLA?
this post was submitted on 20 Oct 2025
420 points (98.8% liked)
Selfhosted
52401 readers
1502 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Why do we place so much reliance on one mega company? This level of importance. It should be seized by the government.
It should be seized by the ~~government~~ people and mercilessly decentralized.
Agree
AWS aggressively pursues high priced and years-long spending commitments with large customers, and they incentivize it with huge discounts for doing so.
And when AWS does this they intentionally incentivize these large customers to migrate existing workloads away from other cloud service providers as well, going so far as to offer assistance in doing so.
And when they hit their end inevitable enshittification, what then?
At that point you're completely invested in their ecosystem and it'll cost you triple to get out.
IbM has entered the chat
Way above my pay grade! I would never suggest or support making such agreements, but I also don't want to be in a position where I'd even be asked, so I'd just sit back with a bowl of popcorn
load more comments
(12 replies)
according to that page the issue stemmed from an underlying system responsible for health checks in load balancing servers.
how the hell do you fuck up a health check config that bad? that's like messing up smartd.conf and taking your system offline somehow
Well, you see, the mistake you are making is believing a single thing the stupid AWS status board says. It is always fucking lying, sometimes in new and creative ways.
I mean if your OS was "smart" as not to send IO to devices that indicate critical failure (e.g. by marking them read-only in the array?), and then thinks all devices have failed critically, wouldn't this happen in that kind of system as well..
I hate how Signal went down because of this... Wish it wasn't so centralised.
I have been able to use Signal like any other day. I haven’t seen any disruption in sending or receiving.
For me it was not possible to send or receive messages for a couple of hours.
My friend messaged me on Signal asking if Instructure (runs on AWS) was down. I got the message. That being said, it's scary that Signal's backbone depends on AWS
Why is this scary? That's what e2ee is for, so that no one besides your recipient can view the contents of a message. It does not matter which server is used. If anything for a service like Signal, you want a server with high availability like AWS, Azure, Google Cloud or Cloudflare.
load more comments
(2 replies)
Started moving to Element/Matrix this weekend when I attended a protest and wanted to have some kind of communication, but also wanted to leave my primary phone at home. I was using a de-googled android fork and an e-sim, but being a data-only e-sim, I couldn't use Signal due to the phone number requirement.
Annoying to have try to get contacts to get another app, but at least it's decentralized and comes with the option of being self-hosted once I'm ready to tackle that.
Hey, note that you can use mautrix-signal to access your Signal account within Element on this phone.
@MrMcGasion @Sunny Come to the dark side (xmpp, and jmp.chat) and get decentralized messaging and SMS support with that data-only sim!
@Sunny@slrpnk.net already has an XMPP account, as that is included in every slrpnk.net account automatically. It is very easy to set that up for most Fediverse software, and the user id is identical between Fediverse and XMPP.
Oh damn i did not even know about this! I will defo have a play around with this tomorrow, how very neat!
However, it isnt me im really worried about in the grand picture, its family and friends. It was already difficult enough to convert them to using Signal.
load more comments
(1 replies)
that is an understatement 😂
It's wild that these cloud providers were seen as a one-way stop to ensure reliability, only to make them a universal single point of failure.
Well companies use not for relibibut to outsource responsibility. Even a medium sized company treated Windows like a subscription for many many years. People have been emailing files to themself since the start of email.
For companies moving everything to msa or aws just was the next step and didn't change day to operations
People also tend to forget all the compliance issues that can come around hosting content, and using someone with expertise in that can reduce a very large burden. It's not something that would hit every industry, but it does hit many.
But if everyone else is down too, you don't look so bad 🧠
One of our client support people told an angry client to open a Jira with urgent priority and we'd get right on it.
... the client support person knew full well that Jira was down too : D
At least, I think they knew. Either way, not shit we could do about it for that particular region until AWS fixed things.
load more comments
(7 replies)
universal single point of failure.
If it's not a region failure, it's someone pushing untested slop into the devops pipeline and vaping a network config. So very fired.
Apparently it was DNS. It’s always DNS…
load more comments
(17 replies)
view more: next ›