search

tagpro-game / tagpro-issues

Public repository to report and review TagPro bugs, enhancements and suggestions.
15 stars 4 forks source link

ping to radius explodes only during league play #293

Open fragrantfowl opened 7 years ago

fragrantfowl commented 7 years ago

I'm an origin player that was drafted to a radius team. I get good ping to radius, 45, steady. Not perfect but definitely playable. Last night during league play it was 200+. It did the same last week during league play, and I thought it was a fluke. Today, i get ready to troubleshoot my connection, but it's back to 45 ping.

I only notice the increased ping during league play. Is it possible that I am being routed differently when the server is overloaded?

fragrantfowl commented 7 years ago

MTR from today:

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.2.1 0 4894 4894 1 4 270 5
172.30.232.1 1 4854 4844 8 12 383 12
216.80.78.87 1 4866 4859 8 13 826 12
bdle2.border1.eqnx.il.rcn.net 1 4870 4864 8 13 482 15
mpr1.ord7.us 1 4861 4853 8 15 555 14
64.125.31.84 1 4865 4858 9 21 841 14
ae27.cs1.ord2.us.eth.zayo.com 1 4873 4868 9 20 812 36
ae3.cs1.lga5.us.eth.zayo.com 1 4884 4882 33 46 662 39
ae0.cs2.lga5.us.eth.zayo.com 1 4876 4872 36 46 772 45
ae27.cr2.lga5.us.zip.zayo.com 1 4868 4862 33 41 357 40
ae6.mpr2.ewr1.us.zip.zayo.com 1 4878 4874 37 45 683 44
128.177.26.242 1 4871 4865 38 46 496 46
173.255.239.3 1 4862 4854 37 46 842 44
li1075-106.members.linode.com 1 4869 4863 34 43 544 42

Last night this node was the problem. I don't have an image of it now, but that's where the jump was.

| mpr1.ord7.us - 1 | 4861 | 4853 | 8 | 15 | 555 | 14 |

fragrantfowl commented 7 years ago

It happened again tonight. My ping was 45 during the day. As league play commenced it climbed and climbed and climbed until it was over 160. It has now declined to 126.

It has calmed down a little, but you can see the sticking point is that same node.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.2.1 0 13 13 1 7 27 5
172.30.232.1 0 12 12 10 14 20 17
216.80.78.87 0 12 12 10 12 18 11
bdle2.border1.eqnx.il.rcn.net 0 12 12 10 14 22 22
mpr1.ord7.us 0 12 12 46 66 89 65
ae11.er2.ord7.us.zip.zayo.com 0 12 12 47 66 87 71
64.125.31.82 0 12 12 46 65 90 72
ae27.cs2.ord2.us.eth.zayo.com 0 12 12 75 98 128 104
ae3.cs2.lga5.us.eth.zayo.com 0 12 12 75 96 145 96
ae27.cr2.lga5.us.zip.zayo.com 0 13 13 71 91 113 102
ae6.mpr2.ewr1.us.zip.zayo.com 0 13 13 78 99 118 107
128.177.26.242 0 12 12 81 99 121 104
173.255.239.3 0 12 12 81 100 120 102
li1075-106.members.linode.com 0 12 12 71 92 114 98
ylambda commented 7 years ago

There's nothing we can do about this.

If there's something on our end, we may be able to do something. If there's something on your end you may be able to do something to fix it. If there's something in the middle there's nothing either of us can do about this.

fragrantfowl commented 7 years ago

That's about what I thought. And if I change providers, that might work unless it routes through the same node, correct?

iTunes https://itunes.apple.com/us/podcast/readingoutloud/id795209826?mt=2 Twitter https://twitter.com/TeamROL Facebook https://www.facebook.com/ROLpodcast http://www.readingoutloud.org

On Wed, Dec 14, 2016 at 10:23 PM, ylambda notifications@github.com wrote:

There's nothing we can do about this.

If there's something on our end, we may be able to do something. If there's something on your end you may be able to do something to fix it. If there's something in the middle there's nothing either of us can do about this.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagpro-game/tagpro-issues/issues/293#issuecomment-267235545, or mute the thread https://github.com/notifications/unsubscribe-auth/AXbsUYPVxfXddN7cycrgSt2F9aWyK3h8ks5rIMDbgaJpZM4LNG_x .

wilcooo commented 6 years ago

@fragrantfowl correct