Earlier quoted context omitted.
yes, it's planned. I believe the only blocker we saw last time we looked was a 1-hour downtime-window every week (not that always went offline, but that they could use that time for maintenance). Do you know if that's still the case?
If you’re talking about https://www.backblaze.com/scheduled-maintenance.html it’s not intended to affect file usage of B2 (the bucket functions may go offline for up to 15min, but ul, dl, and listing of files are fine. One related thing to be aware of: the official documentation suggests adding retry to every file upload as some uploads naturally fail (usually for load balancing))
one caveat - we are shipping as fast as we can right now so that we can have feature-parity with Firebase. It's a balance of "breadth vs depth" and right now we are going for breadth. We will definitely offer more providers on the platform but the resilience of s3 is beneficial for our engineers right now - it means that they can focus on features rather than devops.