1.1.1.1 not reachable, 1.0.0.1 working fine [Comcast, Nashville TN]

I have lost ability to reach 1.1.1.1. I can traceroute to 1.1.1.1 from my router and from my iPhone, but Windows tracert dies at the last hop. I cannot ping the server from none of the devices. Traceroute and ping from my router:

~$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 38 byte packets
 1  96.120.52.165 (96.120.52.165)  9.685 ms  11.777 ms  10.869 ms
 2  68.86.194.89 (68.86.194.89)  9.850 ms  9.780 ms  13.892 ms
 3  162.151.41.245 (162.151.41.245)  15.906 ms  8.770 ms  9.874 ms
 4  96.108.81.26 (96.108.81.26)  10.898 ms  8.780 ms  11.851 ms
 5  one.one.one.one (1.1.1.1)  9.856 ms  9.681 ms  13.936 ms
~$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
^C
--- 1.1.1.1 ping statistics ---
205 packets transmitted, 0 received, 100% packet loss, time 212177ms

~$ traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 38 byte packets
 1  96.120.52.165 (96.120.52.165)  9.021 ms  9.764 ms  8.873 ms
 2  68.86.194.89 (68.86.194.89)  13.871 ms  9.779 ms  9.919 ms
 3  162.151.41.245 (162.151.41.245)  9.898 ms  10.787 ms  11.930 ms
 4  96.114.68.78 (96.114.68.78)  9.864 ms  9.710 ms  9.881 ms
 5  one.one.one.one (1.0.0.1)  11.920 ms  9.726 ms  9.908 ms

~$ ping 1.0.0.1
PING 1.0.0.1 (1.0.0.1) 56(84) bytes of data.
64 bytes from 1.0.0.1: icmp_seq=1 ttl=60 time=9.34 ms
64 bytes from 1.0.0.1: icmp_seq=2 ttl=60 time=9.69 ms
64 bytes from 1.0.0.1: icmp_seq=3 ttl=60 time=9.96 ms
64 bytes from 1.0.0.1: icmp_seq=4 ttl=60 time=9.99 ms
64 bytes from 1.0.0.1: icmp_seq=5 ttl=60 time=23.0 ms
^C
--- 1.0.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 9.340/12.405/23.034/5.321 ms

Tracert and ping from Windows:

tracert -d -w 300 1.1.1.1

Tracing route to 1.1.1.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2     8 ms    12 ms     9 ms  96.120.52.165
  3    12 ms    10 ms     8 ms  68.86.194.89
  4     8 ms    10 ms    10 ms  162.151.41.245
  5     9 ms     9 ms     9 ms  96.108.81.26
  6     *        *        *     Request timed out.
  7     *     ^C
ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

1.0.0.1 is working fine. I am in Nashville TN using Comcast internet connection.

Same here on Comcast in Nashville as well. Switched to quad9 for now.

I’m in East TN but I’ve been having the same issue as well.

I’ve switched over to the secondary and things are working fine. I hope the primary starts working soon.

For the past two weeks I have been unable to reach any of the CloudFlare primary name-server IPs. This includes 1.1.1.1, 1.1.1.2 and 1.1.1.3. I can reach the secondaries fine…

If I traceroute to any of these addresses, the exchange path appears to be going through Comcast in Mr Laurel NJ:

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.18.1
2 <1 ms <1 ms <1 ms 192.168.31.254
3 8 ms 7 ms 8 ms 96.120.110.25
4 7 ms 9 ms 8 ms 69.139.213.125
5 14 ms 20 ms 16 ms 68.85.171.105
6 19 ms 19 ms 19 ms 162.151.95.117
7 18 ms 19 ms 19 ms 96.108.81.26 (Comcast Mt Laurel NJ IP)
8 * *

Tracing route to 1.1.1.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.18.1
2 <1 ms <1 ms <1 ms 192.168.31.254
3 10 ms 7 ms 7 ms 96.120.110.25
4 8 ms 11 ms 7 ms 69.139.213.173
5 9 ms 8 ms 10 ms 68.85.171.101
6 18 ms 19 ms 18 ms 162.151.94.93
7 18 ms 17 ms 23 ms 96.108.81.30 (Comcast Mt Laurel NJ IP)
8 18 ms 22 ms 17 ms 10.138.241.38
9 * * * Request timed out.

Tracing route to 1.1.1.3 over a maximum of 30 hops

1 28 ms <1 ms <1 ms 192.168.18.1
2 14 ms <1 ms <1 ms 192.168.31.254
3 7 ms 8 ms 11 ms 96.120.110.25
4 15 ms 18 ms 40 ms 69.139.213.125
5 13 ms 14 ms 11 ms 68.85.171.105
6 18 ms 27 ms 18 ms 162.151.95.117
7 18 ms 19 ms 17 ms 96.108.81.26 (Comcast Mt Laurel NJ IP)
8 * * * Request timed out.

I can traceroute to a secondary name-server address fine…

Tracing route to 1.0.0.3 over a maximum of 30 hops

1 <1 ms <1 ms 192.168.18.1
2 8 ms <1 ms 192.168.31.254
3 7 ms 7 ms 7 ms 96.120.110.25
4 7 ms 7 ms 7 ms 69.139.213.125
5 13 ms 18 ms 12 ms 68.85.171.105
6 19 ms 19 ms 22 ms 162.151.95.117
7 19 ms 18 ms 19 ms 96.114.68.78
8 22 ms 19 ms 18 ms 1.0.0.3

Trace complete.

Any ideas? Could this be congestion in the exchange or something else?

Seems like a Comcast/Cloudflare exclusive issue. Been happening to me as well.

Must be a routing issue as the secondaries are reachable. Ironically Comcast has locked all the CloudFlare related topics on their community site which doesn’t surprise me. Was hoping someone from the CloudFlare team could dig into this as it appears to be a common problem effecting Comcast customers in the southeast.

Its helpful to have a community thread but could you also make a ticket regarding this? Community isn’t official support

1 Like

I have just opened a ticket with Cloudflare Support.

I’m in East TN as well :slight_smile: Based on my Cape sensor, it broke on Thursday at ~5:00PM EST. I changed the DHCP scope on Friday morning.

My ticket got closed by the bot. Any joy?

The email you received from the bot will give instructions on how to reopen the ticket.

Back up for me here in Nashville on Comcast.

Yes, all primary DNS servers are now reachable from Comcast connection in Nashville.

Ideally yes - but clicking on the links resulted in a 404 not found.

Same for me! Thank goodness.