20+ ms pings to 1.1.1.1 from Seattle


#1

I’m getting over 20ms pings from my clink fiber to 1.1.1.1 … for some reason I’m being routed down to San Jose

traceroute:

 1  tukw-dsl-gw70.tukw.qwest.net (63.231.10.70)  1.694 ms  2.060 ms  1.983 ms
 2  63-226-198-41.tukw.qwest.net (63.226.198.41)  1.988 ms  2.002 ms  1.843 ms
 3  sea-brdr-02.inet.qwest.net (67.14.41.190)  2.511 ms  2.541 ms  2.352 ms
 4  63.146.26.54 (63.146.26.54)  13.749 ms  15.127 ms  14.732 ms
 5  if-ae-20-2.tcore1.sv1-santa-clara.as6453.net (64.86.123.95)  20.982 ms  20.623 ms  20.586 ms
 6  if-ae-0-2.tcore2.sv1-santa-clara.as6453.net (63.243.251.2)  20.853 ms  20.611 ms  21.122 ms
 7  if-ae-38-2.tcore1.sqn-san-jose.as6453.net (63.243.205.74)  21.460 ms
    if-ae-18-2.tcore1.sqn-san-jose.as6453.net (63.243.205.12)  20.879 ms
    if-ae-38-2.tcore1.sqn-san-jose.as6453.net (63.243.205.74)  20.896 ms
 8  if-ae-1-2.tcore2.sqn-san-jose.as6453.net (63.243.205.2)  21.173 ms  22.373 ms  20.874 ms
 9  64.86.21.181 (64.86.21.181)  21.460 ms  21.508 ms  38.716 ms
10  one.one.one.one (1.1.1.1)  20.606 ms  20.380 ms  20.603 ms

Is this a cloudflare problem or a clink problem? Conversely, I’m getting sub-3ms pings to 8.8.8.8


#2

Hi @caleb.reft! can you please visit the help page https://1.1.1.1/help/ and share the link with us? The information we gather on that page helps us debug these sort of problems.

Apologies for your inconvenience :frowning:


#3

Sure, here ya go:

https://1.1.1.1/help/#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJObyIsImlzRG9oIjoiTm8iLCJyZXNvbHZlcklwLTEuMS4xLjEiOiJZZXMiLCJyZXNvbHZlcklwLTEuMC4wLjEiOiJZZXMiLCJyZXNvbHZlcklwLTI2MDY6NDcwMDo0NzAwOjoxMTExIjoiWWVzIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTAwMSI6IlllcyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IlNKQyIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==


#4

Looks like it is a peering issue for Centurylink: https://www.peeringdb.com/net/3035