http://img.photobucket.com/albums/v5...pscdae0838.png
To all you tech savvy people. What does that tell you?. I ran that for 10 minutes. Now you can see. It's totally unplayable.
Printable View
http://img.photobucket.com/albums/v5...pscdae0838.png
To all you tech savvy people. What does that tell you?. I ran that for 10 minutes. Now you can see. It's totally unplayable.
Looks like a lot of hops.
I just launched this program, I will post results later on.
here is the JP results
http://img.photobucket.com/albums/v5...psd7cf5e79.png
Mm, look at dem perfect JP servers.
So what some of you are saying is that it's SE's fault that a node not under SE's control (judging by the names in the trace) is having some sort of problem causing issues for you?
Odin (EU)
Hope they'll give us equal quality and service soon :|
Yes!
And it doesn't take an understanding in IT to know this.
It began when the servers updated, no earlier, no later and has been horrifying ever since. I don't care what excuse SE produces, enough is enough, they just want to hide our issues so they can get good reviews.
I have not mentioned It was SE's fault anywhere In the thread. Way I see it. You don't bring a donkey to a Grand National. Here's my example. Square got in a bunch of servers but also with those servers Instead of getting stallions got donkey's and that's where I believe the faults are. The Donkeys are slowing down the race. (Donkeys = Bad servers)
Sorry about my weird terminology In the last post. :cool:
Here are my results (just using pathping command, connecting to Famfrit from NYC on TWC):
I also did a normal ping test with 500 pings and got 2% total loss (11 lost).Quote:
Tracing route to 199.91.189.44 over a maximum of 30 hops
0 PC [192.168.1.5]
1 192.168.1.1
2 10.32.128.1
3 gig-0-3-0-24-nycmnya-rtr2.nyc.rr.com [24.29.104.110]
4 bun101.nycmnytg-rtr001.nyc.rr.com [184.152.112.107]
5 bun6-nycmnytg-rtr002.nyc.rr.com [24.29.148.250]
6 ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
7 107.14.17.171
8 te0-7-0-29.ccr21.jfk05.atlas.cogentco.com [154.54.13.185]
9 be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.13]
10 be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
11 38.122.42.34
12 10.2.2.1
13 192.34.76.2
14 199.91.189.234
15 199.91.189.44
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC [192.168.1.5]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.32.128.1
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% gig-0-3-0-24-nycmnya-rtr2.nyc.rr.com [24.29.104.110]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% bun101.nycmnytg-rtr001.nyc.rr.com [184.152.112.107]
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% bun6-nycmnytg-rtr002.nyc.rr.com [24.29.148.250]
0/ 100 = 0% |
6 11ms 0/ 100 = 0% 0/ 100 = 0% ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
0/ 100 = 0% |
7 14ms 0/ 100 = 0% 0/ 100 = 0% 107.14.17.171
0/ 100 = 0% |
8 49ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-29.ccr21.jfk05.atlas.cogentco.com [154.54.13.185]
1/ 100 = 1% |
9 --- 100/ 100 =100% 99/ 100 = 99% be2062.mpd21.jfk02.atlas.cogentco.com [154.54.7.13]
0/ 100 = 0% |
10 --- 100/ 100 =100% 99/ 100 = 99% be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134]
0/ 100 = 0% |
11 25ms 4/ 100 = 4% 3/ 100 = 3% 38.122.42.34
0/ 100 = 0% |
12 --- 100/ 100 =100% 99/ 100 = 99% 10.2.2.1
0/ 100 = 0% |
13 28ms 6/ 100 = 6% 5/ 100 = 5% 192.34.76.2
0/ 100 = 0% |
14 26ms 1/ 100 = 1% 0/ 100 = 0% 199.91.189.234
2/ 100 = 2% |
15 25ms 3/ 100 = 3% 0/ 100 = 0% 199.91.189.44
Trace complete.
Anecdotally, I experience frequent, minor lag spikes in game, especially noticeable in group content (FATEs or dungeons/hests). They'll last just a half a second or so, so it's not a killer, but it does make avoiding some mechanics a bit tougher.
You people do realize that a traceroute shows responses from all servers until it reaches the final destination (se)... Plus lag or high pings can be caused by other things such as high traffic, internet providers, and rerouting of hubs because of downed servers... Stop blaming se for something that isn't on their end... They control their servers only not the path of how your connection gets there...
Are you sure you're pinging a game server? That IP address in the OP doesn't match what I've seen for the NA/EU Datacenter located worlds or the NA/EU Lobby server which all start with 199 (Toludin's trace through command line uses a 199 address which I would assume is Famrit's). The packet loss in the OP is definitely at the end of the traceroute so there's a good chance it's server end. The question is is that actually a server's address. I routinely get 100% packet loss hops in between myself and the destination but those are fairly meaningless (means routing hardware/software is set to block ICMP). Loss at the destination is the important thing.
I don't pretend to be an expert on these matters, but from the test I ran (and others I've seen), don't these show some amount of packet loss in the last few hops, which are most likely by the time it reaches SE's network? My tests just had IP addresses at the end with the packet loss, no address names, so I'm not sure what they are, exactly.
I play several MMO games and am not having equivalent issues in any of them right now, and haven't had this sort of issue before. It may very well be an issue with how my ISP (TWC) is handling this traffic, or something like that, but it doe seem, for me, to be limited to FFXIV.
If you have any advice or other things I can test to narrow down where the issue is, I'd very much appreciate it.
In most cases I'd say this isn't SE's fault but if you compare traceroutes from other users, towards the end, the last 3–5 hops are all generally the same pathway. There's A LOT of people that seem to have issues, usually a REQUEST TIMED OUT, in the last 5 hops of a trace.
If this is something that is consistent amongst a large group of players, this is not something that "is the player's fault, stop qq'ing" but something that SE needs to address.
I tested ping for entire night now!
I'm pissed that we got eu servers in us but from the other side - for the entire night I had really good and stable connection.
Packet lost - 3 times for almost 10 hours and ping was checked every 2.5 sec.
The ping was stable between 150 and 200 ms. most of the time 160-170.
And be aware that I'm using mobile internet connection with wireless router!
So let's face it - the servers provided by SE are really good and that's hwat makes me happy!