Network Latency Issue
|
Is there something wrong with the game servers atm? Been noticing today that my ping has gone from 40ish to 160ish. It's not just me either, few guildies from the same area as me (socal) are all seeing the same ping spike throughout the day.
| |
|
Yeah fucking it's doing it right now while I'm doing fucking uber aztiri the fuck GGG -.-
- In the US Can't fucking do this place =/ while having a fucking 180- spikes to 800 ping. Dys an sohm Rohs an kyn Sahl djahs afah Mah morn narr Last edited by Coconutdoggy on Oct 16, 2014, 8:09:38 PM
|
|
|
Yea it's pretty bad atm. Beyond league + laggy servers= bad news.
| |
|
I'm not aware of any problems with the servers but we'll let you know if this is confirmed. If the latency issue is restricted to users in California this could indicate a problem at the ISP level or other third party infrastructure. A WinMTR report might shed some light on where the disruption is occurring.
|
|
" Not sure what issue they are having but for Arizona cox cable internet, it is fine (except for main site failure, which may be normal).
Spoiler
Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\tim>ping google.com Pinging google.com [208.117.233.59] with 32 bytes of data: Reply from 208.117.233.59: bytes=32 time=9ms TTL=56 Reply from 208.117.233.59: bytes=32 time=8ms TTL=56 Reply from 208.117.233.59: bytes=32 time=9ms TTL=56 Reply from 208.117.233.59: bytes=32 time=10ms TTL=56 Ping statistics for 208.117.233.59: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 10ms, Average = 9ms C:\Users\tim>ping pathofexile.com Pinging pathofexile.com [173.192.44.20] with 32 bytes of data: General failure. General failure. General failure. General failure. Ping statistics for 173.192.44.20: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\tim>ping 173.192.25.23 Pinging 173.192.25.23 with 32 bytes of data: Reply from 173.192.25.23: bytes=32 time=54ms TTL=54 Reply from 173.192.25.23: bytes=32 time=56ms TTL=54 Reply from 173.192.25.23: bytes=32 time=53ms TTL=54 Reply from 173.192.25.23: bytes=32 time=62ms TTL=54 Ping statistics for 173.192.25.23: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 53ms, Maximum = 62ms, Average = 56ms C:\Users\tim>tracert 173.192.25.23 Tracing route to patch101.pathofexile.com [173.192.25.23] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.1.10.1 2 1 ms <1 ms <1 ms 192.168.2.1 3 7 ms 7 ms 6 ms 10.38.112.1 4 11 ms 9 ms 11 ms 70.169.73.90 5 7 ms 8 ms 8 ms chndsysc01-te-8-4.ph.ph.cox.net 70.169.72.201 6 47 ms 45 ms 43 ms sanjbprj02-ae0.0.rd.sj.cox.net 68.1.5.186 7 42 ms 43 ms 42 ms 50.97.16.52 8 50 ms 49 ms 50 ms ae0.bbr02.cs01.lax01.networklayer.com 173.192.1 8.151 9 50 ms 50 ms 49 ms ae7.bbr01.cs01.lax01.networklayer.com 173.192.1 8.166 10 53 ms 55 ms 54 ms ae19.bbr01.eq01.dal03.networklayer.com 173.192. 18.140 11 55 ms 55 ms 54 ms ae0.dar02.sr01.dal01.networklayer.com 173.192.1 8.253 12 56 ms 78 ms 60 ms po2.fcr05.sr06.dal01.networklayer.com 66.228.11 8.223 13 54 ms 54 ms 54 ms patch101.pathofexile.com 173.192.25.23] Trace complete. theory-shadow: http://tinyurl.com/l3nu76x | puncture Last edited by mokaiba on Oct 16, 2014, 9:26:27 PM
| |
|
can you please use winmtr instead? ping and traceroute by themselves aren't nearly as useful.
| |
|
My piety battle caused me to die once because my skills wouldn't work and it lagged out.
screenshot:
Spoiler
Spoiler
not a piety area  http://postimg.org/image/ckqqzt64d/ winmtr:
Spoiler
piety |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 10.1.10.1 - 0 | 135 | 135 | 0 | 0 | 3 | 0 | | 192.168.2.1 - 0 | 135 | 135 | 0 | 0 | 7 | 0 | | 10.38.112.1 - 2 | 127 | 125 | 6 | 10 | 73 | 11 | | 70.169.73.90 - 2 | 127 | 125 | 8 | 12 | 74 | 9 | | chndsysc01-te-8-4.ph.ph.cox.net - 2 | 127 | 125 | 6 | 12 | 77 | 9 | | sanjbprj02-ae0.0.rd.sj.cox.net - 3 | 123 | 120 | 41 | 44 | 59 | 41 | | 50.97.16.52 - 3 | 123 | 120 | 41 | 44 | 106 | 45 | | ae0.bbr02.cs01.lax01.networklayer.com - 3 | 123 | 120 | 49 | 53 | 118 | 51 | | ae7.bbr01.cs01.lax01.networklayer.com - 4 | 121 | 117 | 48 | 52 | 116 | 50 | | ae19.bbr01.eq01.dal03.networklayer.com - 5 | 115 | 110 | 52 | 55 | 67 | 53 | | ae0.dar02.sr01.dal01.networklayer.com - 6 | 111 | 105 | 0 | 57 | 73 | 58 | | po2.fcr05.sr06.dal01.networklayer.com - 6 | 111 | 105 | 0 | 57 | 81 | 56 | | patch101.pathofexile.com - 2 | 127 | 125 | 0 | 56 | 69 | 58 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Spoiler
not piety |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 10.1.10.1 - 0 | 22 | 22 | 0 | 0 | 3 | 0 | | 192.168.2.1 - 6 | 19 | 18 | 0 | 0 | 3 | 0 | | 10.38.112.1 - 6 | 18 | 17 | 8 | 11 | 17 | 9 | | 70.169.73.90 - 6 | 18 | 17 | 9 | 11 | 16 | 11 | | chndsysc01-te-8-4.ph.ph.cox.net - 6 | 18 | 17 | 8 | 11 | 17 | 10 | | sanjbprj02-ae0.0.rd.sj.cox.net - 6 | 18 | 17 | 42 | 45 | 52 | 46 | | 50.97.16.52 - 6 | 18 | 17 | 42 | 44 | 50 | 42 | | ae0.bbr02.cs01.lax01.networklayer.com - 6 | 18 | 17 | 51 | 52 | 55 | 54 | | ae7.bbr01.cs01.lax01.networklayer.com - 6 | 18 | 17 | 50 | 51 | 54 | 50 | | ae19.bbr01.eq01.dal03.networklayer.com - 14 | 15 | 13 | 53 | 55 | 60 | 53 | | ae0.dar02.sr01.dal01.networklayer.com - 14 | 15 | 13 | 0 | 56 | 61 | 57 | | po2.fcr05.sr06.dal01.networklayer.com - 28 | 11 | 8 | 0 | 56 | 57 | 56 | | patch101.pathofexile.com - 6 | 18 | 17 | 0 | 56 | 61 | 58 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider If I go back into the piety area, its 180+ms again. Something in the piety area is causing fram lag and high pings. Video (will be up in about an hour): http://youtu.be/R7EhHoJiLJs ISP speeds http://www.speedtest.net/my-result/3839865419 ----------- EDIT: Seems using a VPN resolved my ping issue. theory-shadow: http://tinyurl.com/l3nu76x | puncture Last edited by mokaiba on Oct 17, 2014, 6:07:06 PM
| |
|
22 packets is WAY too short to get any reasonable idea on the overall network conditions, but that alone looks like a problem.. either between you and your ISP, or with the ISP itself.
The first trace is starting to lose packets inside of the ISP where as the second trace is losing packets between you and your ISP. This packet loss can account for latency spikes as it takes longer for the packets measuring latency to be returned when they're being dropped. Reboot your modem and try again. If you still have issues, you'll likely need to contact your ISP. |
