My thread was one of those.
Had to think of my own solution. I used a VPN in the past for wow when it had issues with time warner. Just tried one for ARR and it is AMAZING. 0 lag issues now.
I highly suggest anyone looking for an immediate fix to try out Battleping...
Well, I don't have the mentioned hop on my trace but I have started having random disconnection problems after the September 3 server maintenance. I had no disconnection problems prior to that date, when I could connect to the server. My problem mostly manifests when doing dungeons where I get lag spikes where everyone stops moving for 10-15 seconds then everything updates and will be fine for a few more minutes where it will do it again. Sometimes the lag will last longer and that is normally when I will get disconnected.
In normal play, I do disconnect (mostly in primetime hours) but I don't have the lag spikes like I do in the dungeons.
Here is my tracert:
Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 2 ms 3 ms 2 ms 10.0.1.1
2 9 ms 10 ms 10 ms 10.234.0.1
3 11 ms 17 ms 10 ms 10.41.0.13
4 34 ms 28 ms 29 ms 10.41.0.6
5 25 ms 25 ms 26 ms 10.50.0.2
6 25 ms 25 ms 30 ms te0-0-0-14.ccr21.atl04.atlas.cogentco.com [38.122.46.113]
7 27 ms 33 ms 27 ms be2034.ccr21.atl01.atlas.cogentco.com [154.54.6.113]
8 31 ms 30 ms 34 ms te0-2-0-3.ccr21.dca01.atlas.cogentco.com [154.54.24.9]
9 52 ms 40 ms 37 ms te0-0-0-20.mpd21.jfk02.atlas.cogentco.com [154.54.26.178]
10 44 ms 45 ms 54 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
11 46 ms 49 ms 44 ms 38.122.42.34
12 * * * Request timed out.
13 46 ms 48 ms 52 ms 192.34.76.2
14 48 ms 45 ms 49 ms 199.91.189.234
15 49 ms 51 ms 58 ms 199.91.189.74
Trace complete.
Bumping thread.
Right there with you with RCN, tiscali.net, and many, many 90000's.
So, I have no idea why or how, but my lag has gone away. After a week of it constantly, it has finally gone away. Both times I logged in today, I was lag free. The only thing I can think that I've done differently from some of you here is that I posted in the Technical Support section of the Japanese forums, in Japanese. I live in Japan, and my ISP is through OCN / NTT Flets Hikari, but I had contacted them and was told the problem was on Square-Enix's end, so I'm confused as to how this got worked out. I'm not sure what this means, but here it is. Make of it what you will. If the lag comes back or I get 90000 errors again, I'll be sure to post about it.
tracert neolobby02.ffxiv.com
Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 8 ms 10 ms 8 ms 10.50.192.1
3 13 ms 10 ms 9 ms ten0-0-0-7.ORLD02-ser1.bhn.net [72.31.239.224]
4 12 ms 14 ms 20 ms ten0-0-0-7.orld01-ser1.bhn.net [72.31.194.58]
5 23 ms 21 ms 26 ms ten0-8-0-0.tamp20-CAR1.bhn.net [71.44.1.210]
6 21 ms 16 ms 21 ms 71.44.3.92
7 17 ms 15 ms 23 ms 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com [66
.109.6.96]
8 41 ms 43 ms 42 ms ae-0-0.a1.pit75.tbone.rr.com [66.109.1.70]
9 40 ms 42 ms 41 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
10 41 ms 39 ms 41 ms ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
11 62 ms 66 ms 62 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
12 62 ms 61 ms 69 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
13 62 ms 60 ms 62 ms be2010.ccr22.mci01.atlas.cogentco.com [154.54.46
.217]
14 60 ms 58 ms 60 ms te0-7-0-4.ccr22.ord01.atlas.cogentco.com [154.54
.30.102]
15 75 ms * 81 ms be2080.ccr22.yyz02.atlas.cogentco.com [154.54.42
.6]
16 70 ms 70 ms 69 ms be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25
.26]
17 67 ms 68 ms 67 ms 38.122.42.34
18 * * * Request timed out.
19 66 ms 68 ms 65 ms 192.34.76.2
20 70 ms 66 ms 79 ms 199.91.189.234
21 65 ms 82 ms 65 ms 199.91.189.74
Trace complete.
OK, I get this problem too. I'll point out again that while I can't play the game at all, my girlfriend plays on the same connection with no problems.
Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 12 ms 10 ms 13 ms cpc22-stav14-2-0-gw.17-3.cable.virginmedia.com [
92.233.1.1]
2 16 ms 15 ms 16 ms aztw-core-2b-ae7-719.network.virginmedia.net [80
.1.243.217]
3 20 ms 19 ms 18 ms brhm-bb-1c-ae13-0.network.virginmedia.net [80.1.
240.177]
4 54 ms 19 ms 20 ms brhm-bb-1b-ae11-0.network.virginmedia.net [62.25
3.174.101]
5 42 ms 23 ms 25 ms teln-ic-1-ae0-0.network.virginmedia.net [212.43.
163.250]
6 22 ms 23 ms 23 ms m282-mp2.cvx3-a.ltn.dial.ntli.net [213.104.85.26
]
7 24 ms 27 ms 24 ms 154.54.72.194.bcube.co.uk [154.54.72.194]
8 30 ms 30 ms 29 ms te0-3-0-0.ccr22.lpl01.atlas.cogentco.com [154.54
.60.110]
9 29 ms 30 ms 28 ms te0-1-0-3.ccr21.lpl01.atlas.cogentco.com [154.54
.37.145]
10 100 ms 100 ms 99 ms te0-2-0-1.ccr21.ymq02.atlas.cogentco.com [154.54
.87.62]
11 100 ms 98 ms 99 ms 38.122.42.34
12 * * * Request timed out.
13 113 ms 98 ms 101 ms 192.34.76.2
14 127 ms 100 ms 98 ms 199.91.189.234
15 97 ms 98 ms 96 ms 199.91.189.74
Trace complete.
Started today for me and to be honest getting frustrated as hell because I have had every error being posted about this bloody game. This ISN'T a FTP THIS IS A PTP......
I don't know anything about networks, I do know I just used battleping (Vpn) and it is fine now. Well better. I used Battleping just to start and get into the game then I closed Battleping completely and still seems fine..... fark knows and I'm just Pissed off because as I said I've had every error thrown at me and it's becoming a real downer
But VPN are dangerous, or not? I don't know too much about this things
Same here. I have played one hour of ARR without any lag or disconnects, that is the first time since Sunday night. I will report back later if lag/disconnects happen again or if it's lag free/disconnect free. I haven't changed anything myself today in an effort to try and fix this it should be noted.
I'm using Spotflux and it's free. i suppose it's up to you hehe http://download.cnet.com/Spotflux/30...-75762054.html I hope it's only a temporary fix :)
I just used Battleping and got into the game for the first time in days, thank you Soulsa :D
So some got it fixed posting on Japanese forums. Doesn't that feel like there playing favorites. How many English threads with how many posts and nothing!
U post in JP and they look into the service provider and fix the compatibility issue ?
Why did they even open a NA EU branch if this is how its handled.
I just don't understand. When I run a tracert to 199.91.189.21 (The IP I see when running my resource monitor when playing FFXIV) I do not see anything strange. I am also running WinMTR and I see no packet loss to the same IP, or any hops on the way. However, I am still experiencing crippling lag and disconnects every 10 to 15 minutes. Can someone interpret this?
Has anyone found a temporary fix for the disconnect? I've decided to use the free trial for BattlePing. It greatly helped my lag issue that just came up. But! I still disconnect.
3rd day: 20 Connection Lost
4th day: 25 Connection Lost
5th day: 31 Connection Lost
The problem is getting worst... and I am now entering the 6th day of "90k Reborn".
It's almost like my first experience with the 90k errors back in Phase 4 but, this time, the "stuck in another world" state left its place for the "lag spikes" frenzy.
Hi guys,
I don't use RCN and I'm not trying to hijack, but I'm also in Brooklyn, NY and am with Optimum Online. I've been running ping tests since about a week and a half ago when my connection became highly unstable and today did traceroutes after seeing this thread.
Here are my results:
This is pinging the neolobby02, I keep getting timed out at 7 and 11-- no idea what it's failing to ping though.
Code:Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 16 ms 10.240.168.29
3 7 ms 7 ms 8 ms 67.59.229.177
4 10 ms 11 ms 11 ms rtr4-ge1-1.mhe.hcvlny.cv.net [67.83.222.5]
5 11 ms 11 ms 10 ms 451be07d.cst.lightpath.net [65.19.99.125]
6 12 ms 12 ms 16 ms 64.15.0.205
7 * * * Request timed out.
8 16 ms 12 ms 11 ms te0-6-0-5.ccr21.jfk02.atlas.cogentco.com [154.54.47.21]
9 * 28 ms 20 ms be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
10 * 21 ms 20 ms 38.122.42.34
11 * * * Request timed out.
12 26 ms 18 ms 19 ms 192.34.76.2
13 19 ms 19 ms 23 ms 199.91.189.234
14 20 ms 19 ms 23 ms 199.91.189.74
Trace complete.
Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 10.240.168.29
3 7 ms 8 ms 7 ms 67.59.229.177
4 11 ms 10 ms 11 ms rtr4-ge1-1.mhe.hcvlny.cv.net [67.83.222.5]
5 11 ms 11 ms 11 ms 451be07d.cst.lightpath.net [65.19.99.125]
6 27 ms 12 ms 12 ms rtr4-tg10-1.in.nycmnyzr.cv.net [64.15.0.5]
7 * * * Request timed out.
8 12 ms 11 ms 11 ms te0-6-0-5.ccr21.jfk02.atlas.cogentco.com [154.54.47.21]
9 19 ms 19 ms 19 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
10 19 ms 19 ms 19 ms 38.122.42.34
11 * * * Request timed out.
12 20 ms 18 ms * 192.34.76.2
13 19 ms 19 ms 19 ms 199.91.189.234
14 19 ms 19 ms 20 ms 199.91.189.74
Trace complete.
This is pinging what I believe to be my server IP (Midgardsormr), again, stopping at 7 and 11 with no idea what it's trying to ping.
Regarding this week, it's been sporadic with lag and 90k disconnects but last night was far the worst. I couldn't remain in-game for more than 5-minutes at any given time, there was one window of opportunity which lasted like 15-minutes which was enough to break into 50. After that though, it was just disconnects left and right. Today I can't even login to the game without getting disconnected between 5-10 minutes =[Code:Tracing route to 199.91.189.25 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 6 ms 10.240.168.29
3 17 ms 11 ms 11 ms 67.59.244.61
4 11 ms 8 ms 10 ms rtr3-ge2-1.mhe.hcvlny.cv.net [67.83.222.9]
5 13 ms 11 ms 11 ms 451be07d.cst.lightpath.net [65.19.99.125]
6 13 ms 11 ms 11 ms 451be081.cst.lightpath.net [65.19.120.129]
7 * * * Request timed out.
8 21 ms 10 ms 11 ms te0-1-0-0.mpd21.jfk02.atlas.cogentco.com [154.54.44.69]
9 * 34 ms 33 ms be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
10 19 ms 19 ms 19 ms 38.122.42.34
11 * * * Request timed out.
12 36 ms * * 192.34.76.2
13 19 ms 19 ms 19 ms 199.91.189.234
14 20 ms 19 ms 19 ms 199.91.189.25
Trace complete.
Tracing route to 199.91.189.25 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 8 ms 7 ms 10.240.168.29
3 8 ms 8 ms 6 ms 67.59.244.61
4 20 ms 11 ms 10 ms rtr3-ge2-1.mhe.hcvlny.cv.net [67.83.222.9]
5 10 ms 13 ms 11 ms 451be0cd.cst.lightpath.net [65.19.99.205]
6 13 ms 14 ms 12 ms rtr4-tg10-1.in.nycmnyzr.cv.net [64.15.0.5]
7 * * * Request timed out.
8 11 ms 11 ms 11 ms te0-1-0-0.mpd21.jfk02.atlas.cogentco.com [154.54.44.69]
9 19 ms 18 ms 20 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
10 20 ms 20 ms 20 ms 38.122.42.34
11 * * * Request timed out.
12 18 ms 19 ms 19 ms 192.34.76.2
13 20 ms 22 ms 19 ms 199.91.189.234
14 19 ms 19 ms 19 ms 199.91.189.25
Trace complete.
I don't think that was it, because checking Starlight's posts showed she didn't post over there, and she's based in the US. At least, I think she is, as she has RCN as a service provider. No idea why this suddenly just started working for us. I was finally able to run two instances with no issues whatsover. It's a bit bizarre.
***UPDATE***
as of Saturday Sept 7th, 2013, I logged on at 9am EST , and now it's almost 2pm EST,
no lag or disconnect so far.
Been disconnected at least 5 times within the last hour 12:00 - 1PM CST.
I've been so patient with SE until now!!!! WTF is happening? Honestly, at some point the fuck up must end!
13 hops so far to get to the server. This is ridiculous for the west coast players.
Are you on Bright House Networks? I noticed your bhn hops and I'm on Bright House and having lag issues as well.
traceroute to neolobby02.ffxiv.com (199.91.189.74), 64 hops max, 52 byte packets
1 * * *
2 ten0-0-0-7.orld52-ser2.bhn.net (97.69.193.142) 12.663 ms 8.667 ms 11.015 ms
3 ten0-7-0-4.orld48-car2.bhn.net (71.44.60.128) 14.861 ms
ten0-1-0-2.orld48-car2.bhn.net (72.31.194.122) 19.236 ms
ten0-7-0-4.orld48-car2.bhn.net (71.44.60.128) 12.568 ms
4 ten0-3-0-12.orld71-car2.bhn.net (72.31.194.200) 15.826 ms
ten0-10-0-5.orld71-car2.bhn.net (71.44.61.44) 27.849 ms 25.906 ms
5 ten0-8-0-0.tamp20-car2.bhn.net (71.44.1.214) 31.207 ms
ten0-13-0-0.tamp20-car2.bhn.net (71.44.1.212) 21.795 ms
ten0-8-0-0.tamp20-car2.bhn.net (71.44.1.214) 29.612 ms
6 72.31.208.2 (72.31.208.2) 17.888 ms
hun0-7-0-0-tamp20-cbr1.bhn.net (72.31.117.164) 23.889 ms
hun0-6-0-0-tamp20-cbr1.bhn.net (72.31.117.160) 23.223 ms
7 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com (66.109.6.96) 19.647 ms 24.162 ms 22.549 ms
8 ae-0-0.a1.pit75.tbone.rr.com (66.109.1.70) 47.377 ms 49.622 ms 45.104 ms
9 ae-0-0.cr0.dfw10.tbone.rr.com (66.109.6.39) 47.413 ms 51.351 ms 46.413 ms
10 * ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 48.292 ms
ae0.pr1.dfw10.tbone.rr.com (107.14.17.232) 39.129 ms
11 te0-4-0-17.ccr21.dfw03.atlas.cogentco.com (154.54.11.49) 102.918 ms 109.304 ms 106.632 ms
12 be2031.ccr21.dfw01.atlas.cogentco.com (154.54.7.45) 100.700 ms *
be2032.ccr22.dfw01.atlas.cogentco.com (154.54.6.53) 109.501 ms
13 be2064.mpd21.mci01.atlas.cogentco.com (154.54.5.217) 104.667 ms
be2010.ccr22.mci01.atlas.cogentco.com (154.54.46.217) 96.724 ms
be2012.ccr21.mci01.atlas.cogentco.com (154.54.2.113) 107.456 ms
14 * te0-7-0-1.mpd22.ord01.atlas.cogentco.com (154.54.25.78) 104.025 ms
te0-4-0-3.mpd21.ord01.atlas.cogentco.com (154.54.30.169) 107.359 ms
15 be2079.ccr21.yyz02.atlas.cogentco.com (154.54.27.182) 317.816 ms
be2080.ccr22.yyz02.atlas.cogentco.com (154.54.42.6) 113.619 ms
be2081.ccr21.yyz02.atlas.cogentco.com (154.54.42.10) 122.979 ms
16 be2090.ccr21.ymq02.atlas.cogentco.com (154.54.30.206) 113.077 ms
be2092.ccr21.ymq02.atlas.cogentco.com (154.54.25.26) 106.778 ms 106.663 ms
17 38.122.42.34 (38.122.42.34) 68.650 ms 70.308 ms 70.026 ms
18 * * *
19 192.34.76.2 (192.34.76.2) 68.423 ms 69.165 ms 69.902 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
I'm assuming these in red are timeouts and if that has anything to do with the problem I'm having.
running and then got error 90000
It got fixed for me! Played all day yesterday without any problem. Did FATEs, a dungeon, traveled around: no problem at all.
Not necessarily. It just means that a router is refusing response to ICMP requests, therefor it's not passing any. Some data centers block ICMP on purpose.
Here's mine:
Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
5 14 ms 15 ms 12 ms rc4wt-pos15-0-0.wa.shawcable.net [66.163.76.210]
6 18 ms 23 ms 15 ms rc2wt-ge6-2-1.wa.shawcable.net [66.163.68.21]
7 12 ms 15 ms 13 ms ix-1-2-1-0.tcore1.00S-Seattle.as6453.net [64.86.123.25]
8 203 ms 202 ms 204 ms if-1-0-0-3.core1.00S-Seattle.as6453.net [64.86.123.6]
9 91 ms 90 ms 81 ms if-8-2-3-0.tcore2.CT8-Chicago.as6453.net [64.86.124.30]
10 95 ms 91 ms 81 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
11 97 ms 84 ms 84 ms 66.198.96.50 (TATA Montreal)
12 147 ms 84 ms 82 ms 192.34.76.2 (Ormuco Montreal)
13 83 ms 83 ms 84 ms 199.91.189.234 (Eidos Montreal (Ormuco))
14 82 ms 82 ms 82 ms 199.91.189.74 (Eidos Montreal (Ormuco))
Trace complete.
Kinda odd that it goes Vancouver-Seattle-Chicago-Montreal, my ISP is Shaw Communications.
I'm never getting the 90000 error, but the game is crashing after usually about 30 seconds of extreme lag (happens most often near zone edges)
I find if I let go of the mouse and keyboard, it will usually not crash, but it will remain lagged. If I minimize, ctrl-alt-del, or basically do anything to take focus away from it while it's lagging, it will result in a black screen, but the audio will resume working. If you punch esc, you can hear the menu come up, or at least I think it's the menu.
The game will work for anywhere between a few minutes and maybe 2 hours. Note that every crash sends a problem report to Microsoft. There's 27 reports of which 11 of them were on the 4th. The errors themselves are showing up as 0xc0000005 (Access Violation.) Note that I have DEP enabled on the CPU, and this may explain why the game client crashes and not simply throws itself back to the desktop.
Don't get me wrong, the game is playable enough, just the crashing/dc is unpredictable, that it would likely result in people not subscribing, who wants to pay for beta-quality... again.
Is anyone with Time Warner Cable having issues? Just started having 90000 disconnect issues. Did a traceroute and didn't notice anything in particular that was odd but this has been an issue all day today for me and only today.
Not seeing tiscali but I'm constantly getting a time out at #11 out of 14.
I'm not an RCN customer, but Verizon FiOS.
The problem for me is the TINET hops.
8 41 ms 39 ms 37 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 41 ms 37 ms 40 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
Reply from 216.221.156.110: bytes=64 time=39ms TTL=250
Reply from 216.221.156.110: bytes=64 time=37ms TTL=250
Request timed out.
Request timed out.
Reply from 216.221.156.110: bytes=64 time=40ms TTL=250
Reply from 216.221.156.110: bytes=64 time=34ms TTL=250
Reply from 216.221.156.110: bytes=64 time=33ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=32ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=39ms TTL=250
From Cox Communications in Las Vegas, NV. Both at home and at the office I have lag with TINET hops as well then again with Eidos Montreal.
Quote:
3 1 ms 1 ms 1 ms wsip-24-120-105-81.lv.lv.cox.net [24.120.105.81]
4 8 ms 7 ms 7 ms 10.90.64.1
5 9 ms 9 ms 7 ms 24-234-16-105.ptp.lvcm.net [24.234.16.105]
6 9 ms 10 ms 13 ms 24-234-6-233.ptp.lvcm.net [24.234.6.233]
7 9 ms 9 ms 9 ms 24-234-6-250.ptp.lvcm.net [24.234.6.250]
8 24 ms 21 ms 27 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
9 22 ms 15 ms 80 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
10 101 ms 107 ms 100 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
11 110 ms 101 ms 101 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
12 106 ms 102 ms 92 ms 192.34.76.2
13 96 ms 95 ms 95 ms 199.91.189.234
14 113 ms 107 ms 111 ms 199.91.189.74
im in washington dc and it takes me 13 hops to get to the server
Also in Las Vegas here with Cox Communications. Mine is similar:
Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.89.0.1
3 11 ms 9 ms 8 ms 24-234-16-101.ptp.lvcm.net [24.234.16.101]
4 10 ms 8 ms 8 ms 24-234-6-245.ptp.lvcm.net [24.234.6.245]
5 8 ms 8 ms 8 ms 24-234-6-222.ptp.lvcm.net [24.234.6.222]
6 21 ms 20 ms 21 ms langbbrj01-ae2.rd.la.cox.net [68.1.1.14]
7 20 ms 14 ms 14 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
8 102 ms 94 ms 101 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 106 ms 99 ms 108 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 106 ms 105 ms 109 ms 192.34.76.2
11 100 ms 101 ms 101 ms 199.91.189.234
12 94 ms 93 ms 102 ms 199.91.189.74
Trace complete.
TWC here. 90000 sometimes every 5 minutes. I don't know if it is related to FFXIV though. Honestly, I do a tracert and if I ping the first IP past my gateway (so a TWC/RoadRunner IP) and it times out there - about 1.5% packet loss over 24 hours.
That seems like a TWC problem... I had TWC put a modem watch on my modem. Supposedly they see it "dropping off" every 5-10 minutes for 10 seconds. This is with or without FFXIV running.