Hacker News Reader

Comment by ukulele | Hacker News Reader

Honestly, "not taking advantage of our DNS management" is a garbage response. We use AWS for our DNS management. If you offer a configuration, you should support it fully.

Our sites have been down for 3 hours now, and you're blaming someone else? We have 5 properties on Netlify now and will have 0 this time next week.

View on HN

> Our sites have been down for 3 hours now, and you're blaming someone else?

Well if the issue is at Google then maybe "blaming" isn't really the right word. No need to be rude.

I might as well make the same argument for your sites.

- Your sites have been down for 3 hours now, and you're blaming someone else?

Yes, it is our fault for believing Netlify had contingency plans as hosting is their core business. We're fixing this mistake now so that our customers don't have the same experience.

By the same line of reasoning, your customers could be faulted for believing you had a contingency plan.

Nobody is telling parent's customers how to feel. But the OP suggests that Netlify customers should be faulted for choosing the the wrong setup. Broken trust goes all the way down the chain, which is why the middle links have every reason to get ticked off.

The difference is that Netlify communicated the risks to its customers, something other parts of the chain apparently did not do, in addition to not evaluating the risks presented to them by Netlify.

Did you read the docs [1] before writing this? Putting a "(recommended)" on one branch of configuration instructions isn't the same as saying that the other option has a single point of failure. Also, people on both sides of a service don't have the same responsibilities - that's the whole point of the service.

Communicating about risks OR outages are both hard, and every company has both. I'm actually a happy (though impacted) Netlify customer. But it's completely bizarre to me to try to invalidate this customer's complaint.

[1] https://web.archive.org/web/20200303050851/https://docs.netl... (search "flattening")

Yes, I’ve visited that page before today. I admit my familiarity with these DNS setups may have made the tradeoff jump out at me. No problem invalidating the complaint.

Point your apex domain to 75.2.60.5, Netlify recommends it here [0] and in their documentation now [1].

I just did for a site that's hosted by Netlify and it solved the issue. Thankfully I had a short TTL, I hope you do too.

[0] https://www.netlifystatus.com/

[1] https://docs.netlify.com/domains-https/custom-domains/config...

I'm not sure your organization's setup with Netlify but isn't the whole point of Serverless to be... "serverless"? I could migrate twice the amount of properties you have to another provider in less than 3 hours...

I get your frustration but maybe cut some slack. If anything is mission critical, you should have had a backup plan if Netlify, Vercel, Cloudflare, or something else.

We use(d) Netlify for the frontend. I agree, our mistake was believing Netlify could be used for more than toy websites and took care of backup plans for us. Clearly they do not.

I do believe you to be trolling now by saying that. If not, congrats on the valuable lesson!

Not trolling, just very frustrated. But yes a valuable lesson.

What's keeping you from migrating your frontends? Shouldn't that take a couple of hours at worst?

It's not just migrating the front-end if they're also using other functionalities like Netlify functions, forms, authentications etc. Netlify is not just static file hosting.

Reply on news.ycombinator.com