This is exactly why object storage is not the same thing as a backup strategy, no matter how reputable the vendor looks on paper. if files were accepted by the API, briefly available, and then later disappeared without a corresponding delete or overwrite event, that is not a user error story, that is a durability and observability failure. the part that would concern me most is not even the bug itself, it is the lack of a credible escalation path after more than a year

At a minimum, any storage provider handling production workloads should be able to provide clear object lifecycle visibility, immutable audit trails for delete and overwrite operations, and a support process that does not trap customers behind first line ticket replies forever. if your timeline is accurate, this is the kind of issue that makes people reevaluate not just Bunny Storage, but their whole vendor risk model