Major ping increase since about a month ago

[Celte]

Routing is outside of what SE can do, for that you need to talk to your internet provider, and you need to keep at them.

Your ISP will likely try to brush you off and blame others, but don't put up with that. They provide the internet to you, and it is always their responsibility to get their BGP tables sorted out.

I get that reasoning, since it was the one I started with when I began looking into the issue. However, I have since discovered people who share my ISP that DO NOT have any issues as well as people who have a different ISP that DO have the issue. At this point I just don't see how it can be on the side of my ISP.

[worldofneil]

At this point I just don't see how it can be on the side of my ISP.

When it comes to routing, sorry but it's always down to your ISP.

I'm simplifying this, but whenever you want to connect to any service on the Internet you tell your Internet provider where you want to go. They in turn then tell you the way on how you can get there. Unfortunately in some cases, like your example where you are being sent via New York, the route they give you is really bad, but that's still on your Internet provider to fix this, they're the ones providing the information on how you get there.

Although the Internet is digital, it is still made up of physical objects in real locations (such as the XIV EU game servers are physically located in Germany). There's also a lot of cabling connecting the Internet together. Much like travelling from one city to another there are many different roads (cables) on how you can get from one place to another, but you don't have a choice in how you get there because your ISP does this for you and I don't know of any ISP that will let you pick your own routing, at least not from a home user connection.

However that being said, the reason VPNs work is that when you connect to their services they in turn try to give you a better route to the destination. To do this thought VPN providers usually have to have multiple servers set up in many different countries. Internet providers (generally) only deal with Internet connectivity in their own state/country so when you want to go to parts of the Internet they don't control, they have agreements with other providers to handle your traffic. Unfortunately it simply comes down to cost and it might not be the best solution for you if it's slowed down, but as long as your traffic gets there then they're happy to send it a way that saves them money.

Square Enix provide the servers for the game, but they have absolutely no control over how your Internet provider routes your traffic. Sorry this answer isn't what you want to hear, but I hope that it's been some help at least.

[Shibi]

I get that reasoning, since it was the one I started with when I began looking into the issue. However, I have since discovered people who share my ISP that DO NOT have any issues as well as people who have a different ISP that DO have the issue. At this point I just don't see how it can be on the side of my ISP.

Do you have a tracert we can look at? It will give a bit of evidence and a direction for you to chase!

for Omega/Chaos the command is:

tracert 195.82.50.9

Networking issues can be frustrating!

[Samuraieira]

Heres one of mine, also from Portugal, like many people here have the same issue since the patch hit.

Tracing route to 195.82.50.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 3 ms 3 ms 3 ms a109-49-80-2.cpe.netcabo.pt [109.49.80.2]
3 3 ms 3 ms 2 ms 10.137.240.206
4 3 ms 3 ms 2 ms 10.255.48.74
5 4 ms 3 ms 2 ms ix-ae-9-0.tcore2.pv9-lisbon.as6453.net [195.219.214.17]
6 103 ms 105 ms 102 ms if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
7 104 ms 103 ms 103 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
8 * * * Request timed out.
9 * * * Request timed out.
10 127 ms 102 ms 102 ms if-ae-66-2.tcore3.nto-newyork.as6453.net [80.231.130.106]
11 102 ms 102 ms 102 ms 63.243.186.19
12 103 ms 103 ms 103 ms nyk-bb2-link.ip.twelve99.net [62.115.135.132]
13 174 ms 174 ms 174 ms ldn-bb1-link.ip.twelve99.net [62.115.113.21]
14 208 ms 208 ms 208 ms prs-bb1-link.ip.twelve99.net [62.115.135.25]
15 208 ms * 208 ms ffm-bb1-link.ip.twelve99.net [62.115.123.12]
16 208 ms 210 ms 208 ms ffm-b10-link.ip.twelve99.net [62.115.137.227]
17 207 ms 205 ms 205 ms kddi-ic301630-ffm-b10.ip.twelve99-cust.net [62.115.32.110]
18 206 ms 207 ms 206 ms 195.82.60.29
19 205 ms 205 ms 205 ms 195.82.61.14
20 1214 ms * 1402 ms 195.82.50.230
21 205 ms 205 ms 205 ms 195.82.50.10