Wasabi: Reports of DNS resolution issues for some endpoints
Timeline of updates
- resolved
As of 1411 UTC (0911 EST) on 29 Dec 2020, our third-party domain name registrar has removed the wasabisys.com domain from their blacklist. We have seen traffic reach normal levels for most of our customers. Due to the time it takes DNS to refresh, it may take several hours for all affected customers to fully access the Wasabi service. To summarize this incident, our domain name registration was suspended due to concerns over publicly accessible malicious content that was uploaded by one of our newly subscribed customers. Our domain name registrar attempted to notify Wasabi of this problem but the email report of this problem from them went to the incorrect Wasabi email address. After the domain name registrar did not receive a response from Wasabi, they blacklisted the wasabisys.com domain. Upon learning of the malicious content report, Wasabi did immediately suspend the associated customer account for terms of service violations. We also contacted the domain name registrar as soon as we identified the problem. However, despite our escalation attempts, it took over 13 hours for them to reactivate the wasabisys.com domain. We are preparing a more detailed root cause analysis (RCA) to share with affected customers and the following actions are planned for the near future: * Enhancing our existing policies for handling abuse reports from third-party service providers * Replace our current domain name registrar with one more suited for our global cloud service * Reviewing our policies regarding anonymous public access to customer buckets We thank all of our customers and partners for their patience and support through this service event.
From Wasabi’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.wasabi.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Wasabi, started 2020-12-28 19:38 UTC, resolved after 22 h, 1 update(s).
- Title
- Reports of DNS resolution issues for some endpoints
- Vendor
- Wasabi
- Date
- URL
- https://rewindex.com/company/wasabi/incidents/d0cgk227n22x
Wasabi profileRecent Wasabi incidentsAll outages on December 28, 2020Wasabi in December 2020MarkdownJSON