Question on routing to server

I've recently been having connection issue. A large portion of the issue is likely a local ISP issue. However it prompted me to trace the route I take to the server. I'm in Ohio in the US. I ran the route to both DC and Texas servers, and in both instance I was routed through Europe about half way through it's path. Anyone know why someone in the US, trying to connect to a US server, would need to be routed overseas?

Hello,

Could you please post the logs?

"

Crolansolo wrote:

Anyone know why someone in the US, trying to connect to a US server, would need to be routed overseas?

Like Sarno has asked please post the logs.

As for why this could happen, because your connection is trying to find it's way around the problem area, it's getting so far then it has to take the next best route which just so happens to take you overseas then back.

I would guess that the connection heads to New York then tries to get to DC, but there is a problem between NYC and DC so it takes you over to the EU then back to DC (coming on from a different area which bypasses the problem)

Or it could just be something simple like the ISP messing up routing for some random reason.

I first attempted to use winMTR as Henry_GGG suggestion in this post: https://www.pathofexile.com/forum/view-thread/361292

It seemed unresponsive though. I would tell it to start and it would just sit there til I cancelled it 20 minutes later. So I ended up using http://www.monitis.com instead and this was the result of trying to ping the DC server: http://www.monitis.com/traceroute/index.jsp?url=wdc.login.pathofexile.com&testId=2157327

I also tried the Texas and California servers with similar results. I've seen anywhere from 50+ms latency normally to 600-1200ms when it spikes regularly.