Cloud

484 readers

2 users here now

This community was created to share news, hold discussions, insights, and knowledge sharing about cloud computing and different cloud services like AWS, Google Cloud, Azure, and many others.

Read our rules here

founded 1 year ago

MODERATORS

[email protected]

Cloudflare 1.1.1.1 incident on June 27, 2024 (blog.cloudflare.com)

submitted 1 month ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 1 month ago (2 children)

I gave up their dns quite long ago, I was getting slow internet regularly and some day I discovered accidentally that it was their fault.

[–] [email protected] 6 points 1 month ago (1 children)

It's interesting that the internet is packed with search hits of complains that Cloudflare's DNS is slowing everything but Cloudflare representatives are quick to post followups pointing the finger everywhere else.

[–] [email protected] 5 points 1 month ago

That's like the most trivial of theories one can test for.

Save response time every minute

while true; do /usr/bin/time -f "%e `date`" dig '@1.1.1.1' +noall programming.dev &>>/tmp/dns_clf_perf.txt; sleep 60; done

Then after a while (maybe a couple of days), check the worst numbers:

sort -n /tmp/dns_clf_perf.txt |tail

Run the same script with a different DNS server at the same time, and compare numbers.

Dates included in case there are any patterns regarding the time of day/week.