I also can't find a status page and not so much as a peep from Backblaze anywhere. I pinged them on Twitter [1] to no avail. I like Backblaze but this has been going on for 3 hours now. You can't be down for 3 hours without any communication about it...
From the support page, I get the impression nothing will happen until 9am Pacific. Tickets have a 1d response time, and chat is Pacific working day with a lunch break.
This site can’t be reachedCheck if there is a typo in backblazeb.com.
If spelling is correct, try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
Today's task: starting working on moving back to aws.
Storage savings cant compete with the cost of developer time and downtime even when we store a petabyte.
24 comments
[ 4.4 ms ] story [ 57.9 ms ] threadPacific time is several hours behind me in the UK and it's 11am here.
I don't think it was even Thursday yet Pacific time when this started.
[1] https://twitter.com/JasperSiepkes/status/1329347119774375937
Bottom of https://www.backblaze.com/help.html
I think they're all sound asleep, blissfully unaware of the day they'll wake up to!
Perhaps the first they'll know of the problem is when they read it on HN
This site can’t be reachedCheck if there is a typo in backblazeb.com. If spelling is correct, try running Windows Network Diagnostics. DNS_PROBE_FINISHED_NXDOMAIN
I am now wandering if my data is safe there. I think it will be smart to keep a copy in aws glacier.
https://s3.eu-central-003.backblazeb2.com/
https://f002.backblazeb2.com/file/blah
https://f003.backblazeb2.com/file/blah
*Edit -> we've identified the fix and are rolling it out, you should see S3-Endpoint service resuming shortly!
> Well, hopefully there won't be a next time
Are you seriously saying that not only is there not one, but you're against having one because you hope the status is always green?