Here’s my WinMRT. Just found this thread and have been having the same issue for the last week.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| mynetwork - 0 | 476 | 476 | 0 | 0 | 30 | 0 |
| 10.11.0.225 - 0 | 476 | 476 | 14 | 18 | 72 | 15 |
| 10.178.206.74 - 0 | 476 | 476 | 14 | 16 | 70 | 15 |
| 10.178.206.75 - 0 | 476 | 476 | 16 | 17 | 71 | 17 |
| tcore4-toronto47_2-4-0-0.net.bell.ca - 0 | 476 | 476 | 16 | 22 | 65 | 19 |
|tcore4-toronto01_100gige0-14-0-0.net.bell.ca - 0 | 476 | 476 | 16 | 19 | 62 | 19 |
| bx2-toronto01_et7-1-0.net.bell.ca - 1 | 472 | 471 | 16 | 18 | 71 | 19 |
| ae55.bar2.Toronto1.Level3.net - 0 | 476 | 476 | 28 | 30 | 70 | 29 |
| 4.69.216.226 - 17 | 289 | 242 | 0 | 54 | 81 | 54 |
| BLIZZARD-EN.ear1.NewYork5.Level3.net - 1 | 472 | 471 | 43 | 56 | 88 | 57 |
| ae1-br01-eqny8.as57976.net - 1 | 468 | 466 | 63 | 77 | 134 | 77 |
| et-0-0-2-br02-eqch2.as57976.net - 1 | 469 | 468 | 236 | 326 | 1547 | 304 |
| be2-pe01-eqch2.as57976.net - 1 | 472 | 471 | 66 | 75 | 111 | 77 |
| chi-eqch2-ia-bons-02.as57976.net - 1 | 472 | 471 | 63 | 74 | 112 | 71 |
| 24.105.62.129 - 1 | 461 | 457 | 63 | 74 | 103 | 77 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I’m on Videotron and I have no network problems while playing Overwatch. I didn’t even know of this issue until someone point it out on reddit. Seems to be only Bell having this problem or any providers that use their network.
1 Like
Not sure if it’s related, but tonight I was playing with friends. I got a “Failed to connect to server” notice three times. Once when loading a map in QP, once when loading a map in custom game, and once mid-match in a custom game. I was able to play a match or two between these occurrences, until it would happen again out of nowhere. Rebooting my modem fixes it temporarily, but then inevitably it would happen again 20-60 minutes later. Third one that happened mid-match acted very much like a latency spike, except that I literally couldn’t play anymore. Couldn’t even load back into the game - would just get stuck on the intro screen and fail to connect again. I could still browse the internet/type messages on Discord when failing to connect, although both seemed laggy until I rebooted my modem. Bell ISP in Canada.
Sorry for the previous message. these things always happen one game from promo you know…
I can see they transferred us to LAX1 server instead of ORD1. The ms is around 90 but at least its playable.
Thanks for your efforts, I hope to see a solution soon.
This is really frustrating, after 1 game I always have 400ms. And I am FORCED to play because of rank decay this is really annoying, the gameplay is sabotaged for me and the others in my games. I am basically forced to lose games.
Any updates on this issue blizz? Still working on it?
You’re the real MVP here. Hoping that this stuff gets cleared out soon because this is just ridiculous on Bell’s end.
OH, I’m having this issue too. Sometimes it get as high as +3000ms.
It generally varies at 60-90 ms range (my normal ping is around 60). And out of nowhere it goes up and then down.
Brazil.
Here is mine again. with rogers. been having multiple instances of rubberbanding and basically unplayable games due to latency.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| CODA4582 - 81 | 83 | 16 | 0 | 1 | 12 | 1 |
|CPE68b6fc3c6573-CM68b6fc3c6570.cpe.net.cable.rogers.com - 0 | 348 | 348 | 3 | 20 | 165 | 23 |
| 69.63.254.145 - 0 | 348 | 348 | 4 | 14 | 52 | 17 |
| 209.148.232.70 - 0 | 348 | 348 | 4 | 15 | 164 | 19 |
| 9906-cgw01.wlfdle.rmgt.net.rogers.com - 0 | 348 | 348 | 5 | 16 | 171 | 18 |
| 209.148.233.102 - 0 | 348 | 348 | 20 | 32 | 181 | 35 |
| eqix-dc2.blizzard.com - 0 | 348 | 348 | 19 | 32 | 171 | 35 |
| ae1-br01-eqdc2.as57976.net - 0 | 348 | 348 | 22 | 34 | 181 | 42 |
| et-0-0-2-br01-eqch2.as57976.net - 1 | 337 | 336 | 30 | 79 | 4396 | 40 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 70 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Already contacted Rogers. they say the problem isn’t on their end
here have another. longer this time
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| CODA4582 - 93 | 153 | 12 | 1 | 2 | 14 | 1 |
|CPE68b6fc3c6573-CM68b6fc3c6570.cpe.net.cable.rogers.com - 0 | 715 | 715 | 3 | 16 | 275 | 15 |
| 69.63.254.145 - 0 | 715 | 715 | 5 | 13 | 62 | 15 |
| 209.148.232.70 - 0 | 715 | 715 | 3 | 13 | 274 | 11 |
| 3006-cgw01.wlfdle.rmgt.net.rogers.com - 0 | 715 | 715 | 5 | 14 | 273 | 13 |
| 69.63.249.26 - 0 | 715 | 715 | 20 | 29 | 286 | 32 |
| eqix-dc2.blizzard.com - 0 | 715 | 715 | 20 | 29 | 76 | 26 |
| ae1-br01-eqdc2.as57976.net - 0 | 715 | 715 | 19 | 31 | 285 | 31 |
| et-0-0-2-br01-eqch2.as57976.net - 0 | 715 | 715 | 26 | 41 | 176 | 53 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
UrsaMajor Your Issue may be an QoS or unstable connection to the router:
| CODA4582 - 93 | 153 | 12 | 1 | 2 | 14 | 1 |
|CPE68b6fc3c6573-CM68b6fc3c6570.cpe.net.cable.rogers.com - 0 | 715 | 715 | 3 | 16 | 275 | 15 |
First ISP hop also has 275 latency spike. We would want this to be checked out by your ISP, as the route itself seems fine during these tests.
Thanks everyone for the latest examples, keep them coming if you continue to notice major issues. Remember to run the WinMTR for 10 minutes.
Thank you.
Please fix this blizz. I haven’t been able to play for 10 days ![:frowning:](https://d74zh8edaijub.cloudfront.net/en/overwatch/images/emoji/twitter/frowning.png?v=6" ":frowning:")
I’m hard wired into my router and I have already contacted rogers and they told me the problem isnt on their end. i was on th ephone with them for over two hours yesterday and jumped through numerous hoops and the game is still unplayable and its ONLY overwatch
Literally all of the same people are experiencing major issues, so saying “if you continue to notice”. Yes. We are continuing to notice. It’s been every day since Nov. 11 that we’ve continued to notice.
Telling us to keep on reporting the same issue is pointless. It’s also asking us to sit through games with 300+ latency, being an anchor for our teams because its impossible to play, and after all that it’s just going to say the same thing. Ya, no thanks.
I’ve uninstalled until this gets resolved.
I really want to love this game like I used to but now it’s just impossible. I don’t want to give up but that’s what’s gonna happen if this continues much longer. really sad.
ping shot up from ~50 to 700-800 during the endgame, team basically has the license to blame me. this is so bad. what the hell is taking so long?
And I’m pretty sure any disconnects from the game due to this will just hand me a penalty… last time it kicked me out of comp gave me a 30 min wait time.
Blizzard, why should I suffer from the punishment when I’m already losing the match and the opportunity to play the game that I purchased? at least don’t give the players affected by this a Penalty, please? That’s the least you can do while we have no choice but to wait for this to be solved.
i have uninstalled until this is fixed.
Hey everybody,
We made another modification today and it seems to have mixed success - some people reporting it’s better and others not so much. Please keep posting if you’re affected so we can send information to our network team. Please ensure you post WinMTRs so we can look for other issues just in case it’s something else.
Does this last post imply that you’ll only help with people who continue to post problems, or are you still looking into the issue as a whole?
Fair question - we still need help diagnosing where there still need to be tweaks and if there still need to be tweaks. The winMTRs let us see the route and make sure it’s the same thing. There have been no posted winMTRs since we made some more modifications to the routing we have control over. Just posting gives us some information on where you are and where the routing may need to be improved, but the winMTRs give us increased insight on exactly what path you’re taking into our servers.