Menu
Reply
  • 2
  • 0
  • 0
Takheos
Joining in
244 Views
Message 1 of 3
Flag for a moderator

Rubberbanding with Overwatch

In the last few days, I've experienced extreme lag and rubberbanding whilst trying to play Overwatch. Jolted movement, teleporting, sliding. I haven't had any internet issues reported to me by housemates, nor have I had any problem with VoIP, Teamviewer, Skype or other games.

Spoiler below contains a couple of pings.

Spoiler
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Nick>ping 192.168.0.1 -n 30

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=568ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=16ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=32ms TTL=64
Reply from 192.168.0.1: bytes=32 time=14ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=67ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=924ms TTL=64
Reply from 192.168.0.1: bytes=32 time=399ms TTL=64
Reply from 192.168.0.1: bytes=32 time=19ms TTL=64
Reply from 192.168.0.1: bytes=32 time=59ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1048ms TTL=64
Reply from 192.168.0.1: bytes=32 time=451ms TTL=64
Reply from 192.168.0.1: bytes=32 time=14ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=14ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=15ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 1048ms, Average = 125ms

C:\Users\Nick>ping 192.168.0.1 -n 30
Spoiler

C:\Users\Nick>ping 5.42.173.37

Pinging 5.42.173.37 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 5.42.173.37:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Nick>ping 5.42.173.37:26519
Ping request could not find host 5.42.173.37:26519. Please check the name and try again.

C:\Users\Nick>tracert 5.42.173.37

Tracing route to 5.42.173.37 over a maximum of 30 hops

1 5 ms 10 ms 17 ms 192.168.0.1
2 * * * Request timed out.
3 33 ms 27 ms 21 ms glfd-core-2a-xe-801-0.network.virginmedia.net [80.7.14.1]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 93 ms 73 ms 51 ms ams2-ic-1-ae0-0.network.virginmedia.net [62.253.188.158]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 80.249.208.83 reports: Destination net unreachable.

Trace complete.

C:\Users\Nick>

No faults reported with my area. Please advise, thank you.

0 Kudos
Reply
  • 2
  • 0
  • 0
Takheos
Joining in
227 Views
Message 2 of 3
Flag for a moderator

Re: Rubberbanding with Overwatch

Spoiler

C:\Users\Nick>ping Blizzard.com -n 30

Pinging Blizzard.com [24.105.29.30] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 129.250.199.54: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.105.29.30:
Packets: Sent = 30, Received = 1, Lost = 29 (96% loss),

C:\Users\Nick>tracert blizzard.com

Tracing route to blizzard.com [24.105.29.30]
over a maximum of 30 hops:

1 5 ms 59 ms 16 ms 192.168.0.1
2 * * * Request timed out.
3 28 ms 45 ms 74 ms glfd-core-2a-xe-801-0.network.virginmedia.net [80.7.14.1]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 23 ms 49 ms 34 ms manc-ic-1-ae1-0.network.virginmedia.net [62.254.42.242]
10 36 ms 44 ms 44 ms 86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
11 * * * Request timed out.
12 42 ms 72 ms 46 ms us-was03a-rd1-xe-8-2-3-0.aorta.net [84.116.130.242]
13 54 ms 53 ms 42 ms ae-6.r25.amstnl02.nl.bb.gin.ntt.net [80.249.208.36]
14 137 ms 170 ms 148 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
15 144 ms 147 ms 140 ms ae-2.r05.asbnva02.us.bb.gin.ntt.net [129.250.2.22]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\Nick>

Apologies for double, can't edit again.

0 Kudos
Reply
  • 9.54K
  • 281
  • 607
Forum Team
Forum Team
195 Views
Message 3 of 3
Flag for a moderator

Re: Rubberbanding with Overwatch

Hey Takheos,

 

Thanks for posting and a big welcome to the community Smiley Very Happy

 

Sorry to hear about your connection problems, it sounds frustrating.

 

I've checked your Hub and the power levels could be tweaked a bit, also there are a few time-outs. I think to be on the safe side, we'll arrange for an engineer to call around.

 

I'll send you appointment info via PM (purple envelope, top right).

 

Speak with you soon,

Take care.

Heather_J

Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply