Live data from Hacker News

Cloudflare's new DNS attracting 'gigabits per second' of rubbish

zdnet.com

201–206 of 206 posts

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#201

Earlier quoted context omitted.

A smarter, and perhaps even more profitable way to approach this problem is "OK, we want almost everything that happens to customers to be a self-serve situation" and then make your (fewer) call centre employees highly trained troubleshooters who can figure out why _this_ customer wasn't able to self-serve and get that sorted for them. The result is a better customer experience (usually everything just works, when yo…

Often I prefer "self-serve," but sometimes I like to talk to a human who knows about the system that has created my problem, and can quickly fix it. That's why there are websites dedicated to showing people how to skip through phone menus and reach actual humans, even if those humans are soundboard operators paid almost nothing to make you go away.

link? I refuse to talk to computers.

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#202

Earlier quoted context omitted.

> I am not off by an order of magnitude, I know exactly how big they are. Your post implied a total of 200-400gb, the real number is 10x that (otherwise known as “order of magnitude”). I’m not disputing your knowledge or experience, but the post as written has issues.

no, my post was quite specifically about a single IX point in one geographical location, and was accurate. You confused me talking about interface sizes and counts at one IX point with cloudflare as a whole.

What difference does it how much they have as peering in one specific geo? Are you going to posit then that that is their capacity in that geo? I hope not, as Cloudflare has their own backbone and could easily and efficiently exchange traffic outside the geo depending on peering agreements.

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#203
post #193

Earlier quoted context omitted.

> no development on the LAN Does this just mean staging/shared servers are not deployed on machines inside the corporate network, or that developers can't have their dev environment locally and instead remote in to some other machine to do their work? I've heard of the latter in a few companies and it's always the kind of thing that makes me nope out of every applying to them.

Devs do most of their work on localhost. Changes are pushed to an independent server on an independent network in another city. Once those changes are vetted, then the work is mirrored to production. Each dev has his own cellular connection for internet on his development box. Again, no LAN access. Corporate e-mail and cross-department file servers are on another box on each dev's desk. The downside is massive over-u…

Oh wow - I would not want to work there ever. I understand the need for some security but this seems just over the top.

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#204

Earlier quoted context omitted.

Often I prefer "self-serve," but sometimes I like to talk to a human who knows about the system that has created my problem, and can quickly fix it. That's why there are websites dedicated to showing people how to skip through phone menus and reach actual humans, even if those humans are soundboard operators paid almost nothing to make you go away.

link? I refuse to talk to computers.

The fact that these pages exist tells you all you need to know about the fundamental user-hostility of modern tech companies:

https://gethuman.com

https://www.wikihow.com/Talk-to-a-Human-when-Calling-a-Busin...

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#205
post #178

Earlier quoted context omitted.

Who scolded you for it? Wouldn't that just mis-route legitimate traffic to 1.1.1.0/24 locally instead of to the internet?... but you probably had no legitimate traffic there anyway, right?

Who? I don't remember. Someone on HN/reddit. It was a mild scolding in the same vein as in the article. And yes, that's what it would do. And no, I didn't. Made it easier to type in IPS, that's for sure.

Oh, okay... I thought it was your ISP or something. That is why I was wondering how anyone would even notice.

Re: Cloudflare's new DNS attracting 'gigabits per second' of rubbish

#206

Earlier quoted context omitted.

Very true that it is a typo, which I had noticed, and thanks for calling out. Still doesn’t invalidate my point though. My theory is that a lot of that traffic is likely coming from spoofed IPs as I doubt there would be substantial sustained legitimate, but improperly directed, traffic. My guess is a lot of it is shoddily written malicious traffic.

Google for “BCP 38”. This pain has been known for many, many years.

I don’t need to Google it, I’m well aware. Part of why I said what I did.
Post reply on HN