So just curious if anyone else gets 0 received packet.

Because this has been an issue for me since at launch. And after doing some testing with a friend of mine, it seems to be a really bizzare thing, because I'm still sending packets. So when packets stop being received for 10 seconds or more at a time, I see everything lag/freeze on my end. But my friends can still see me move around the game as if nothing was wrong on my end.
Anyone else have this problem?

For clarification, I'm on Balmung. I use Telus out here in Victoria, BC, Canada. Fairly sure it's not a throttling issue as Telus doesn't do that.

Yes, since the last patch.

I have that issue from time to time, though usually it's on my end due to snowstorms.
If you see your packets drop, there's a good chance you might DC. Though I'm sure you've noticed that already. Packets are pretty much your latency, and connection to the server. Not much can really be done about it, as lag is something that's been an issue since beta. The Montreal (Last I checked, this is where all the NA/EU servers were located) servers have been a pain, and they really don't seem to be trying to fix things all that much... and if they are, it hasn't been very noticeable by those affected.

Either way, I would suggest WTFast. It helps with lag quite a bit. It gives a monthly free trial, and then asks for a sub. But as far as I've noticed, you should be able to just reinstall and get a new free month. Dunno if they've changed it or not, as I haven't used it in a few months. If it doesn't help, then not sure what to do :<

Good luck, and hope it helps.

Thread: [NA] Issues Occurring After Patch 2.16 and the Addressing Thereof (Mar. 5)

THey have actually been actively trying to address stability issues they've been able to identify on their end for a while now. The last few maintenances have included changes hoping to resolve some of them. Tonight's is another such attempt.

As to your in route latency... that is something for your ISP to address. And yes, they CAN address it. Getting them to investigate and take action is another story, but it actually is their responsibility. They set up the service agreements for third parties to carry your data off of their lines, and those agreements provide them with a means of enforcement when that third party's service goes south and begins to impact a client's quality of service. If your ISP did not enter into negotiations with these third parties to carry your data across to other networks, you would not be able to access content or even send email to someone using a different ISP--they have to pay someone to connect the dots for them, and with that comes a means to influence them to clean up their act.

The trick is in identifying the symptoms in your routing (tracerts) to your game server (Canada based NA/EU servers start with 199, not the web server starting with 184 that is plastered all over the web), as well as to other common services like Google/YouTube, Netflix, or even another game's server and then forwarding that data to your ISP's tier3 via their support portal/contacts. You may have to be persistent and lean on them.. but they CAN affect changes in your routing to get around some if not all of the congested paths. The fact that a VPN/proxy service can mitigate the issue is proof that such changes will work... and SE has no power over the decisions your ISP and their partners make in routing you from point A to point B. That is all dictated by your ISP and their partner(s) routing policies and analytics.

I'm having the same issue where I lose packets from time to time, although it's not often it happens, the duration is very long (20 seconds), it came to the point where I couldn't finish T5. What I find strange though is it's only happening in JP servers, I check NA servers to see if it's an issue and it isn't.