Extremely high, frequent ping spikes only on American gateway
|
Lately the game has become nearly unplayable for races on the American gateway. I have been forced to use the European gateway due to high latency spikes.
On the American gateway, my latency is around 60 MS, but spikes to 500+ for an instant every second at an extremely regular interval, causing my client to never be in synch at all. On the european gateway, my latency is constant between 130 and 160 MS. On the Australian, my ping is constant between 240 and 260 ms. I do not experience any spikes on these gateways, it is only present on the American. I am quite certain it is not any issues with my local internet. I have tried nearly every solution I have found, including disabling network throttling that often causes issues on windows 7. The fact that the issue only occurs on the American gateway suggests that it is an issue with either the game server or some internet provider in between. Also, I live in florida. Perhaps this is a regional issue. |
|
" Hey there, Can you please run some trace routes whilst playing the game and experiencing these latency spikes on the US gateway? This way we can track down where the spikes are originating and hopefully help you to resolve the problem. A guide for running a trace route can be found here: https://www.pathofexile.com/forum/view-thread/361292 "Also, I live in florida. Perhaps this is a regional issue." This is always a possibility. It could even resolve itself after a day or two. How long has it been occurring for? |
|
|
This has been occuring very frequently for the last week. The spikes tend to happen for many hours at a time, and disappear for a few hours once in a while. Interestingly, the spikes disappeared the moment the servers reset for the patch today. I will run the traceroute next time they occur, assuming that the restart did not somehow fix the issue.
|
|
|
Trace
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 622 | 622 | 0 | 0 | 1 | 0 | | 10.52.32.1 - 0 | 622 | 622 | 6 | 9 | 22 | 11 | | ten1-0-0.orld59-cts1.bhn.net - 0 | 622 | 622 | 7 | 12 | 29 | 15 | | ten0-0-0-3.orld31-car1.bhn.net - 0 | 622 | 622 | 8 | 13 | 26 | 14 | | ten0-13-0-7.orld71-car1.bhn.net - 0 | 622 | 622 | 11 | 15 | 28 | 18 | | 72-31-188-170.net.bhntampa.com - 0 | 622 | 622 | 13 | 16 | 29 | 20 | | 4.68.70.153 - 32 | 277 | 190 | 0 | 20 | 78 | 16 | | ae-0-11.bar2.Orlando1.Level3.net - 0 | 622 | 622 | 12 | 17 | 76 | 12 | | ae-5-5.ebr2.Miami1.Level3.net - 0 | 622 | 622 | 17 | 19 | 33 | 18 | | ae-2-52.edge1.Miami2.Level3.net - 0 | 622 | 622 | 18 | 24 | 123 | 22 | | te2-5.bbr01.tm01.mia01.networklayer.com - 5 | 535 | 513 | 109 | 123 | 160 | 124 | | ae7.bbr01.tm01.mia01.networklayer.com - 3 | 567 | 553 | 0 | 121 | 145 | 119 | | ae1.bbr01.sr02.hou02.networklayer.com - 2 | 583 | 573 | 0 | 127 | 218 | 128 | | ae3.bbr01.eq01.dal03.networklayer.com - 2 | 587 | 578 | 0 | 128 | 157 | 128 | | ae0.dar01.sr01.dal01.networklayer.com - 4 | 551 | 533 | 0 | 127 | 144 | 124 | | po1.fcr05.sr06.dal01.networklayer.com - 3 | 559 | 543 | 0 | 129 | 193 | 130 | | patch103.pathofexile.com - 2 | 579 | 568 | 0 | 126 | 138 | 129 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider The issue has reappeared. It started shortly before the descent race today. did not have any issues earlier in the day. Ping was stuck around 140 with extremely high spikes (which I am guessing is from packet loss). To my knowledge no programs were running on any computer in the house that would use enough bandwidth to cause this. Edit: My ping normalised shortly after the race ended. I wonder if this is a coincidence. Last edited by mardukthewolf#5333 on Jun 24, 2014, 10:54:07 PM
|
|
|
My guess is that there is a capacity issue between these two nodes (at the peer exchange):
| ae-2-52.edge1.Miami2.Level3.net - 0 | 622 | 622 | 18 | 24 | 123 | 22 | | te2-5.bbr01.tm01.mia01.networklayer.com - 5 | 535 | 513 | 109 | 123 | 160 | 124 | notice that not only is that where the packet loss starts, but it is also where the latency picks up and starts consistently being elevated. So that would be my best guess based on that trace is a peering issue. Should contact your ISP and provide them a copy of the trace so they can escalate to Level3 (since Level3 won't deal with end-users) |
|
|
I've been monitoring speedtest.wdc01.softlayer.com while playing:
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 641 | 641 | 0 | 0 | 4 | 0 | | No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 | | 10.170.183.61 - 0 | 641 | 641 | 7 | 13 | 40 | 11 | | 216.113.126.218 - 0 | 641 | 641 | 12 | 17 | 40 | 16 | |xe.1.0.0.bbr01.cl01.tor02.networklayer.com - 0 | 641 | 641 | 14 | 17 | 80 | 16 | | ae7.bbr02.cl01.tor02.networklayer.com - 0 | 641 | 641 | 14 | 18 | 42 | 25 | | ae0.bbr01.cl01.mon02.networklayer.com - 2 | 609 | 601 | 32 | 36 | 137 | 32 | | ae7.bbr02.cl01.mon02.networklayer.com - 2 | 613 | 606 | 33 | 38 | 138 | 34 | | ae3.bbr01.tl01.nyc01.networklayer.com - 2 | 613 | 606 | 38 | 43 | 242 | 43 | | ae1.bbr01.eq01.wdc02.networklayer.com - 1 | 617 | 611 | 40 | 44 | 104 | 46 | | ae0.dar02.sr01.wdc01.networklayer.com - 2 | 613 | 606 | 38 | 42 | 73 | 43 | | po2.fcr01.sr01.wdc01.networklayer.com - 1 | 617 | 611 | 39 | 43 | 99 | 43 | | speedtest.wdc01.softlayer.com - 1 | 617 | 611 | 41 | 49 | 245 | 45 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Seems pretty fair to me but I still had in game lag spikes (or packet loss?) while playing on Washington's gateway. Fun fact I never really noticed before is, those spikes start at 12am EST (like...exactly). Looks like some cronjob running on the gateway/server/or somewhere along the way. I'll try to monitor this over the next few days. |
|
