Where is the problem with this connection issue?

is this still going to NY?

dynamic-76-73-171-85.knology.net 3 0.05 5699 5696 10 35 799 39 1314 65 29.55
user-24-214-131-140.knology.net 4 0.02 5699 5698 10 28 694 22 524 61 24.74
76-73-164-101.knology.net 5 0.05 5699 5696 11 29 743 28 544 63 25.93
static-76-73-191-224.knology.net 6 0.00 5699 5699 12 31 660 29 825 57 24.81
dynamic-75-76-35-10.knology.net 7 0.02 5699 5698 12 30 683 29 766 58 24.36
dynamic-75-76-35-6.knology.net 8 0.09 5699 5694 12 31 743 24 900 56 26.35
13335.ch.equinix.com 9 0.09 5699 5694 11 31 680 55 794 59 26.78
Target WTFast.com 10 0.07 5699 5695 12 32 719 39 1077 60 27.36

Really like to know how wtfast is doing the routing. It will help me know what that is to help me sort for a new isp.

called ISP today, phoned with different people in the course of 5 hours. This is what I got:
"We do not control the routing but we can send a tech to your house to look at it"
"We always send it to New York first, that is how it has always been and never changed it"
Me: not acceptable anymore in this day and age
yeah im dropping them soon. tried of the lag from the server move SB gave, hey on the bright side help me realize my ISP is garbage.

using vpn:
2 12 ms 11 ms 11 ms unknown.puregig.net [173.245.202.1]
3 13 ms 13 ms 15 ms 38.142.65.161
4 12 ms 12 ms 14 ms ae-11.r06.chcgil09.us.bb.gin.ntt.net [129.250.9.121]
5 13 ms 13 ms 12 ms ae-1.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.7]
6 90 ms 82 ms 96 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
7 95 ms 96 ms 87 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
8 87 ms 87 ms 88 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
9 93 ms 95 ms 98 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
10 87 ms 146 ms 88 ms 204.2.229.234
11 87 ms 94 ms 86 ms 204.2.229.9

Trace complete.

also this seems to give me the best performance I can find atm:
3 32 ms 36 ms 21 ms 4.35.180.213
4 30 ms 24 ms 22 ms ae-3-3503.edge4.Chicago3.Level3.net [4.69.203.138]
5 22 ms 22 ms 31 ms 4.68.111.70
6 83 ms 73 ms 78 ms ae-21.r06.chcgil09.us.bb.gin.ntt.net [129.250.3.158]
7 25 ms 25 ms 26 ms ae-1.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.7]
8 76 ms 70 ms 71 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 75 ms 74 ms 75 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
10 74 ms 75 ms 72 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
11 72 ms 74 ms 73 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
12 73 ms 74 ms 76 ms 204.2.229.234
13 78 ms 71 ms 72 ms 204.2.229.9

how does this fair?

Those both seem to be pretty good. Disconnects are more from delayed/dropped packets, so unless you're also getting bad lag, a more stable connection is typically the better thing to go after. Granted, less hops and a more direct route usually improve that because it's less chances for something to go wrong.

If your connection to the game seems good with those connections, I'd stick with them. A ping under 100ms is usually seen as extremely good for most MMOs/multiplayer games. (Still depends on how often polling occurs, but in games like FFXIV, that's typically every 200-300ms).

This is the one that seems to be performing the best:
Packets: Sent = 1025, Received = 1017, Lost = 8 (0% loss),
Minimum = 69ms, Maximum = 215ms, Average = 77ms
Packets: Sent = 14109, Received = 13977, Lost = 132 (0% loss), Minimum = 69ms, Maximum = 418ms, Average = 77ms

3 29 ms 15 ms 24 ms te-9-5.csr2.Chi3.Servernap.net [66.252.0.178]
4 21 ms 27 ms 14 ms ae-12.er1.Chi2.Servernap.net [66.252.0.70]
5 24 ms * 25 ms Pccw-br04-Chc01.er1.Chi2.Servernap.net [66.252.3.134]
6 48 ms 28 ms 23 ms ae-19.a01.chcgil09.us.bb.gin.ntt.net [129.250.8.137]
7 90 ms 80 ms * ae-2.r05.chcgil09.us.bb.gin.ntt.net [129.250.5.95]
8 35 ms 17 ms 23 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
9 77 ms 72 ms * ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
10 75 ms 79 ms 80 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
11 86 ms 78 ms * ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
12 * 79 ms 78 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
13 * 74 ms 75 ms 204.2.229.234
14 71 ms 71 ms 73 ms 204.2.229.9

given each hop and ms time, what ya think?
I doono how you feel about what i am gonna say next but this is how i feel from testing things:

I feel a real VPN is getting me better performance then wtfast. It is skipping knology nodes and seems to have lower threashoalds in pings (76-72 never for wtfast) and seems to have lower spike values.

Go for it.

Sometimes other VPNs work better than WTFast, or other "Gaming" VPNs like Pingzapper or MUDFISH. Use what works best for you!

https://i.gyazo.com/77fb3edf0133ef7e...86c6e83dc7.png
no d/cs so far like the experience I got under my ISP, I just found it weird it kept happening at the same occurrence (teleporting to lav beds and d/c during the final CS in DFs)
I just do not understand how it was my ISP when it keeps repeating for the same situations.

Quote:

---

Originally Posted by reiichi

Good luck! Hopefully they can tell you why you're being routed like that. ...or figure out why they're routing like that because it could be a mistake. I don't know enough about gritty networking details or how routing tables are set up, but it could be the case that their hardware's unaware of the NTT Chicago hub, or it was down at their last check, or something else and it was determined that the "better" prioritized route was to NYC. It's probably adjustable although it might require someone with more authority than a customer service tech or a field agent to handle.

---

They are blaming it on SE:
http://forum.square-enix.com/ffxiv/t...-extra-routing.

Reaching destination = success I guess, this is more proof for me SE really needs to test in less then optimal conditions for their coding. The game is way too picky what happens on a single packet loss or how the game is effected by 70-80 ms vs 130-150 ms

Basically I am blaming both, SE for the coding, expecting perfect net, and my ISP not understanding what quality is.

whats this one doing (testing a diff isp)

1 <1 ms <1 ms <1 ms homeportal ----------
2 20 ms 20 ms 20 ms ------------.lightspeed.cicril.sbcglobal.net ------------
3 21 ms 21 ms 21 ms ---------------
4 * * * Request timed out.
5 26 ms 23 ms 23 ms 12.83.43.57
6 25 ms * 22 ms cgcil402igs.ip.att.net [12.122.133.161]
7 22 ms 22 ms 22 ms 192.205.32.194
8 80 ms 80 ms 78 ms ae-11.r05.chcgil09.us.bb.gin.ntt.net [129.250.3.144]
9 21 ms 23 ms 50 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
10 75 ms 74 ms 75 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
11 79 ms 80 ms 79 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
12 79 ms 80 ms 79 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
13 80 ms 79 ms 79 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
14 79 ms * 85 ms 204.2.229.234
15 86 ms 84 ms 86 ms 204.2.229.9