Bleeping Computer reporters noted that the Wasabi cloud service, which successfully competes with Amazon S3 (due to lower prices and no fees for outgoing traffic or API usage), has experienced a serious failure. Earlier this week, Wasabi users unexpectedly discovered ( 1 , 2 , 3 ) that they could not access their buckets and data hosted on wasabisys.com.
Wasabi employees soon confirmed that the service had crashed, and also reported that the company had unforeseen DNS resolution issues, including s3.eu-central-1.wasabisys.com, s3.us-west-1. wasabisys.com and s3.wasabisys.com.
As it turned out, the problem was that the domain registrar had been trying to notify Wasabi for a long time about malicious content posted on wasabisys.com. However, when sending notifications of violations, the registrar made a mistake and sent them to an incorrect email address. That is, Wasabi simply did not receive these letters and there was no response from the company. As a result, the domain was blocked by the registrar due to malicious content posted by users (it is not known what exactly it was). The problem is that all Wasabi buckets were used by wasabisys.com and became unavailable due to blocking.
Having figured out the problem, Wasabi experts immediately blocked the client who posted the malicious content and asked the registrar to return the domain to service. As a result, it took more than 13 hours to restore the service.