High(er) ping times

Is there any works going on at the minute? My ping has gone from 6ms to any from 10ms to 22ms. I know it’s not stupidly high and still 100% useable but just curious that’s all. I thought after migration the pings were going to reduce.

Cheers.

Also noticed slightly higher pings
1.1.11 is usually <10ms.

Can you do a traceroute to 1.1.1.1?

1.1.1.1 should be sorted now :slightly_smiling_face:

Direct from Router :
root@AltaRoute10:~#

traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 46 byte packets
 1  213.18.200.1 (213.18.200.1)  4.635 ms  3.944 ms  4.244 ms
 2  yayzi-broadband.pe0.lhr0.uk.as61049.net (185.20.53.17)  4.614 ms  3.983 ms  4.219 ms
 3  speed-ix.cloudflare.com (185.1.222.191)  12.786 ms  28.194 ms  14.342 ms
 4  141.101.65.14 (141.101.65.14)  12.946 ms  141.101.65.109 (141.101.65.109)  12.848 ms  141.101.65.105 (141.101.65.105)  13.434 ms
 5  one.one.one.one (1.1.1.1)  12.277 ms  12.304 ms  12.366 ms

@Yayzi_Team

Are there issues with routing?


traceroute to ui.com (18.239.36.19), 64 hops max, 40 byte packets
 1  10.10.15.1 (10.10.15.1)  6.906 ms  3.814 ms  3.524 ms (0% loss)
 2  213.18.200.1 (213.18.200.1)  9.586 ms  9.762 ms  8.807 ms (0% loss)
 3  yayzi-broadband.pe0.lhr0.uk.as61049.net (185.20.53.17)  10.139 ms  8.769 ms  8.046 ms (0% loss)
 4  xe-1-5-2-3.a02.londen12.uk.bb.gin.ntt.net (83.231.146.238)  11.019 ms  10.121 ms  8.536 ms (0% loss)
 5  ae-10.r22.londen12.uk.bb.gin.ntt.net (129.250.5.156)  9.567 ms  9.109 ms  8.515 ms (0% loss)
 6  ae-3.r22.amstnl07.nl.bb.gin.ntt.net (129.250.5.2)  14.253 ms  13.561 ms  13.525 ms (0% loss)
 7  ae-15.a00.amstnl07.nl.bb.gin.ntt.net (129.250.2.75)  15.619 ms
    ae-2.a01.amstnl07.nl.bb.gin.ntt.net (129.250.2.93)  14.488 ms  14.174 ms (0% loss)
 8  ae-0.amazon.amstnl07.nl.bb.gin.ntt.net (129.250.207.114)  33.320 ms  14.751 ms * (33% loss)
 9  * 52.93.112.155 (52.93.112.155)  17.587 ms
    52.93.112.159 (52.93.112.159)  16.304 ms (33% loss)
10  54.239.114.45 (54.239.114.45)  15.943 ms *
    54.239.114.69 (54.239.114.69)  29.199 ms (33% loss)
11  * * * (100% loss)
12  * * * (100% loss)
13  * * * (100% loss)
^C

1 Like

Mine is diffrent, so probably NTT have messed up by the looks of it.

later edit, actually i get 143.204.68.90 when resolving ui.com

My pings increased past few hours, plus packet loss

Pings have calmed down but packet loss is a thing now