Final Fantasy XIV Servers Specs.

[Shurrikhan]

Latency has nothing to do with server specs. I get pings in the low 20s from Washington.

You just have a bad route.

Within 500 mi of the server and get 40s-70s, with frequent spikes. On two different ISPs. Both end up garbled once they enter the NTT's service, and bog badly after about 8 PST, especially on Fri/Sat. All other games unaffected. Unlike during HW, none of my VPNs (WTFast, Battleping, Mudfish, Pingzapper) have any real effect on XIV ping or spikes, either, each running into the same issues within the last few hops.

[Valkyrie_Lenneth]

Within 500 mi of the server and get 40s-70s, with frequent spikes. On two different ISPs. Both end up garbled once they enter the NTT's service, and bog badly after about 8 PST, especially on Fri/Sat. All other games unaffected. Unlike during HW, no VPNs have any real effect on XIV ping or spikes, either.

See, I have a bad ISP out here, where occasionally their DNS drops XIV completely, but I just VPN and it boots up fine. Sounds more like an issue with the ISPs going through the same nodes than anything. A VPN can only get you around the issue if there is an alternate path it can take.

[KisaiTenshi]

Great info - thanks for that. So which way do you think my traffic goes (with respect to FF14?). The only nodes I touch are local ones, Ashburn VA and SNJ -> Sacramento.

Well normally I'd say Ashburn would route through Megaport IX (Ashburn) , that's IX for Internet Exchange, not 9. https://prefix.pch.net/applications/...il.php?id=1956 , and Hurricane Electric is in San Jose and peers with them. But NTT has a peering node in Ashburn, but who knows if that's their fiber (ae-2.r23.asbnva02.us.bb.gin.ntt.net).

Interesting to note that Megaport IX peers directly with Riot games (League of Legends) though.

Routes can change frequently, but if you managed to get a direct link between the east coast and the west coast without going through AZ or IL, then you really should not have any network-related issues with the NA game. The complaints that people are having trend towards the SE/NTT or NTT/Comcast peering arrangement. Of which Comcast does peer with NTT, and NTT's largest peer is Level3, so if your ISP is not one of the big 3 US ones (comcast, verizon, at&t) then it's likely getting to NTT via level3.

[Kazrah]

See, I have a bad ISP out here, where occasionally their DNS drops XIV completely, but I just VPN and it boots up fine. Sounds more like an issue with the ISPs going through the same nodes than anything. A VPN can only get you around the issue if there is an alternate path it can take.

It's basically one path going through San Jose that is the problem because it can't handle the load of all the people using it during primetime hours (~5-10pm) and involves a company Comcast is trying to screw over, or at least that's how I've come to understand it.

[dotsforlife]

You can blame NTT. They have a couple of nodes that are notorious for causing some issues. Most people are fine unless they happen to be unfortunate enough to get routed through those bad nodes.

[Nihility]

for me the troubles happen when it's routed through San Jose
If i set a VPN to avoid san jose i never have issues

ups my latency from ~11 to something in the 90's but the spikes do go away

[Kazrah]

for me the troubles happen when it's routed through San Jose
If i set a VPN to avoid san jose i never have issues

ups my latency from ~11 to something in the 90's but the spikes do go away

Yeah, that's the one that always gives NA players issues. Had to edit my post for that.

[Malzian]

for me the troubles happen when it's routed through San Jose
If i set a VPN to avoid san jose i never have issues

ups my latency from ~11 to something in the 90's but the spikes do go away

Yeah, that's the one that always gives NA players issues. Had to edit my post for that.

Part of that problem is that San Jose is right there with Silicon Valley, arguably one would say they most congested network segments in the country despite being one of the most robust. So it makes a bit of ironic sense that any connections travelling through San Jose and not terminating there would hit a lot more congestion than elsewhere.