Just as a marginally-relevant data point, I've got FiOS and it works well, but it's a section that was sold to Frontier in the last few years, and I'm on the West Coast, and some combination of those two differences means I'm not being routed through the Level3 bit that seems to be the main issue. Assuming it's basically congestion in the L3 section or on the Verizon<->L3 link in the Northeast, Verizon really has the most leverage to make things un-suck, but in getting leverage on Verizon, Square may have better odds than the customer, heh. The joys of big-boy routing issues...
I'll try the other two listed as WTFast is giving my system issues on startup. Endless black screens and loading screens before user password ever comes up. Safe mode -> uninstalling works but that's going to get annoying.
What is an ip address of their servers so we can see what our route is?
Try 190.93.243.228, that's their montreal server. But I get incredibly low ping (3ms from Hong Kong) so I'm not sure you can get reliable information (a tracert shows the last hop before this server at a hk isp...)
I don't think that's right...
http://puu.sh/6p9Pl/f734c08247.png
Left is the IP you gave, right is the IP I'm currently connected to at SE.
http://puu.sh/6p9Ud/9edcf5a8d5.png
hahaha I left this running for like 2 minutes and look at the stark difference between my MTR to SE and to whatever that other address is.
Even my first hop, which is the same for both routes, reacts differently pinging SE's servers. What the helllllllllllllllllllllll?
Not a network expert. This is the line from WTFast log I used:
[18:28:02] ffxiv.exe (6084) - 199.91.189.74:54994 open through hk3.wtfast.com>mtl1.wtfast.com proxy chain
Left IP is a SE server (maybe lobby) but w/e. Right, you have their two server's names (I use what they call a chain route using their server in hk then their server in montreal but have same perf if I connect directly to mtl1.wtfast.com).
Then if I ping mtl1.wtfast.com, the IP i gave you was responding to the ping (it's also one of the two IP i get from a ns lookup)
Oh I see now. I thought you meant that was the SE IP. That's actually the WTFast IP.
Yes, the first IP is the (one of the) lobby servers.
Oh, yes, I interpreted lilbubbles question as what was a wtfast server ip address.
still what I gave you can't really be their montreal server despite being the one for mtl1.wtfast.com considering the impossibly low ping i get to this and the short/simple route.
looking at Resource Monitor, I saw that WTFast maintained connection to this address but also to another one which also looks to be in asia. Ping and route are less good so I suspect this is their actual hk server. I'll retry with a direct connection to their montreal server, maybe that'll give the true address for their server over there.
It's a pain in the neck they can't just show the actual route they take
Edit: looks like their Montreal server is 205.204.85.30
I'm experiencing the same issue UK and Italy users are having; constant R0 during prime time which results in time-lag where nothing is happening for 1-15s and everything suddenly speeds up again. Issue is fairly recent, last two weeks, and has gone unnoticed @ SE, it seems. I've used WTFast and the results are the same. Mind you, I'm in Toronto so the route I'm taking, I would hope, is fairly short. Here's hoping this shit actually gets fixed on Monday >_>
i did use Both Wtfast and BattlePing, both to be honest help me greatly and with them i had zero lag issues at all, however i notice the Wtfast had more stable servers than BP but... BP give me way better ping than wtfast.
Bottom line is, you'll need to experiment with different servers and perhaps different VPN services until you find what works for you. Even afterwards, be prepared to tinker. For example, I find that WTFast's Chicago servers yield the numerically lowest ping for me, but going through Texas (which is completely counterintuitive given that I'm in St Louis trying to get to Montreal) is the most stable and gives the least rubberbanding and spikes.
Isn't there a way to blacklist (for lack of the appropriate term) a route? For instance, shouldn't it be possible for me to tell my network connection to not use that montreal.level3 one that is giving us issues? Swear I read that somewhere once.
Well, my trial for WTFast is coming to an end within a week and the problem still isn't fixed. Looks like I'll be subbing to them until this issue with FiOS is fixed =\
Didn't the BP trial DC you every 20 minutes? That isn't very useful for a lot of things.