100ms latency in Softlayer's network between Denver and Dallas

I just started playing the game about a week ago, and I am not happy with the desync and latency issues that I am having.

I am obscuring the first few hops of this Windows traceroute for privacy. I don't have an MTR output available for you at this time, but these results have been consistent for me over the last few days. This doesn't appear to be a temporary or intermittent problem.

In-game, I've never seen less than 175ms for my latency graph.

8 31 ms 36 ms 27 ms te2-5.bbr01.wb01.sea01.networklayer.com [4.71.152.138]
9 19 ms 25 ms 21 ms ae7.bbr01.wb01.sea02.networklayer.com [173.192.18.186]
10 49 ms 60 ms 49 ms ae0.bbr01.cs01.den01.networklayer.com [173.192.18.145]
11 156 ms 156 ms 147 ms ae12.bbr02.eq01.dal03.networklayer.com [173.192.18.138]
12 157 ms 156 ms 148 ms ae1.dar01.sr01.dal01.networklayer.com [173.192.18.255]
13 144 ms 149 ms 155 ms po1.fcr05.sr06.dal01.networklayer.com [66.228.118.221]
14 147 ms 155 ms 146 ms patch101.pathofexile.com [173.192.25.23]

Between those two hops in Softlayer's network, 100ms is consistently being added. That den and dal I am assuming is Denver and Dallas.

And just to help you and google out:

https://www.softlayer.com/press/release/1941/softlayer-now-powers-online-games-for-more-than-100-million-players

I'm sure that this isn't the kind of post IBM/Softlayer wants to be seen. Hopefully you can motivate them to fix this.

This is probably affecting all of your players in the greater northwest and center-west US, so this is a major issue.

EDIT: Fixed inability to count.

Create WinMTR, point out issue to ISP, you are their customer, they're causing connectivity issues on your end as a result of their routing...

"

jmomo wrote:

9 19 ms 25 ms 21 ms ae7.bbr01.wb01.sea02.networklayer.com [173.192.18.186]
10 49 ms 60 ms 49 ms ae0.bbr01.cs01.den01.networklayer.com [173.192.18.145]
11 156 ms 156 ms 147 ms ae12.bbr02.eq01.dal03.networklayer.com [173.192.18.138]
12 157 ms 156 ms 148 ms ae1.dar01.sr01.dal01.networklayer.com [173.192.18.255]
13 144 ms 149 ms 155 ms po1.fcr05.sr06.dal01.networklayer.com [66.228.118.221]
14 147 ms 155 ms 146 ms patch101.pathofexile.com [173.192.25.23]

Yeah, I'd agree this persistent increase in latency is caused between Denver and Dallas, which should have less of an increase than between Seattle and Denver... but I'm not sure if there is more going on in this route than this trace allows us to see. Do an MTR for a few minutes (300 cycles at least) and post the results, and also send it in to the support email so they can send it upstream.