The time-oriented graphical display can help make clearer what is going on. (For some people restarting the router also helps, too.)Īnyway, PingPlotter might be useful here. Right now, though, it looks like there are several candidates - all outside the AWS area ANet use for hosting - for said:One percent packet loss on your local network is bad, as are the latencies it shows if you are on a wireless network, I'd definitely suggest moving to a wired connection, or at least closer to the AP, to see if that helps. That'd be worth following up with your ISP, if that is gtt.net.Īnyway, PingPlotter might be useful here. (For some people restarting the router also helps, too.)īeyond that, between hops five and six - the gtt.net one, and 89.149, show huge loss and a huge latency increase. One percent packet loss on your local network is bad, as are the latencies it shows if you are on a wireless network, I'd definitely suggest moving to a wired connection, or at least closer to the AP, to see if that helps. you can see every hops with amazon server ip have loss around 30%-50% I doubt 1% loss on my isp side can make me lag for whole 30min when i run winmtr.
theres loss on my isp side too but its only 1% i doubt that can make me lag everyday. i run winmtr from anet for 30minfrom what i see there's a lot of loss in hops with amazon ip. sometimes only in wvw but no lag in pve map, sometimes everything lag. recently this lag/spike getting worse almost unplayable now.
FLAG's own network also offers a utility, with a list of all the said:from SEA too here, already 1 week like this, after moving to AWS ping increase to 300 but still playable, after 1 2 months starting to have spike from time to time. Here's a quick google for example, allowing you to ping from Amazon in Virginia (same as GW2 NA), showing a <10ms ping to 85.95.26.13, whereas an IP in London is around 80ms or 90ms to Amazon in Frankfurt. Always double check these services, such as pinging/tracing and looking up the surrounding hops to estimate just how far it could realistically be. GW2 had the same problem, with people believing the original EU servers were in Texas, since they're registered to NCSoft West. It's showing up as UK because the location is unknown, so they're defaulting to the location of the owner, which is in the UK. whois gives for both10 208 ms 218 ms 208 ms ge-3-1-0.0. 11 294 ms 299 ms 279 ms ae2.0. UK as location, so maybe they are the both end of the atlantik-cable owned by a UK company, still not the shortest path from australia to amazon Said:Anyone can name the 3rd position as he likes, but maybe your right.
0 kommentar(er)
