Hi everyone, we’ve been big fans of the cloudflare DNS resolvers and use it for all of our I.T. customers, but while diagnosing several internet issues the past few days we noticed that across the board every single one of our customers using Comcast as their ISP (Home & Business) are getting 25% to 40% packet loss to IP 22.214.171.124 and 126.96.36.199. As far as we know, it does appear isolated to Cloudflares dns resolver IPs and I’m unaware if this is affecting Comcast users outside metro Detroit. Traceroute shows the possible problem child being 188.8.131.52 .
I’ve tried reporting this to Comcast technical support and escalating it but I’m sure anyone that has dealt with that knows I’m spinning my wheels. Does anyone have any suggestions?
Yea figured it was a Comcast IP and confirmed with a quick arin search. Was just hoping someone here would have a possible different angle to get Comcast to fix this.
That link is super cool. I’ll run it on a few locations and post results. Thanks!
As this appears to be outside of CF and our control, i’ll be moving our clients over to Level3 and Google until there’s some progress made. If a ticket or tech needs additional information for progress, I’ll be glad to assist.
To contact Cloudflare Customer Support, login & go to https://dash.cloudflare.com/?account=support and select get more help. If you receive an automatic response that does not help you, please reply and indicate you need more help.
Can we just set it as sticky one day, give it to one of interim to blog.
ICMP traceroutes, and observed packet loss (or timeouts), are not indicative of a problem, routers will drop/block/depriotize ICMP traffic. Do you really believe that CF would not be aware of 25%+ packet loss to their edge servers from perhaps the biggest eyeball network outside of China?
You obviously didn’t read the post in its entirety, or you’re insinuating that CF is dropping ICMP traffic on purpose. Also I don’t believe that Michigan Comcast customers are the biggest eyeball network outside of China, but you apparently know more than I do plus it does sound pretty cool. Thank you for your contribution to this post! It’s helped a great deal!
I’ve contacted comcast regarding this issue because I am also experiencing it from the Chicago area. This was tier 2 enterprise support and they recognized the issue and identified an existing ticket regarding a link that is over saturated. The resolution involves very expensive upgrades to the equipment on that link, but they are actively working on it. Apparently this requires executive approval due to the costs involved. I’m guessing it will be a few weeks before it is resolved. Very frustrating, with only a few million people affected apparently it’s not a huge priority.