cancel
Showing results for 
Search instead for 
Did you mean: 
freshest
Aspiring Contributor
323 Views
Message 1 of 12

Latency Between Hops

Go to solution
Hey, I have quite a big problem going on with my hub 5 box where when im gaming I get extreme latency hops it might be a DLM issue or wiring, I have no idea what has caused it. I have some of the hops here Reply from 185.198.188.100: bytes=32 time=1029ms TTL=54 Reply from 216.58.204.14: bytes=32 time=181ms TTL=54 9 206 ms 45 ms 39 ms 185.198.188.1  9 901 ms 47 ms 30 ms 185.198.188.1  13 870 ms 18 ms 17 ms 108.170.246.193  As you can ee the start goes up to 9206, 9901 and then 13870 If i can get some assistance that would be great.
0 Ratings
11 REPLIES 11
Distinguished Guru
Distinguished Guru
298 Views
Message 2 of 12

Re: Latency Between Hops

Go to solution
Can you post a complete tracert?
0 Ratings
freshest
Aspiring Contributor
290 Views
Message 3 of 12

Re: Latency Between Hops

Go to solution

How do I get a complete tracert?

0 Ratings
Distinguished Guru
Distinguished Guru
278 Views
Message 4 of 12

Re: Latency Between Hops

Go to solution
Can you open a command prompt window? If so then just enter tracert followed by the destintion.
0 Ratings
freshest
Aspiring Contributor
268 Views
Message 5 of 12

Re: Latency Between Hops

Go to solution

Alrighty, I think this is it.          

Spoiler
Running RC-RP Diagnostics test...
Retrieving system date and time.
16/12/2017
15:30

------- Ping/Traceroute to EU.FROSTGAMING.COM -------:

Pinging eu.frostgaming.com [185.198.188.98] with 32 bytes of data:
Reply from 185.198.188.98: bytes=32 time=16ms TTL=54
Reply from 185.198.188.98: bytes=32 time=17ms TTL=54
Reply from 185.198.188.98: bytes=32 time=16ms TTL=54
Reply from 185.198.188.98: bytes=32 time=16ms TTL=54
Reply from 185.198.188.98: bytes=32 time=16ms TTL=54
Reply from 185.198.188.98: bytes=32 time=17ms TTL=54
Reply from 185.198.188.98: bytes=32 time=16ms TTL=54
Reply from 185.198.188.98: bytes=32 time=17ms TTL=54

Ping statistics for 185.198.188.98:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 17ms, Average = 16ms

Tracing route to eu.frostgaming.com [185.198.188.98]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms BThomehub.home [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 15 ms 15 ms 15 ms 31.55.185.188
5 19 ms 17 ms 17 ms core2-hu0-6-0-6.colindale.ukcore.bt.net [213.121.192.24]
6 17 ms 17 ms 16 ms 109.159.252.138
7 15 ms 15 ms 16 ms peer2-et-10-3-0.faraday.ukcore.bt.net [62.6.201.199]
8 16 ms 16 ms 16 ms linx-lon1.thn2.peering.clouvider.net [195.66.227.14]
9 206 ms 45 ms 39 ms 185.198.188.1
10 18 ms 18 ms 17 ms 185.198.188.3
11 16 ms 16 ms 16 ms rev.srv3.eu.frostgaming.com [185.198.188.98]

Trace complete.

------- Ping/Traceroute to SERVER.REDCOUNTYRP.COM -------:

Pinging server.redcountyrp.com [185.198.188.100] with 32 bytes of data:
Reply from 185.198.188.100: bytes=32 time=18ms TTL=54
Reply from 185.198.188.100: bytes=32 time=17ms TTL=54
Reply from 185.198.188.100: bytes=32 time=47ms TTL=54
Reply from 185.198.188.100: bytes=32 time=17ms TTL=54
Reply from 185.198.188.100: bytes=32 time=17ms TTL=54
Reply from 185.198.188.100: bytes=32 time=17ms TTL=54
Reply from 185.198.188.100: bytes=32 time=1029ms TTL=54
Reply from 185.198.188.100: bytes=32 time=17ms TTL=54

Ping statistics for 185.198.188.100:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 1029ms, Average = 147ms

Tracing route to server.redcountyrp.com [185.198.188.100]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 18 ms 32 ms 37 ms 31.55.185.180
5 17 ms 17 ms 17 ms host213-121-192-8.ukcore.bt.net [213.121.192.8]
6 104 ms 17 ms 18 ms core3-hu0-8-0-0.faraday.ukcore.bt.net [195.99.127.36]
7 16 ms 17 ms 17 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.195]
8 17 ms 16 ms 17 ms linx-lon1.thn2.peering.clouvider.net [195.66.227.14]
9 901 ms 47 ms 30 ms 185.198.188.1
10 18 ms 18 ms 22 ms 185.198.188.3
11 17 ms 17 ms 16 ms rev.srv5.eu.frostgaming.com [185.198.188.100]

