nice work guys. Keep in touch with them on it, even if it's just to send them updated tracerts once a week while they work on it. It took about 2 months of moving me from east coast corridors, to the midwest, to the west coast, and all the way back to east coast again.... but they got me cleaned up pretty good after about 8 weeks. I'm in SC, and was originally going through Charlotte first after my local segments (after moving me from Columbia a few years back when I had issues with XI). For a while I was getting shot through Raleigh (and was staying in 80-90 ms PEAK territory, which was SWEET). I'm back to Charlotte again, but it's down to around 100-110 peak latency now (vs 180+ before), but more importantly, I'm not suffering the nasty losses I was when all this started (at times was nailing 48 packets lost in 100 routinely at some hops).
Just need to keep feeding them data about your specific connection so they know where to look for problems, and they will eventually sort it out.
Code:Tracing route to 199.91.189.74 over a maximum of 30 hops
<Initial hops removed for security>
4 25 ms 23 ms 23 ms xe-7-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.42]
5 32 ms 31 ms 31 ms bu-ether34.atlngamq46w-bcr00.tbone.rr.com [107.14.19.48]
6 28 ms 28 ms 26 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 76 ms 75 ms 78 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
8 75 ms 77 ms 78 ms be2050.ccr21.atl01.atlas.cogentco.com [154.54.0.165]
9 87 ms 85 ms 91 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
10 93 ms 95 ms 95 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
11 108 ms 111 ms 112 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
12 60 ms 50 ms 48 ms 38.122.42.34
13 82 ms 65 ms 64 ms 10.2.2.1
14 61 ms 62 ms 60 ms 192.34.76.2
15 63 ms 63 ms 64 ms 199.91.189.234
16 61 ms 61 ms 61 ms 199.91.189.74
Trace complete.
For Those with Time Warner Cable( Lag Issue)
Printable View
-
11-27-2013, 04:59 AMRaist
-
11-27-2013, 05:20 AMRaistDon't take those IP's at arrstatus as your actual server IP's. They have multiple front-ends for getting into the system, and then you get forwarded to the proper server for the current world/zone you are playing in. Your client may actually be connecting to a different IP then what is listed there. Note also that arrstatus has listed the same IP for different worlds (Adam, Faerie, Blamung all show the same IP address, and this happens for a few other IP's).Quote:
Originally Posted by Gamersciz
Open resmon and find the IP's your ffxiv is using, or run netstat in a CMD prompt while in game to verify for certain which one your client is actually using. For example, my client is connecting to .74, but arrstatus lists Midgard as .28. -
11-27-2013, 05:36 AMCompassion
I am with TWC and the lag was getting worse and worse. I started logging my trace routes and started emailing with TWC sending them my data. It got escalated and they got in touch with me. I called their number, gave them my case, and got transferred to a level 3 tech who ran some diagnostics on my connection. The results came back showing my latency at 9000 ms with a 27% packet loss.
Later on that day, they called me back saying they "restarted my service" and asked for me to check if my connection improved. Let's just say on a tracert hop came back with 2 no responses and a 3000ms latency. So now, I'm waiting on a technician to come out since 9am which they haven't shown up today and it's already 2:30pm cst. Considering a switch to Fios... -
11-27-2013, 05:54 AMGamerscizIf you have the option for FioS, like the full FioS internet not just the crappy DSL then go with FioS hands down. I don't have the option...Quote:
Originally Posted by Compassion
-
11-27-2013, 06:00 AMCompassion
I may end up doing that if this doesn't get resolved soon. I live in Dallas, Texas and a few of my friends that are playing are on Fios and they say they get no lag at all. One of them even warned me about TWC since his experiences were bad. Initially TWC had a cheaper price but I should've listened.
-
11-27-2013, 07:11 AMMogVIIThat's entirely possible but I've never had a problem with them in 14 years of gaming. Squenix rep did a tracert to my public IP and said they have a problem at 4.34.69.66.Quote:
Originally Posted by ZohnoReecho
VPN or not, the problem is in the same place every trace:
8 35 ms 36 ms 36 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
9 36 ms 35 ms 34 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 * * * Request timed out.
11 36 ms 37 ms 35 ms 192.34.76.2
12 47 ms 38 ms 35 ms 199.91.189.234 -
11-27-2013, 07:19 AMninesunzQuote:
Originally Posted by MogVII
Where's your problem? you have super good latency to SE, that node 10 just doesn't reply to ping requests, everyone gets that.
Try ping plotter, it will do constant tracert for you and keep a log. -
11-27-2013, 07:47 AMDontTouchMyHoHosYou are miss reading that. #1 Is were you live number 22 is the destination.Quote:
Originally Posted by Gamersciz
-
11-27-2013, 07:54 AMGamerscizOh I get that. It's the number 9 hop that confuses me. It's in Los Angeles still and jumps from 15ms to 85ms before even leaving my city. That's the part that doesn't make sense to me.Quote:
Originally Posted by DontTouchMyHoHos
-
11-27-2013, 09:42 AMArasiel
Well hopefully this means recognition pushes towards solution