I tried using their Magic Containers product and there were issues that showed a lack of attention to detail as well.
It's supposed to scale globally (magically!) but I found multiple cases where particular nodes were problematic and the health checks didn't detect them (in fact to start with the health checks didn't even work properly if you had multiple containers, they did fix that). The support was quite slow too, after finding multiple product issues they'd escalate to developers and then come back a month later and ask to retest, but some of this took multiple round trips. I was only using this on a side project, but definitely wouldn't consider them for anything critical, even if they are quite cheap.
The OP replies to it in such a way that discredits them, ending with "Very professional of you guys." They could have replied with an equal or more negative sentiment in such a way that wasn't counter-productive, and not have lost much credibility with me.
"does not matter if this is an isolated edge case. Data loss for 15 months with poor support isn't something that can be waved off as 'edge case'. The fact I had to go to Reddit to get someone's attention for this is insane. By the way, I tried reaching out to various 'senior management' personnel via LinkedIn last year and no-one replied. Escalation requests via the Support thread ignored and declined. Very professional of you guys."
and that seems pretty damn reasonable of a reply. the fact they had to go to reddit is insane. a sarcastic "very professional of you guys" is pretty tame, given the situation, and not discrediting at all.
Pretty mild when getting a reply that puts more energy into downplaying the problem than acknowledging that they've had an ongoing data loss issue for over a year and their support has been useless.
You did a commendable job of ignoring all the op's (from Reddit) explanations and context to come to this weird output.
OP even actually responded to a similar comment in this reddit thread - look it up and tell me he wasn't reasonable. 15 months of fobbing him off, and once the case has been raised publicly the very senior guy _suddenly_ sees it as a priority despite it being just an edge case.
It's a perfectly understandable response to what is essentially just corporate damage control. I'd be pissed too if I was in their position.
They've been ignoring the issue for over a year, yet it somehow took them only 4 hours after the reddit post was made to determine that it's "an isolated edge case", even though there's at least one other user reporting the same problem. The comment was clearly written with a focus on saving face rather than properly apologizing for the terrible support.
Also a user of their CDN, storage and container service for about 4 years.
My experience was more positive. One time I had a minor issue with their storage where I couldn't replace a file or something. This was fairly early after the product launched. They fixed it and gave me free credit for reporting it.
I’ve used bunny for a few years … happily. I wonder if this is a bug due to some meta data of the files like the names or something. Very weird. Good thing you had metrics to catch it.
I upload all object storage stuff to bunny for live but also to backblace for backup.
I’ve always wanted to implement fail over client side for any asset over to bacblaze but seems like a lot of overhead
That's scary. I'm in the process of moving all of my services to Europe, and I had considered BunnyCDN, but after this I'm not so sure anymore.
I also tried Hetzner Object Storage. I love Hetzner, they're great, except for their Object Storage service, which is completely unreliable (errors, slowness, etc.). I'm surprised that Hetzner still hasn't retired that product until it's properly fixed.
My last chance is with Scaleway. Xavier Niel's products are always good, so fingers crossed...
There is also OVH (not affiliated, just happily using their VPS), but I would consider switching to 2 providers, as any provider can have data loss or just lock your account at anytime for any reasons. 2 providers with free egress so you can easily replicate data between them.
I guess you may have alot of files, but to me object storage is so cheap I keep copies on Aws S3, wasabi, r2 and a 16 TB HDD on my hetzner server.
Admittedly 4 might be too many. But at some point I switched to r2 for the free public egress and deleting one of Aws or wasabi has never been a priority and I don't want to do it without putting in the time to quadruple check I'm not deleting anything important.
But at the very least id have 3. I'd hate to discover that my S3 was blown up in a war and then copying everything my HDD was the last straw that pushed an aging drive over the edge.
Wait...this has been going on for 15 months without resolution or recompense and you haven't pulled up stakes and moved to almost anyone else? I get "it's a lot of work to move" and maybe "we hope they'll figure this out so we don't have to move", but in my world that excuse runs out waaaaaay before 15 months. The people I'm accountable to would have hauled me out back and put me out of their misery after, maybe, 6 months on the outside.
> ...but in my world that excuse runs out waaaaaay before 15 months.
I expect the combination of
Yes, we should've migrated away sooner, we never had the capacity to do so and hoped Bunny would just get their shit together.
and
The loss rate isn't enormous in percentage terms, but it's consistent and ongoing.
means that detecting and dealing with the loss is substantially less work than moving away. [0] I expect that Management is fully aware of what's up and is making the call here.
[0] "Just" add a retry if the post-upload verification step fails! Sure, it's slower, but it works, right??? mournful sob
I'm a very grateful bunnycdn customer. they are great, lovely UX and great performance and price. we use them to store our image files and other documents.
It's supposed to scale globally (magically!) but I found multiple cases where particular nodes were problematic and the health checks didn't detect them (in fact to start with the health checks didn't even work properly if you had multiple containers, they did fix that). The support was quite slow too, after finding multiple product issues they'd escalate to developers and then come back a month later and ask to retest, but some of this took multiple round trips. I was only using this on a side project, but definitely wouldn't consider them for anything critical, even if they are quite cheap.
"does not matter if this is an isolated edge case. Data loss for 15 months with poor support isn't something that can be waved off as 'edge case'. The fact I had to go to Reddit to get someone's attention for this is insane. By the way, I tried reaching out to various 'senior management' personnel via LinkedIn last year and no-one replied. Escalation requests via the Support thread ignored and declined. Very professional of you guys."
and that seems pretty damn reasonable of a reply. the fact they had to go to reddit is insane. a sarcastic "very professional of you guys" is pretty tame, given the situation, and not discrediting at all.
OP even actually responded to a similar comment in this reddit thread - look it up and tell me he wasn't reasonable. 15 months of fobbing him off, and once the case has been raised publicly the very senior guy _suddenly_ sees it as a priority despite it being just an edge case.
Really? Do you work for their PR or what?
They've been ignoring the issue for over a year, yet it somehow took them only 4 hours after the reddit post was made to determine that it's "an isolated edge case", even though there's at least one other user reporting the same problem. The comment was clearly written with a focus on saving face rather than properly apologizing for the terrible support.
My experience was more positive. One time I had a minor issue with their storage where I couldn't replace a file or something. This was fairly early after the product launched. They fixed it and gave me free credit for reporting it.
I upload all object storage stuff to bunny for live but also to backblace for backup.
I’ve always wanted to implement fail over client side for any asset over to bacblaze but seems like a lot of overhead
I also tried Hetzner Object Storage. I love Hetzner, they're great, except for their Object Storage service, which is completely unreliable (errors, slowness, etc.). I'm surprised that Hetzner still hasn't retired that product until it's properly fixed.
My last chance is with Scaleway. Xavier Niel's products are always good, so fingers crossed...
Admittedly 4 might be too many. But at some point I switched to r2 for the free public egress and deleting one of Aws or wasabi has never been a priority and I don't want to do it without putting in the time to quadruple check I'm not deleting anything important.
But at the very least id have 3. I'd hate to discover that my S3 was blown up in a war and then copying everything my HDD was the last straw that pushed an aging drive over the edge.
For my storage needs in the EU I'm using Upcloud's object storage. Very happy with them. Then a Bunny cdn zone if I need to share the files publicly.
I expect the combination of
and means that detecting and dealing with the loss is substantially less work than moving away. [0] I expect that Management is fully aware of what's up and is making the call here.[0] "Just" add a retry if the post-upload verification step fails! Sure, it's slower, but it works, right??? mournful sob