This is what I can share from a friend without the issue. Canada.
https://i.imgur.com/jPVeLOi.png
Printable View
This is what I can share from a friend without the issue. Canada.
https://i.imgur.com/jPVeLOi.png
AT&T same issues and they claim its SE side and I put ticket in for support they just gave run around that I already did all said things. It been going on for last few days for me. I'm in WI.
My ping has gone down from 120ms to about 83ms. I haven't tried battle content yet but its marginally better. Still about 15ms or so more than normal but I haven't been seeing rubberbanding in the cities at least. Running a trace for the data center does seem to still result in packet loss though.
Still terrible lag for me. Cannot pvp well at all. It is making getting the last few series levels before the new series quite painful. It's been 3+ days now :(
ATT fiber customer in IL. Terrible lag during their peak times. I have to use a vpn and it's back to being decent. Really hope this is resolved soon.
It doesn't seem like mine goes through the 57 though and I'm still having the problem. When I ping my routes I'm just fine until I get to the following IP: 128.241.2.18. As soon as I try to ping that it starts dropping packets.
https://i.imgur.com/eQdMZXW.png
My experience with this game for years has mostly been fine. Of course I have experienced lag before (who hasn't?) But it's not usually persistent like this. Recently upgraded to fiber optics with my Internet Provider and it was working absolutely fine as before until a couple days ago. It's okay while I'm doing casual content, but I want to run current high end and I don't even want to try another deep dive in palace or HoH until this is resolved. It's kind of funny out of combat to see a group of people lurch forward only to stop a few paces and then resume, but it's also worrisome.
AT&T customer in South Carolina.. i have the same issues as everyone else.. other than a few solo quests and just hanging out.. or an old dungeon or island sanctuary.. its largely unplayable.
please fix before 6.4
(begging on knees) :(
Yeah it could be 2 nodes
9 55 ms 55 ms 55 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 * 110 ms 110 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
11 111 ms 110 ms 110 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
12 * * * Request timed out.
13 * 111 ms 109 ms 204.2.29.6