Trace complete.

------- Ping/Traceroute to GOOGLE.COM -------:

Pinging google.com [216.58.204.14] with 32 bytes of data:
Reply from 216.58.204.14: bytes=32 time=17ms TTL=54
Reply from 216.58.204.14: bytes=32 time=17ms TTL=54
Reply from 216.58.204.14: bytes=32 time=17ms TTL=54
Reply from 216.58.204.14: bytes=32 time=181ms TTL=54

Ping statistics for 216.58.204.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 181ms, Average = 58ms

Tracing route to google.com [216.58.204.14]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms BThomehub.home [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 16 ms 15 ms 15 ms 31.55.185.188
5 17 ms 16 ms 16 ms core2-hu0-0-0-1.colindale.ukcore.bt.net [195.99.127.136]
6 16 ms 16 ms 16 ms peer2-et3-1-4.slough.ukcore.bt.net [62.172.103.220]
7 334 ms 17 ms 16 ms 109.159.253.195
8 * * * Request timed out.
9 17 ms 17 ms 17 ms 64.233.175.154
10 319 ms 19 ms 19 ms 108.170.246.143
11 18 ms 18 ms 18 ms 216.239.57.227
12 19 ms 18 ms 18 ms 216.239.59.4
13 870 ms 18 ms 17 ms 108.170.246.193
14 18 ms 17 ms 18 ms 108.170.238.145
15 17 ms 17 ms 17 ms lhr35s07-in-f14.1e100.net [216.58.204.14]

Trace complete.

IPconfig information:

Windows IP Configuration

Host Name . . . . . . . . . . . . : computer11-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Wireless LAN adapter Wireless Network Connection 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #7
Physical Address. . . . . . . . . : 24-77-03-55-1E-59
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #6
Physical Address. . . . . . . . . : 24-77-03-55-1E-59
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection 4:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) #4
Physical Address. . . . . . . . . : 7C-E9-D3-C0-69-BE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 9:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Intel(R) Centrino(R) Ultimate-N 6300 AGN
Physical Address. . . . . . . . . : 24-77-03-55-1E-58
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6de2:da91:de52:156b%29(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.77(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 16 December 2017 15:23:14
Lease Expires . . . . . . . . . . : 17 December 2017 15:23:14
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 572815107
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-F7-28-05-08-11-96-24-07-8C
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 4:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection #4
Physical Address. . . . . . . . . : D4-BE-D9-20-EC-53
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.home:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #6
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

*****Test Complete*****!
15:33
16/12/2017
0 Ratings
freshest
Aspiring Contributor
226 Views
Message 6 of 12

Re: Latency Between Hops

Go to solution

Bump

0 Ratings
Distinguished Guru
Distinguished Guru
219 Views
Message 7 of 12

Re: Latency Between Hops

Go to solution

Your tracerts show no problems.

 

BTW it's pointless bumping a thread, it won't get you an answer any quicker.

0 Ratings
Liam_
Expert
215 Views
Message 8 of 12

Re: Latency Between Hops

Go to solution

The timed out request is just a server configured not to respond to ping.
Tracing route to eu.frostgaming.com seems fine.
The increased latency on No. 9 206 ms 45 ms 39 ms 185.198.188.1 is outside the BT network and nothing you can do about that.
On the whole the timing to the game server looks normal.
Repeated pings to 108.170.246.143 returned 20ms from here so the longer time in your trace on the first ping is likely just a temporary glitch.
For information the 185.198.188.1 is in Holland, so again not a lot you can do.

0 Ratings
freshest
Aspiring Contributor
205 Views
Message 9 of 12

Re: Latency Between Hops

Go to solution

So is there a fix to this? Should I reset my box? What should I do.

0 Ratings
Distinguished Sage
203 Views
Message 10 of 12

Re: Latency Between Hops

Go to solution
There is nothing you can do or that BT can do your connection is ok as you have already been told
0 Ratings