Earlier quoted context omitted.
Well, hopefully there won't be a next time - but also, bothering me doesn't help debug or resolve the problem, our Ops/Tech team do that :D
I was baffled that I couldn't find a status page at all, but I assumed I was just failing to find it. > 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?
Backblaze S3 API is having some downtime
21–25 of 25 posts
Re: Backblaze S3 API is having some downtime
#22Earlier quoted context omitted.
I was baffled that I couldn't find a status page at all, but I assumed I was just failing to find it. > 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?
No, that comment was edited after I had responded - we're not against status pages - they are on the roadmap, but unfortunately not implemented yet.
Re: Backblaze S3 API is having some downtime
#23Yev here - we're investing the S3-endpoint issue - apologies for delay in response here, it took them a bit of time to wake me up. *Edit -> we've identified the fix and are rolling it out, you should see S3-Endpoint service resuming shortly!
Re: Backblaze S3 API is having some downtime
#24Re: Backblaze S3 API is having some downtime
#25Earlier quoted context omitted.
I was baffled that I couldn't find a status page at all, but I assumed I was just failing to find it. > 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?
No, that comment was edited after I had responded - we're not against status pages - they are on the roadmap, but unfortunately not implemented yet.