Details of yesterday's Bunny CDN outage
1–10 of 87 posts
Re: Details of yesterday's Bunny CDN outage
#2> On June 22nd at 8:25 AM UTC, we released a new update designed to reduce the download size of the optimization database.
That's around 4:25 a.m EST. Are updates usually done around this time at other companies? Seems like that's cutting pretty close to the around 8am where a lot of employees start working.
The details of the whole incident sounds pretty terrifying and I am inspired to hear how much pressure their admins were under and got it working again. Good work.
Re: Details of yesterday's Bunny CDN outage
#3> On June 22nd at 8:25 AM UTC, we released a new update designed to reduce the download size of the optimization database. That's around 4:25 a.m EST. Are updates usually done around this time at other companies? Seems like that's cutting pretty close to the around 8am where a lot of employees start working. The details of the whole incident sounds pretty terrifying and I am inspired to hear how much pressure their a…
They're based in Slovenia, so that was 10:25 AM local time for them.
Re: Details of yesterday's Bunny CDN outage
#4> On June 22nd at 8:25 AM UTC, we released a new update designed to reduce the download size of the optimization database. That's around 4:25 a.m EST. Are updates usually done around this time at other companies? Seems like that's cutting pretty close to the around 8am where a lot of employees start working. The details of the whole incident sounds pretty terrifying and I am inspired to hear how much pressure their a…
Is there a reason to assume EST?
Re: Details of yesterday's Bunny CDN outage
#5> On June 22nd at 8:25 AM UTC, we released a new update designed to reduce the download size of the optimization database. That's around 4:25 a.m EST. Are updates usually done around this time at other companies? Seems like that's cutting pretty close to the around 8am where a lot of employees start working. The details of the whole incident sounds pretty terrifying and I am inspired to hear how much pressure their a…
They're based in Slovenia, so that was 10:25 AM local time for them.
I am going based off of the map here, Europe and then North America is their biggest market:
Seems like they were updating production during work hours for most people which is pretty odd imo. Usually I would expect them to get this done between midnight and 2-3am.
Re: Details of yesterday's Bunny CDN outage
#6> On June 22nd at 8:25 AM UTC, we released a new update designed to reduce the download size of the optimization database. That's around 4:25 a.m EST. Are updates usually done around this time at other companies? Seems like that's cutting pretty close to the around 8am where a lot of employees start working. The details of the whole incident sounds pretty terrifying and I am inspired to hear how much pressure their a…
Is there a reason to assume EST?
I was mostly going based off of their majority market being Europe and North America.
Re: Details of yesterday's Bunny CDN outage
#7> On June 22nd at 8:25 AM UTC, we released a new update designed to reduce the download size of the optimization database. That's around 4:25 a.m EST. Are updates usually done around this time at other companies? Seems like that's cutting pretty close to the around 8am where a lot of employees start working. The details of the whole incident sounds pretty terrifying and I am inspired to hear how much pressure their a…
A cdn has a global target, there will be someone starting to work all the time around the world.
Re: Details of yesterday's Bunny CDN outage
#8Good and clear explanation. This is a risk you take when you use a CDN, I still think the benefits outweigh the occasional downtime. I'm a big fan of BunnyCDN, they've saved me a lot of money over the past few years.
I'm sure I'd be fuming if I worked at some multi-million dollar company but as someone that mainly works for smaller businesses it's not the end of the world, I suspect most of my clients haven't even noticed yet.
Re: Details of yesterday's Bunny CDN outage
#9on a different note, this outage news will give them more publicity than the product itself, I believe...
Re: Details of yesterday's Bunny CDN outage
#10One of the comments on the post is:
> One thing you could do in future is to url redirect any BunnyCDN url back to the clients original url, in essence disabling the CDN and getting your clients own hosts do what they were doing before they connected to BunnyCDN, yes it means our sites won't be as fast but its better than not loading up the files at all. I wonder if that is possible in technical terms?
Isn't this a horrible idea? If you use bunny, this would cause a major spike in the traffic and thus costs from your origin server.