Packets lost connecting to EU/US servers (Proof In pic)

Quote:

---

Originally Posted by Nekodar

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?

---

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.

Quote:

---

Originally Posted by Nekodar

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?

---

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):

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.

---

I also did a normal ping test with 500 pings and got 2% total loss (11 lost).

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.

Quote:

---

Originally Posted by Toludin

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).

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.

---

This is the strange thing. Some people are completely unaffected.

Quote:

---

Originally Posted by ShuyinTakahara

This is the strange thing. Some people are completely unaffected.

---

Yea, the people I routinely play with don't experience the same issue (one from NJ, another from Louisiana). So it's definitely not a ubiquitous issue, but it also seems I'm not the only one with it.

Quote:

---

Originally Posted by Toludin

Yea, the people I routinely play with don't experience the same issue (one from NJ, another from Louisiana). So it's definitely not a ubiquitous issue, but it also seems I'm not the only one with it.

---

It's like some of my Free Company who come from Europe don't get any form of Lagg or slowdown. Yet a few of Us do.

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.

Quote:

---

Originally Posted by Lithera

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.

---

Just to clarify, I got my IP by running a netstat and using the IP associated with the running ffxiv.exe process.