Wasabi global issues
-
Seems Wasabi is having global issue if any of you are seeing that:
I realise I recommended, and we're also affected, but I don't think size of an organisation is any protection nowadays as any service can be targeted in any way online by determined bad actors.
Best advice is wait it out.
Next best advice is if Cloudron had multi-backup provider options to help cover against issues like this, which inevitably we will when there's any single points of failure relied upon.
-
If I understand it correctly, they were saying that because of some malware content being hosted at one of their servers, their endpoints were blacklisted by major DNS service providers around the world.
Am I correct?
-
@lolliop Sounds like it, which is quite a vulnerability and responsibility for them given they couldn't easily police all content they host.
I imagine the far-reaching consequences of this might mean their domain provider doesn't so quickly respond to abuse takedown notices without liaising with them first.
It does also highlight the weaknesses in the chain with the net and vulnerability to de-platforming tactics using the abuse reports systems being another attack vector everyone has to contend with nowadays and trust in every link in the chain not having their strings pulled unwittingly.
-
@marcusquinn True.
Now it made wonder how the big guys, i.e. Google, Amazon, etc., were able to get away with a similar incidence. I'm certain that their services were used for nefarious purposes at one time or another. I guess they're just too big to fail.
-
@lolliop My guess is an oversight by the domain registrar in handling an Abuse report and that they should have certain domains protected as critical infrastructure that doesn't have automated abuse responses without escalation. I believe many of the other big players are also domain registrars, so more able to self-determine.
-
The latest status says the domain is activated but I guess it will take a while to propagate.
