Something changed about a week ago on my connection, I believe between 20-23 November 2022.
Before then I’d get around 15ms to 1.1.1.1 or any Cloudflare site, and now I get pings around 160ms.
If I do a tracert to 1.1.1.1, I see it routing normally from my ISP (Vodafone NBN) to the first IP owned by Cloudflare, and then the next hop has the 150ms delay.
Since the packets only get slower after the first CF router, it seems to me this is an issue with CF and not my ISP or something else. No other sites/services as far as I can tell have this delay.
My IP is 101.112.199.XXX
Any help would be appreciated!
C:\Users\Adam>tracert 1.1.1.1
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.1.1
2 17 ms 13 ms 17 ms 101.113.64.1
3 13 ms 14 ms 11 ms 10.246.69.151
4 10 ms 21 ms 14 ms 203-220-16-133.tpgi.com.au [203.220.16.133]
5 17 ms 14 ms * syd-apt-ros-wgw2-be90.tpgi.com.au [202.7.162.53]
6 14 ms 15 ms * 203.29.134-82.tpgi.com.au [203.29.134.82]
7 16 ms 11 ms 12 ms 108.162.247.12
8 158 ms 167 ms 163 ms 172.68.144.5
9 163 ms 163 ms 164 ms one.one.one.one [1.1.1.1]
Trace complete.
Sorry to bump again. Would edit but that doesn’t seem to be a thing here.
Expanding on what I said in the first post:
108.162.247.12 and onwards are the CF IPs, but 108.162.247.12 replies fast, and 172.68.144.5 replies slow. Very wierd.
I’m seeing this as well. I’m in Ohio, US and my connecting Datacenter is IAD. I’m having extremely high pings, use to be ~20ms now seeing 130-160ms.
64 bytes from 1.1.1.1: icmp_seq=107 ttl=53 time=123.014 ms
64 bytes from 1.1.1.1: icmp_seq=108 ttl=53 time=126.660 ms
64 bytes from 1.1.1.1: icmp_seq=109 ttl=53 time=120.054 ms
64 bytes from 1.1.1.1: icmp_seq=110 ttl=53 time=128.499 ms
64 bytes from 1.1.1.1: icmp_seq=111 ttl=53 time=129.608 ms
64 bytes from 1.1.1.1: icmp_seq=112 ttl=53 time=131.167 ms
Request timeout for icmp_seq 113
64 bytes from 1.1.1.1: icmp_seq=114 ttl=53 time=135.005 ms
Request timeout for icmp_seq 115
64 bytes from 1.1.1.1: icmp_seq=116 ttl=53 time=125.737 ms
64 bytes from 1.1.1.1: icmp_seq=117 ttl=53 time=133.876 ms
64 bytes from 1.1.1.1: icmp_seq=118 ttl=53 time=133.734 ms
^C
--- 1.1.1.1 ping statistics ---
120 packets transmitted, 96 packets received, 20.0% packet loss
round-trip min/avg/max/stddev = 120.054/131.860/156.290/5.202 ms
[email protected] ~ %
Also, seems to be worse in the evening. When i go to speed.cloudflare.com to test my tunnel speed i see ~300kbits/s, where i would normally see my ISP rate ~300Mb/s
I’m pretty sure this is a different issue, as you’re a long way from Sydney. Whatever solution works for the original poster most likely won’t apply to your situation.
Not so sure about that. I’m seeing the same thing on my traceroute:
[email protected] ~ % traceroute one.one.one.one
traceroute: Warning: one.one.one.one has multiple addresses; using 1.1.1.1
traceroute to one.one.one.one (1.1.1.1), 64 hops max, 52 byte packets
1 rt3200-router (192.168.1.1) 2.479 ms 1.029 ms 1.580 ms
2 142-254-153-129.inf.spectrum.com (142.254.153.129) 7.611 ms 11.244 ms 10.829 ms
3 lag-62.powloh0202h.netops.charter.com (65.24.193.53) 27.801 ms 20.090 ms 25.305 ms
4 lag-35.clmcohib01r.netops.charter.com (24.33.160.34) 10.442 ms 14.770 ms 16.109 ms
5 lag-27.rcr01clevohek.netops.charter.com (65.29.1.38) 17.884 ms 14.463 ms 22.452 ms
6 lag-415.vinnva0510w-bcr00.netops.charter.com (66.109.6.12) 25.378 ms
lag-416.vinnva0510w-bcr00.netops.charter.com (66.109.6.164) 29.232 ms
lag-415.vinnva0510w-bcr00.netops.charter.com (66.109.6.12) 21.632 ms
7 lag-11.asbnva1611w-bcr00.netops.charter.com (66.109.6.30) 24.744 ms
lag-31.asbnva1611w-bcr00.netops.charter.com (107.14.18.82) 23.945 ms
lag-11.asbnva1611w-bcr00.netops.charter.com (66.109.6.30) 32.524 ms
8 lag-311.pr2.dca10.netops.charter.com (24.27.236.9) 24.709 ms
lag-0.pr2.dca10.netops.charter.com (66.109.5.117) 27.537 ms
lag-310.pr2.dca10.netops.charter.com (209.18.43.59) 25.790 ms
9 173.245.63.56 (173.245.63.56) 22.769 ms 26.934 ms 27.177 ms
10 172.71.192.2 (172.71.192.2) 167.149 ms *
172.71.188.2 (172.71.188.2) 193.851 ms
11 one.one.one.one (1.1.1.1) 150.829 ms * 163.767 ms
Hi all,
Unfortunately, there is no update on the escalation yet.
Could you also provide an MTR which includes more helpful information to our engineering team, to help speed things along?
If you are on Windows, you can use WinMTR download | SourceForge.net for this.
Thanks
Thanks adamb,
I have shared this in our internal escalation, and we seem to be making progress in further identifying and mitigating this. We will provide you an update here once we get more feedback.
)