5 ms·
I have ATT and seeing the same issues, but my tracert is different. tracert 1.1.1.1 Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1] over a
by pgrote 9y ago
I have ATT and seeing the same issues, but my tracert is different.
tracert 1.1.1.1
Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
tracert 1.0.0.1
Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]
over a maximum of 30 hops:
1 3 ms <1 ms <1 ms 192.168.1.254
2 48 ms 18 ms 34 ms 99-153-196-1.lightspeed.stlsmo.sbcglobal.net [99.153.196.1]
3 19 ms 17 ms 17 ms 64.148.120.125
4 29 ms 24 ms 18 ms 71.144.225.112
5 19 ms 18 ms 18 ms 71.144.224.85
6 19 ms 18 ms 19 ms 12.83.40.161
7 26 ms 27 ms 26 ms cgcil403igs.ip.att.net
[12.122.132.121]
8 27 ms 24 ms 28 ms ae16.cr7-chi1.ip4.gtt.net [173.241.128.29]
9 32 ms 31 ms 31 ms xe-0-0-0.cr1-det1.ip4.gtt.net [89.149.128.74]
10 31 ms 31 ms 31 ms cloudflare-gw.cr0-det1.ip4.gtt.net [69.174.23.26]
11 31 ms 31 ms 35 ms 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]
In a browser, 1.1.1.1 comes back as connection refused. 1.0.0.1 loads.
- jlgaddis 9y ago> In a browser, 1.1.1.1 comes back as connection refused. 1.0.0.1 loads. Yep, exactly. Using 1.0.0.1, everything works. Using 1.1.1.1, nothing (ping, DNS, HTTPS) does. EDIT: See earlier comment; looks like an issue w/ the AT&T-provided CPE (5268AC).