What worries me more than the outage is that they didn't introduce any emergency measures like creating a new domain that apps could use to interact with their service.
Wasabi just proved completely unreliable as a storage provider for apps, not because the outage happened but because how it's handled.
I help run a service that relies on Wasabi. This outage is rough. It’d be nice to have a workaround while their domain is resolving. As artwis mentioned, an alternative domain would suffice.
As it is, we’re scrambling to come up with a workaround.
Handy if you know the IP addresses, can you share please? I think after the service being unusable for so long Wasabi should be publishing this as a workaround.
;; ANSWER SECTION:
s3.wasabisys.com. 18 IN A 38.27.106.22
s3.wasabisys.com. 18 IN A 38.27.106.23
s3.wasabisys.com. 18 IN A 38.27.106.25
s3.wasabisys.com. 18 IN A 38.27.106.26
s3.wasabisys.com. 18 IN A 38.27.106.27
s3.wasabisys.com. 18 IN A 38.27.106.12
s3.wasabisys.com. 18 IN A 38.27.106.13
s3.wasabisys.com. 18 IN A 38.27.106.14
s3.wasabisys.com. 18 IN A 38.27.106.15
s3.wasabisys.com. 18 IN A 38.27.106.16
s3.wasabisys.com. 18 IN A 38.27.106.19
s3.wasabisys.com. 18 IN A 38.27.106.21
Wouldn’t have worked simply in our case. We put together a proxy server and were going to run it on a box with the /etc/hosts hack, then point our CDN at that. Got it all written up in Go, and then Wasabi came back online.
8 comments
[ 3.0 ms ] story [ 26.6 ms ] threadWasabi just proved completely unreliable as a storage provider for apps, not because the outage happened but because how it's handled.
As it is, we’re scrambling to come up with a workaround.