A steady 58 with minor variance would not be a problem. The problem is that my ingame netgraph shows my ping avg 58, the min is 47, but i get spikes to 70 every intermittently. The gameplay is floaty. I have been getting placed on the West Coast server in LA occasionally. My ping avgs 88 with very minor variance and although the latency is higher, the gameplay is smoother due to a more stable latency. The Overwatch support has also said the reason for being placed on a different server means that the connection had less latency to that server at the time. The problem is not latency its the variance of it and how often.
... View more
I get what your saying. The one 50.208 node spikes every few seconds which is what I think is causing jitter.
I don't understand then, how I was sent this route the other day ,all day. I had lower ping 42 average instead of 58 ingame.
Next day back to the old route. So does that mean everyone in my area had a reroute to the Overwatch US central server?
I think I'm just giving up on the issue altogether and will probably try to downgrade or cancel service since its just to expensive and a hassle to mess with any further.
... View more
No, I do not understand what it takes to get a custom route. I do know if you look at the winMTR I posted about the route that felt perfect, you will see my connection did take a different route that day for whatever reason. Also, if you look at the official xfinity subreddit you can find other people having a similar issue and being rerouted. I doubt its a "custom route" but possibly a different one.
WinMTR is one of the primary tools used by Blizzard Officials. It gives more accurate results to a given ip address over time.
If you look at the most recent WinMTR
| 22.214.171.124 - 0 | 1029 | 1029 | 15 | 20 | 59 | 19 |
|be-22909-cr02.56marietta.ga.ibone.comcast.net - 0 | 1029 | 1029 | 23 | 27 | 44 | 27 |
|be-1102-cs01.56marietta.ga.ibone.comcast.net - 1 | 1025 | 1024 | 22 | 26 | 973 | 25 |
|be-2101-pe01.56marietta.ga.ibone.comcast.net - 0 | 1029 | 1029 | 22 | 25 | 50 | 23 |
| 126.96.36.199 - 0 | 1029 | 1029 | 21 | 29 | 121 | 24 |
There is packet loss and large spikes in latency. This is consistent after 10 minutes.
And here. The 112? That spikes from 20-30 to 80-120 consistently. BTW this WinMTR was only to show the route taken. It was under 10 minutes of gameplay.
| 188.8.131.52 - 0 | 642 | 642 | 23 | 29 | 112 | 24 |
| ae1-br01-eqat2.as57976.net - 0 | 642 | 642 | 41 | 46 | 97 | 42 |
The ae1-br01.... is " designed to ignore some ping traffic as a defense mechanism against DDoS attacks. You will often see their response times as over 1k-2k because of this."
That is a qoute from Nicole, Blizzard Tech Support.
Considering Xfinity sponsors/ has sponsored OWL (Overwatch League) and I'm paying $73
a month for internet only. Then I absolutely will be hoping for a fix. :-)
... View more