Hello again, after changing my router three weeks ago and having no problems. it seems to have started rubber banding after the patch. My ping is stable for a good 5 mins before it starts to fluctuate between 67 and 170 ms.
WinMTR Statistics
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
mynetwork | 0 | 604 | 604 | 0 | 1 | 32 | 1 |
10.11.xx.xxx | 0 | 604 | 604 | 16 | 25 | 85 | 26 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
tcore3-_hundredgige2-13-0-0.net.bell.ca | 2 | 572 | 565 | 17 | 25 | 112 | 34 |
dis53-_hundredgige0-2-0-0.net.bell.ca | 1 | 580 | 575 | 16 | 22 | 79 | 22 |
tcore4-_1-14-0-0.net.bell.ca | 1 | 592 | 589 | 26 | 33 | 82 | 31 |
tcore4-newoyrkaa_hundredgige0-8-0-0.net.bell.ca | 1 | 588 | 584 | 29 | 38 | 80 | 40 |
bx10-newyork83_ae1.net.bell.ca | 2 | 580 | 574 | 28 | 34 | 123 | 38 |
blizzard_bx10-newyork83.net.bell.ca | 2 | 580 | 574 | 29 | 38 | 151 | 32 |
ae1-br01-eqny8.as57976.net | 1 | 584 | 579 | 44 | 51 | 148 | 49 |
et-0-0-2-br02-eqch2.as57976.net | 1 | 584 | 579 | 45 | 56 | 157 | 51 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 120 | 0 | 0 | 0 | 0 | 0 |
Bell is losing some of your data before it reaches the routing partners that Blizzard uses. You sent 604 packets, but we don’t see them again in the test, so that’s how we know it’s actual packet loss.
I just spoke top my isp provider and they changed some things on my modem and now thing a worse in terms of stability. Now I am experiencing the same problem I had 3 weeks ago with my latency fluctuating. Now my ping jumps 30 ms every 2-5 seconds and I slightly rubber band.
Note: I can not physically connect my computer to my modem via either net cable.
WinMTR Statistics
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
mynetwork | 0 | 334 | 334 | 0 | 6 | 536 | 1 |
10.xx.xxx.xxx | 1 | 328 | 327 | 21 | 46 | 3936 | 22 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
tcore3-montreal02_hundredgige2-13-0-0.net.bell.ca | 1 | 328 | 327 | 21 | 47 | 3938 | 29 |
dis53-_hundredgige0-2-0-0.net.bell.ca | 1 | 328 | 327 | 20 | 43 | 3935 | 22 |
tcore3-_1-14-0-0.net.bell.ca | 1 | 326 | 324 | 31 | 43 | 1076 | 34 |
tcore4-newyorkaa_hundredgige0-5-0-0.net.bell.ca | 1 | 328 | 327 | 28 | 92 | 4146 | 36 |
bx10-newyork83_ae1.net.bell.ca | 1 | 324 | 322 | 30 | 95 | 4168 | 32 |
blizzard_bx10-newyork83.net.bell.ca | 1 | 326 | 324 | 31 | 46 | 1075 | 32 |
ae1-br01-eqny8.as57976.net | 1 | 322 | 319 | 92 | 103 | 1080 | 95 |
et-0-0-2-br02-eqch2.as57976.net | 1 | 322 | 319 | 92 | 103 | 1079 | 95 |
et-0-0-29-br01-eqch2.as57976.net | 1 | 322 | 319 | 92 | 103 | 1080 | 96 |
137.221.65.132 | 1 | 322 | 319 | 92 | 102 | 1079 | 96 |
et-0-0-2-br01-eqla1.as57976.net | 2 | 314 | 309 | 92 | 139 | 1080 | 96 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 67 | 0 | 0 | 0 | 0 | 0 |
Yeah, this test does look much worse. Your connection to the modem is very unstable, so possible WiFi interference or maybe it’s just a bad modem. The response time is hitting 536ms and 3936ms periodically before you connect to the ISP’s network.
That lag is carrying over onto the hops of Bell’s network.
Here is another test after restart my computer:
WinMTR Statistics
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
mynetwork | 0 | 261 | 261 | 0 | 3 | 98 | 1 |
10.xx.xx.xxx | 1 | 257 | 256 | 21 | 29 | 111 | 32 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
tcore3-_hundredgige1-6-0-3.net.bell.ca | 0 | 261 | 261 | 21 | 55 | 900 | 26 |
dis3-_0-3-0.net.bell.ca | 1 | 257 | 256 | 21 | 26 | 111 | 32 |
tcore4-_1-10-0-1.net.bell.ca | 1 | 257 | 256 | 31 | 38 | 116 | 34 |
64.230.78.138 | 1 | 257 | 256 | 29 | 36 | 109 | 33 |
bx10-newyork83_ae0.net.bell.ca | 1 | 257 | 256 | 28 | 33 | 115 | 33 |
blizzard_bx10-newyork83.net.bell.ca | 1 | 257 | 256 | 31 | 39 | 182 | 37 |
ae1-br01-eqny8.as57976.net | 1 | 257 | 256 | 43 | 50 | 151 | 44 |
et-0-0-2-br02-eqch2.as57976.net | 1 | 253 | 251 | 44 | 54 | 155 | 114 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 53 | 0 | 0 | 0 | 0 | 0 |
These hops should have a response time of less than 10ms at all times, and they’re still hitting 98-111ms periodically. They may need to come and switch it out for you.
Ironically, I just recently changed my modem 3 weeks ago. I had the exact same problem: Can't create a ticket on the techinical support forums + rubber banding in game - #3 by Zenlaka After changing the modem I experienced problems. So I do not know if the patch screwed it up or the modem they gave me was just a lemon.
Regardless, they’re sending a technician to check my out side lines, modem, etc. I do not understand how this problem occurred just randomly. My ping was stable and fine prior to the patch and now it is giving me trouble.
Also, when I spoke to a representative on the phone they told me it was a blizzard issue with the patch. I told him most likely blizzard reponse will be that it is on my end or my isp provider.
Well, the test shows where the problem is. You ran it, you created the data, so it’s not like someone is altering it to make it say something that isn’t actually happening. If anything, the ISP is shucking responsibility off to Blizzard. The servers for Overwatch have no history of being unstable for any length of time (brief blips here and there), despite what countless posts suggest on the forum (it is 99% ISP issues, really). ISPs changing their routing/handling of traffic has been messing with connections since the internet was born.
I hope the tech can help you. Definitely run the WinMTR to the Overwatch server when they are at your home so they can see the response times and packet loss.
P.S. I’m just a player/MVP, not an employee.
Actually, there was an issue with blizzard’s servers about a year ago ( give or take). For some reason all bell users could not access any of blizzard’s severs, i.e. could not log in into any game, could not access the bnet website, etc. Eventually they fixed the issue but I did not have any idea what the problem was. Also, I am fully aware that you are not a blizzard employee.
Edit: I’m stupid, just ignore this post.