New Contributor
•
10 Messages
I'm having issues playing a game of mine
I've been playing Overwatch on PC since its release, May 24, and up until this past Saturday I have been getting very bad lag/rubberbanding in the game, its really frustrating just stuttering and not getting your inputs when you press keys.
A traceroute to 37.244.0.3, which is what Blizzard says to ping/tr specifically for Overwatch, shows that 68.1.1.13 might be the problem because it'll either give a perfectly fine response, give a high latency response, or timeout.
What's going on there Cox?
Related Content
Closed
2
0
Closed
1
0
Closed
1
0
Closed
10
0
Closed
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
Can you post the tracert?
0
0
sldfghtrike89
New Contributor
•
10 Messages
Tracing route to 37.244.0.3 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 *****ms 043 ms 042 ms 10.145.224.1
3 179 ms 176 ms 155 ms 100.127.68.82
4 131 ms 144 ms 141 ms 70.169.74.148
5 228 ms 138 ms 133 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 146 ms 107 ms 200 ms 70.191.61.10
7 *****ms 025 ms 033 ms 37.244.0.3
Trace complete.
0
0
sldfghtrike89
New Contributor
•
10 Messages
Tracing route to 37.244.0.3 over a maximum of 30 hops
0 SldFghtrIke [192.168.0.16]
1 192.168.0.1
2 10.145.224.1
3 100.127.68.82
4 70.169.74.148
5 langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 70.191.61.10
7 37.244.0.3
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 SldFghtrIke [192.168.0.16]
1/ 100 = 1% |
1 69ms 1/ 100 = 1% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 72ms 1/ 100 = 1% 0/ 100 = 0% 10.145.224.1
0/ 100 = 0% |
3 64ms 2/ 100 = 2% 1/ 100 = 1% 100.127.68.82
0/ 100 = 0% |
4 45ms 1/ 100 = 1% 0/ 100 = 0% 70.169.74.148
0/ 100 = 0% |
5 --- 100/ 100 =100% 99/ 100 = 99% langbprj01-ae1.rd.la.cox.net [68.1.1.13]
0/ 100 = 0% |
6 --- 100/ 100 =100% 99/ 100 = 99% 70.191.61.10
0/ 100 = 0% |
7 91ms 1/ 100 = 1% 0/ 100 = 0% 37.244.0.3
Trace complete.
0
0
ChrisL
Former Moderator
•
7.1K Messages
Looking at your posted results I think the problem actually lies between the computer and the router. Your 2nd result in particular shows packet loss to 192.168.0.1 which is probably where the problem is originating. I'd try these tests on other devices in your home and see if you get loss to the same hop.
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
Blizzard "Blues" are idiots IMO. My Ex used to be one. And if you have a link to your thread I will go there and tell them. They always see ICMP depriorization as packet loss. Either they are REALLY dump, or they are doing it on purpose to pass the buck.
+1 bypass router and tracert again. Also, what is your average ms if you ping 10.145.224.1?
0
0
Norman
New Contributor III
•
37 Messages
Blizzard was getting ddos'd the another night by some random angry guy who probably ran into bastion too many times. It knocked the servers + log in servers down for a few hours. The guy promised it was only the start so expect more of it to come.
I'm not saying that's your issue just throwing that out there.
0
0