Live data from Hacker News

Fastly Outage

fastly.com

421–430 of 740 posts

Re: Fastly Outage

#421

Shopify's CDN is down. Which is causing $15+ million in lost product sales for every hour of outage. Not to mention the loss of any new customers.

Here is lesson to learn for shopify talented staff. Don't put all your eggs in the same nest. I'm sure they can build something better than that. Hopefully, they will learn from this outage.

Re: Fastly Outage

#422
post #329

Earlier quoted context omitted.

But https://news.ycombinator.com/ is UP! :) Prepare those HN servers for massive influx in 3...2..1..

New error now, hopefully fix in progress. Fastly error: unknown domain: www.fastly.com. Details: cache-syd10161-SYD

>The issue has been identified and a fix is being implemented.

According to the status page.

Re: Fastly Outage

#423
post #329

Earlier quoted context omitted.

But https://news.ycombinator.com/ is UP! :) Prepare those HN servers for massive influx in 3...2..1..

New error now, hopefully fix in progress. Fastly error: unknown domain: www.fastly.com. Details: cache-syd10161-SYD

That doesn't take away their embarrassment. It's mean how many websites rely on fastly. Twitter hasn't been loading emojis in a while, and I believe it's for the same reason.

Re: Fastly Outage

#425
post #357

Earlier quoted context omitted.

While we're here.. I am a bit surprised to see how many sites use Fastly. As a dev I've always been happy with Cloudflare.

Now imagine how many sites would go down if it was CF

Do more rely on Cloudflare? Because this felt like it was more than half the internet, certainly more than half the biggest sites.

Re: Fastly Outage

#428

Yeah so it's been mentioned in the comments already, but to everyone in Fastly right now: I feel for you. Something like this must be insanely stressful, and not just during the outage. There will be (should be) a massive post-mortem. People will be losing sleep over this for days, weeks, months. :( Edit: There seems to be a major empathy outage in this thread. Disgusted but not surprised, unfortunately.

Call me old fashioned but the latest trend of showing "empathy" for a serious incident, then proceeding to dance around the aftermath of it, whilst people give themselves a pat on back in a retro/post-mortem, isn't the way to do it. People need to be blamed, and responsibility for actions taken (without covering asses)

We need to learn from our, and other mistakes, or else we keep repeating them. Nothing "old fashioned" about that.

And we, especially companies, typically only learn if there is something at stake. Stock-price, a job, customers, liability etc.

(Call me old fashioned, but what I learned from it, having no stake in the game, is we are truly demolishing the resilient, decentralised nature of the internet; or already have done so)

Re: Fastly Outage

#429
post #381

Earlier quoted context omitted.

Call me old fashioned but the latest trend of showing "empathy" for a serious incident, then proceeding to dance around the aftermath of it, whilst people give themselves a pat on back in a retro/post-mortem, isn't the way to do it. People need to be blamed, and responsibility for actions taken (without covering asses)

The point isn't to dance around the incident, but to not blame people. You can blame systems, design, engineering culture, processes, but don't blame people. Even if someone accidentally pressed the 'destroy prod' button, that's not the fault of that person, it's the fault of that button existing and being accessible in the first place. I have no empathy for Fastly-the-company. I hate the fact that the Internet is ce…

I disagree. People implemented those systems, so if you are correct that it is the systems fault, then it is also a persons fault.

People must be held accountable to have good incentives to reduce such outtages in the future.

I do agree though that we should always be compassionate and realistic with other humans.

Post reply on HN