cancel
Showing results for 
Search instead for 
Did you mean: 

Trace Route I Did Today Had "19ms 57ms 7ms" Pings To peer7-et-0-1-2.telehouse.ukcore.bt.net

FIXED
Joe24
Newbie
Posts: 2
Registered: ‎02-11-2022

Trace Route I Did Today Had "19ms 57ms 7ms" Pings To peer7-et-0-1-2.telehouse.ukcore.bt.net

Hi,

When I repeated this trace route several times the pings for this server were "6ms 6ms 6ms" except for one occasion when the middle ping was 14ms.

Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.???.??? [As our home routers LAN IP shouldn't be required I won't reveal it here]
2 4 ms 4 ms 5 ms 172.16.11.144
3 * * * Request timed out.
4 6 ms 6 ms 6 ms 136.hiper04.sheff.dial.plus.net.uk [195.166.143.136]
5 19 ms 57 ms 7 ms peer7-et-0-1-2.telehouse.ukcore.bt.net [109.159.252.176]
6 6 ms 6 ms 6 ms linx-gw1.thn.ncuk.net [195.66.224.240]
7 6 ms 6 ms 6 ms ae11-11.edge-rt5.thdo.ncuk.net [80.249.97.21]
8 6 ms 6 ms 6 ms te1-51-36.core-rs3.thdo.ncuk.net [80.249.97.72]
9 6 ms 6 ms 6 ms po5-32.core-rs4.thdo.ncuk.net [80.249.97.90]
10 6 ms 6 ms 6 ms pingbox1.thinkbroadband.com [80.249.99.164]

Trace complete.

I ran this Trace Route on my Windows 11 PC connected via ethernet to my parents DrayTek router. They have PlusNet Fibre Unlimited Extra broadband.

4 REPLIES 4
jab1
Legend
Posts: 19,119
Thanks: 6,272
Fixes: 288
Registered: ‎24-02-2012

Re: Trace Route I Did Today Had "19ms 57ms 7ms" Pings To peer7-et-0-1-2.telehouse.ukcore.b

Can I ask why you did the traceroute? Are you having a specific problem?

John
RealAleMadrid
Aspiring Hero
Posts: 2,851
Thanks: 1,498
Fixes: 61
Registered: ‎07-07-2009

Re: Trace Route I Did Today Had "19ms 57ms 7ms" Pings To peer7-et-0-1-2.telehouse.ukcore.b

Fix

@Joe24  What are you worried about?  There's nothing wrong. The destination pings are all 6mS. That's what matters. Various hops along the way, some may not respond to pings at all such as number 3 and others as is the case for the BT one at Telehouse is probably rather busy with real data transfers so unimportant stuff like trace routes can be delayed but it doesn't affect the end result in any way.

jab1
Legend
Posts: 19,119
Thanks: 6,272
Fixes: 288
Registered: ‎24-02-2012

Re: Trace Route I Did Today Had "19ms 57ms 7ms" Pings To peer7-et-0-1-2.telehouse.ukcore.b

Totally agree, @RealAleMadrid . Still curious why the OP did the check, though.

John
Joe24
Newbie
Posts: 2
Registered: ‎02-11-2022

Re: Trace Route I Did Today Had "19ms 57ms 7ms" Pings To peer7-et-0-1-2.telehouse.ukcore.b

I made the original post in case I had noticed an intermittent slow response problem with this server. In hindsight I should not have reported this as if it had actually been a problem someone else with more networking knowledge than me would have noticed and reported it.

As for why I was running a trace route for the first time I was testing our internet connection to see if there were local internet backbone routers with latency issues which could explain the high network latency in this Steam Remote Play Together streaming log message:

Slow framerate: game 21.73, capture 0.31, convert 0.01, encode 5.06, network 52.02, decode 1.58, display 4.54 (network)

I was streaming a local multiplayer game to two friends who didn't own it sending 4mbps 720p video streams to each and receiving their inputs in return. We all have cable connections to our routers though one of my friends has a power socket adapter connection to his router. This friend lives 10 miles away and the other 11 miles.

Given that you've told me its normal for internet backbone routers to some times take 57ms to respond to trace route ping requests they can normally respond to in 6ms, I suppose they may sometimes have to significantly delay passing on game stream video frame packets resulting in the 52ms network latency I saw mentioned in that slow frame rate log message.