Packet Loss to NA servers only

**Raist** · 12-04-2013 06:03 AM

Originally Posted by misterdapi

[edit] Nevermind. Dude, just go pound sand. I don't want your faux help. Just suck start a chocobo. Seriously. I've read your whole post history. You are cancer.

http://nlworks.com/2013/06/final-fan...ver-locations/

Really... people who have been investigating the source of these problems, discussing it, finding/testing/proving methods to either work around them or get them resolved, sharing all this information, directing them to documentation/sources, etc--all in an effort to help people actually get some relief are a CANCER??!! Then, pray tell... what is your cure?

And what about your tracerts that clearly showed that the path to your game servers was actually considerably different than the ones to the EIDOS web server the OP was originally tracing--think it was like 22 hops to the game servers and only 15 to eidos.com, and if I remember right there was even a slight variance in the path to the border as well. Did you post them here and then edit those trace results out...will see if I can find them later. And why the venomous insulting? Why am I the problem when this same information has been posted out there by many others saying the same thing? A little curious as to what you edited out in that last post... oh well, you're already pushing the limits for censorship from the admins already as is.

Oh, and by the way.. that nlworks site doesn't list the eidos.com IP (184.107.107.176) as a data server. It's also information that was gathered in June, and some of that data may have changed since we moved through more beta phases and have gone into full launch now. Even the numbers you get off the arrstatus pages may not be entirely accurate--go through the list and you will see the same IP assigned to the same servers. I've already noted several times in other threads that it shows a different IP than what my client actually uses. Have you followed the advice and looked up the IP your client is using for your own investigating? I am guessing you did since you have previously posted traces to both the 199.91.189.28 and 199.91.189.74 IP addresses which have been identified as currently in use for the game servers. That is the BEST way to make sure you are getting the proper IP--to check what your client is actually using.

That is, after all what needs to be diagnosed--your specific route to the server you are actually having communication issues with, and not a web server. Which is why I pointed that detail out to the OP. Sorry if someone correcting somebody offends you (that IP routinely gets passed around as a data server IP for XIV, started back around original Beta I think), but facts are facts. Your game is NOT having trouble connecting to a web server housed in a building about 14 blocks away and maintained on someone elses network (i-web segments, XIV is maintained on Ormuco segments). Your own trace results have clearly shown there is potentially a substantial difference in the routes being taken between those servers.

This is important not only because it means you are hitting different routers along the way. It is also important because those endpoints are designed and used for different purposes, and thus have different tolerance levels for acceptable levels of QoS. A webserver can get by with a heck of a lot more jitter/loss than these game servers. Most web site content is static--you download most of it and that's it for the most part until you need to pull more down (unless there's streaming or other active content, of course). Typically, your connection goes into an idle state far more frequently on a generic website than it will when compared to an online game that is constantly streaming dynamic content in both directions in realtime, and that is very dependent on reliable, ordered, timely delivery of that data to function properly.

If you have an ISP's technician actually offering to look at your route to try to find what is going on, it is imperative that they be told the right place to look. They could very easily look at that eidos.com IP, see a slight jitter, then realize it's a webserver and take the stance of nothing being wrong because the jitter is within acceptable limits for the content being served. However, if they are looking at an actual game server, the same level of jitter may raise enough concern for them to take it more seriously.

Edit
hmm... interesting... Since you claimed to have read all my 500 some-odd posts (which I find questionable considering your attitude and response to me in this thread), I decided to glance at your 30-ish posts as well. Interesting how many were copy/pasted reposts. And guess what I found posted a few times? Your traces:

Originally Posted by misterdapi

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 9 ms 8 ms 8 ms READYSHARE [192.168.1.1]
2 43 ms 32 ms 34 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 28 ms 18 ms 18 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 24 ms 23 ms 24 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.162]
5 29 ms 22 ms 25 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 20 ms 28 ms 18 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.102]
7 23 ms 28 ms 28 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 34 ms * 34 ms ix-9-0-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.169]
9 119 ms 118 ms * if-22-2.tcore2.PDI-PaloAlto.as6453.net [66.198.144.73]
10 174 ms 140 ms 118 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
11 133 ms 135 ms 130 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
12 120 ms 128 ms * 66.198.96.58
13 133 ms 158 ms 131 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
14 134 ms 129 ms 149 ms 72.55.128.44
15 121 ms 138 ms 118 ms 184.107.107.176

Trace complete.

C:\Windows\System32>tracert 199.91.189.28

Tracing route to 199.91.189.28 over a maximum of 30 hops

1 6 ms 4 ms 2 ms READYSHARE [192.168.1.1]
2 37 ms 37 ms 30 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 16 ms 18 ms 18 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 24 ms 19 ms 28 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.162]
5 19 ms 24 ms 28 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 24 ms 28 ms 28 ms 107.14.17.132
7 22 ms 24 ms 23 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 68 ms 29 ms 38 ms 66.109.9.122
9 98 ms 108 ms 98 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]
10 92 ms 108 ms 98 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.17]
11 95 ms 97 ms 88 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 88 ms 92 ms 99 ms ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
13 95 ms 98 ms 97 ms ae-61-61.ebr1.Dallas1.Level3.net [4.69.151.126]
14 92 ms 98 ms 116 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]
15 94 ms 119 ms 102 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
16 96 ms 98 ms 98 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
17 94 ms 98 ms 98 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
18 91 ms 128 ms 98 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
19 141 ms 131 ms 126 ms 10.2.2.1
20 129 ms 171 ms 126 ms 192.34.76.2
21 112 ms 118 ms 119 ms 199.91.189.234
22 127 ms 138 ms 122 ms 199.91.189.28

Trace complete.

C:\Windows\System32>tracert 199.91.189.28

Tracing route to 199.91.189.28 over a maximum of 30 hops

1 2 ms 9 ms 8 ms READYSHARE [192.168.1.1]
2 42 ms 38 ms 39 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 12 ms 17 ms 19 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 14 ms 18 ms 20 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.162]
5 22 ms 23 ms 18 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 27 ms 26 ms 14 ms 107.14.17.132
7 18 ms 14 ms 25 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 31 ms 39 ms 32 ms 66.109.9.122
9 96 ms 98 ms 98 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]
10 91 ms 91 ms 95 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.17]
11 91 ms 100 ms 97 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 102 ms 99 ms 98 ms ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
13 91 ms 99 ms 99 ms ae-61-61.ebr1.Dallas1.Level3.net [4.69.151.126]
14 91 ms 96 ms 88 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]
15 93 ms 98 ms 98 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
16 94 ms 134 ms 94 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
17 99 ms * 89 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
18 95 ms 86 ms 93 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
19 127 ms 128 ms 128 ms 10.2.2.1
20 121 ms 128 ms 129 ms 192.34.76.2
21 123 ms 128 ms 126 ms 199.91.189.234
22 128 ms 129 ms 128 ms 199.91.189.28

Trace complete.

C:\Windows\System32>tracert 199.91.189.74

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 2 ms 7 ms <1 ms READYSHARE [192.168.1.1]
2 35 ms 39 ms 48 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 14 ms 18 ms 8 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 20 ms 23 ms 28 ms tge0-9-0-8.ontrcacp01r.socal.rr.com [72.129.6.160]
5 18 ms 31 ms 25 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 20 ms 29 ms 18 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.212]
7 23 ms 28 ms 19 ms 107.14.19.86
8 34 ms 28 ms 55 ms 66.109.9.122
9 97 ms 98 ms 87 ms vlan90.csw4.LosAngeles1.Level3.net [4.69.144.254]
10 91 ms 99 ms 118 ms ae-92-92.ebr2.LosAngeles1.Level3.net [4.69.137.29]
11 89 ms 92 ms 95 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 93 ms 98 ms 98 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]
13 98 ms 98 ms 98 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]
14 93 ms 98 ms 98 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]
15 93 ms 98 ms 108 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
16 93 ms 93 ms 89 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
17 108 ms 98 ms 98 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
18 93 ms 118 ms 98 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
19 * 125 ms 128 ms 10.2.2.1
20 124 ms 128 ms 128 ms 192.34.76.2
21 112 ms 118 ms 128 ms 199.91.189.234
22 111 ms 115 ms 108 ms 199.91.189.74

Trace complete.

C:\Windows\System32>

Just thought I'd put that in there for the record to further emphasize the potential differences in routing to the eidos.com IP in question and an actual game server IP.
<note I cleaned up the quote a bit, but it's the original data that was posted by you yesterday in another thread. Just corrected formatting to make it easier to read>

**misterdapi** · 12-04-2013 11:59 AM

Originally Posted by Raist

Really... people who have been investigating the source of these problems, discussing it, finding/testing/proving methods to either work around them or get them resolved, sharing all this information, directing them to documentation/sources, etc--all in an effort to help people actually get some relief are a CANCER??!! Then, pray tell... what is your cure?

And what about your tracerts that clearly showed that the path to your game servers was actually considerably different than the ones to the EIDOS web server the OP was originally tracing--think it was like 22 hops to the game servers and only 15 to eidos.com, and if I remember right there was even a slight variance in the path to the border as well. Did you post them here and then edit those trace results out...will see if I can find them later. And why the venomous insulting? Why am I the problem when this same information has been posted out there by many others saying the same thing? A little curious as to what you edited out in that last post... oh well, you're already pushing the limits for censorship from the admins already as is.

Oh, and by the way.. that nlworks site doesn't list the eidos.com IP (184.107.107.176) as a data server. It's also information that was gathered in June, and some of that data may have changed since we moved through more beta phases and have gone into full launch now. Even the numbers you get off the arrstatus pages may not be entirely accurate--go through the list and you will see the same IP assigned to the same servers. I've already noted several times in other threads that it shows a different IP than what my client actually uses. Have you followed the advice and looked up the IP your client is using for your own investigating? I am guessing you did since you have previously posted traces to both the 199.91.189.28 and 199.91.189.74 IP addresses which have been identified as currently in use for the game servers. That is the BEST way to make sure you are getting the proper IP--to check what your client is actually using.

That is, after all what needs to be diagnosed--your specific route to the server you are actually having communication issues with, and not a web server. Which is why I pointed that detail out to the OP. Sorry if someone correcting somebody offends you (that IP routinely gets passed around as a data server IP for XIV, started back around original Beta I think), but facts are facts. Your game is NOT having trouble connecting to a web server housed in a building about 14 blocks away and maintained on someone elses network (i-web segments, XIV is maintained on Ormuco segments). Your own trace results have clearly shown there is potentially a substantial difference in the routes being taken between those servers.

This is important not only because it means you are hitting different routers along the way. It is also important because those endpoints are designed and used for different purposes, and thus have different tolerance levels for acceptable levels of QoS. A webserver can get by with a heck of a lot more jitter/loss than these game servers. Most web site content is static--you download most of it and that's it for the most part until you need to pull more down (unless there's streaming or other active content, of course). Typically, your connection goes into an idle state far more frequently on a generic website than it will when compared to an online game that is constantly streaming dynamic content in both directions in realtime, and that is very dependent on reliable, ordered, timely delivery of that data to function properly.

If you have an ISP's technician actually offering to look at your route to try to find what is going on, it is imperative that they be told the right place to look. They could very easily look at that eidos.com IP, see a slight jitter, then realize it's a webserver and take the stance of nothing being wrong because the jitter is within acceptable limits for the content being served. However, if they are looking at an actual game server, the same level of jitter may raise enough concern for them to take it more seriously.

Edit
hmm... interesting... Since you claimed to have read all my 500 some-odd posts (which I find questionable considering your attitude and response to me in this thread), I decided to glance at your 30-ish posts as well. Interesting how many were copy/pasted reposts. And guess what I found posted a few times? Your traces:

Just thought I'd put that in there for the record to further emphasize the potential differences in routing to the eidos.com IP in question and an actual game server IP.
<note I cleaned up the quote a bit, but it's the original data that was posted by you yesterday in another thread. Just corrected formatting to make it easier to read>

184.107.107.176 = http://eu.square-enix.com/en

Want Traceroutes to the actual server? The hell dose it matter what I'm pinging? The end destination is still with in the same city block.

I'm in LA and it takes 10 hops just to get out of the state. WOOO HOOO The rerouted us right into Level3 garbage. Awesome.

3 19 ms 14 ms 18 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 23 ms 28 ms 29 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.16
2]
5 23 ms 28 ms 22 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 19 ms 22 ms 20 ms 107.14.19.32
7 27 ms 19 ms 19 ms 107.14.19.138
8 23 ms 29 ms 30 ms 66.109.9.122
9 95 ms 99 ms 99 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
10 93 ms 95 ms 93 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.2
5]
11 97 ms 98 ms 100 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 104 ms 98 ms 99 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

13 93 ms 99 ms 99 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]

14 90 ms 95 ms 97 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

15 93 ms 88 ms 98 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
16 94 ms 99 ms 99 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177]

17 93 ms 95 ms 90 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

18 98 ms 98 ms 99 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
19 112 ms 119 ms 115 ms 10.2.2.1
20 119 ms 119 ms 119 ms 192.34.76.2
21 109 ms 98 ms 109 ms 199.91.189.234
22 98 ms 98 ms 98 ms 199.91.189.35

Trace complete.

C:\Windows\System32>4:12 PM Pacific time. Rubberband Lag in the cities
The system cannot find the drive specified.

C:\Windows\System32>tracert 199.91.189.35

Tracing route to 199.91.189.35 over a maximum of 30 hops

1 3 ms 9 ms 8 ms READYSHARE [192.168.1.1]
2 32 ms 30 ms 28 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 25 ms 15 ms 19 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 23 ms 26 ms 20 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.16
2]
5 17 ms 26 ms 17 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 22 ms 28 ms 29 ms 107.14.19.32
7 18 ms 26 ms 17 ms 107.14.19.138
8 19 ms 24 ms 30 ms 66.109.9.122
9 106 ms 96 ms 91 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
10 95 ms 99 ms 99 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.2
5]
11 92 ms 90 ms 97 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 93 ms 98 ms 89 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

13 93 ms 101 ms 88 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]

14 92 ms 101 ms 95 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

15 92 ms 101 ms 91 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
16 92 ms 98 ms 95 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177]

17 91 ms 100 ms 99 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

18 93 ms 101 ms 99 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
19 122 ms 130 ms 136 ms 10.2.2.1
20 125 ms 129 ms 127 ms 192.34.76.2
21 110 ms 119 ms 117 ms 199.91.189.234
22 120 ms 107 ms 119 ms 199.91.189.35

Trace complete.

C:\Windows\System32>5:28 pm Pacific Time
The system cannot find the drive specified.

C:\Windows\System32>tracert 199.91.189.35

Tracing route to 199.91.189.35 over a maximum of 30 hops

1 7 ms 8 ms 12 ms READYSHARE [192.168.1.1]
2 102 ms 39 ms 39 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 43 ms 28 ms 21 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 24 ms 32 ms 25 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.16
2]
5 17 ms 28 ms 19 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 22 ms 31 ms 31 ms 107.14.19.32
7 30 ms 21 ms 18 ms 107.14.19.138
8 16 ms 34 ms 18 ms 66.109.9.122
9 90 ms 93 ms 99 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
10 101 ms 91 ms 101 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.2
5]
11 100 ms 98 ms 98 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 102 ms 100 ms 102 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

13 103 ms 98 ms 98 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]

14 102 ms 100 ms 98 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

15 100 ms 99 ms 98 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
16 94 ms 106 ms 102 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177]

17 106 ms 93 ms * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

18 97 ms 95 ms 86 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
19 * 122 ms 128 ms 10.2.2.1
20 128 ms 124 ms 178 ms 192.34.76.2
21 114 ms 121 ms 115 ms 199.91.189.234
22 116 ms 125 ms 106 ms 199.91.189.35

Trace complete.

C:\Windows\System32>5:31 pm pacific
The system cannot find the drive specified.

C:\Windows\System32>tracert 199.91.189.35

Tracing route to 199.91.189.35 over a maximum of 30 hops

1 7 ms 10 ms 7 ms READYSHARE [192.168.1.1]
2 29 ms 33 ms 38 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 13 ms 19 ms 18 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 25 ms 33 ms 23 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.16
2]
5 27 ms 28 ms 35 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 35 ms 29 ms 32 ms 107.14.19.32
7 15 ms 38 ms 27 ms 107.14.19.138
8 23 ms 18 ms 29 ms 66.109.9.122
9 93 ms 97 ms 105 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
10 89 ms 94 ms 98 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.2
5]
11 103 ms 98 ms 100 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 94 ms 99 ms 98 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

13 93 ms 98 ms 98 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]

14 94 ms 99 ms 98 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

15 94 ms 98 ms 98 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
16 92 ms 103 ms 88 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177]

17 110 ms 99 ms 138 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

18 93 ms 98 ms 99 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
19 124 ms 129 ms 128 ms 10.2.2.1
20 122 ms 131 ms * 192.34.76.2
21 113 ms 122 ms 115 ms 199.91.189.234
22 116 ms 113 ms 118 ms 199.91.189.35

Trace complete.

C:\Windows\System32>5:33 Pacific time
The system cannot find the drive specified.

C:\Windows\System32>tracert 199.91.189.35

Tracing route to 199.91.189.35 over a maximum of 30 hops

1 8 ms 9 ms 6 ms READYSHARE [192.168.1.1]
2 31 ms 23 ms 45 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 12 ms 17 ms 20 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 25 ms 25 ms 18 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.16
2]
5 25 ms 22 ms 22 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 14 ms 19 ms 29 ms 107.14.19.32
7 25 ms 28 ms 19 ms 107.14.19.138
8 26 ms 26 ms 21 ms 66.109.9.122
9 96 ms 100 ms 98 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
10 94 ms 97 ms 100 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.2
5]
11 94 ms 99 ms 99 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 96 ms 97 ms 100 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

13 93 ms 96 ms 86 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]

14 96 ms 89 ms 96 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

15 95 ms 98 ms 99 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
16 95 ms 98 ms 99 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177]

17 95 ms 99 ms 97 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

18 93 ms 98 ms 96 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
19 126 ms 129 ms 128 ms 10.2.2.1
20 121 ms 129 ms 129 ms 192.34.76.2
21 111 ms 109 ms 119 ms 199.91.189.234
22 126 ms 119 ms 119 ms 199.91.189.35

Trace complete.

C:\Windows\System32>
C:\Windows\System32>tracert 199.91.189.35

Tracing route to 199.91.189.35 over a maximum of 30 hops

1 8 ms 10 ms 7 ms READYSHARE [192.168.1.1]
2 41 ms 38 ms 39 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 15 ms 18 ms 18 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 22 ms 20 ms 29 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.16
2]
5 25 ms 28 ms 32 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 18 ms 24 ms 17 ms 107.14.19.32
7 20 ms 29 ms 29 ms 107.14.19.138
8 31 ms 28 ms 20 ms 66.109.9.122
9 97 ms 96 ms 99 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
10 102 ms 100 ms 96 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.2
5]
11 94 ms 98 ms 98 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 94 ms 98 ms 98 ms ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

13 93 ms 89 ms 99 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150]

14 94 ms 98 ms 98 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

15 93 ms 98 ms 96 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
16 94 ms 88 ms 98 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177]

17 98 ms 96 ms 100 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

18 95 ms 98 ms 98 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
19 124 ms 129 ms * 10.2.2.1
20 * 128 ms 128 ms 192.34.76.2
21 109 ms 113 ms 118 ms 199.91.189.234
22 160 ms 107 ms 172 ms 199.91.189.35

Trace complete.

C:\Windows\System32>JUST FOR FUN LETS COMPARE
'JUST' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\System32>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 10 ms 8 ms 11 ms READYSHARE [192.168.1.1]
2 * 385 ms 38 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 14 ms 18 ms 19 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 24 ms 18 ms 29 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.16
2]
5 24 ms 23 ms 24 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 22 ms 26 ms 26 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.102]
7 22 ms 42 ms 23 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 38 ms 38 ms 38 ms ix-9-0-1-0.tcore2.LVW-LosAngeles.as6453.net [64.
86.252.169]
9 121 ms 138 ms * if-22-2.tcore2.PDI-PaloAlto.as6453.net [66.198.1
44.73]
10 126 ms 118 ms 128 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.14
4.58]
11 133 ms 138 ms 139 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
12 114 ms 128 ms 118 ms 66.198.96.58
13 136 ms 137 ms 138 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
14 * 134 ms 128 ms 72.55.128.44
15 119 ms 128 ms 118 ms 184.107.107.176

Trace complete.

C:\Windows\System32>THAT ONE WAS WEIRD< LETS TRY AGAIN
The system cannot find the file specified.

C:\Windows\System32>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 5 ms 3 ms 12 ms READYSHARE [192.168.1.1]
2 46 ms 36 ms 30 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 19 ms 31 ms 20 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 26 ms 28 ms 28 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.16
2]
5 22 ms 28 ms 26 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 15 ms 28 ms 30 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.102]
7 18 ms 18 ms 23 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 36 ms 29 ms 39 ms ix-9-0-1-0.tcore2.LVW-LosAngeles.as6453.net [64.
86.252.169]
9 123 ms 119 ms 116 ms if-22-2.tcore2.PDI-PaloAlto.as6453.net [66.198.1
44.73]
10 123 ms 118 ms 127 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.14
4.58]
11 149 ms 143 ms 147 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
12 * 113 ms 114 ms 66.198.96.58
13 128 ms 131 ms 140 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
14 136 ms 132 ms 135 ms 72.55.128.44
15 126 ms 113 ms 128 ms 184.107.107.176

Trace complete.

C:\Windows\System32>http://nlworks.com/2013/06/final-fan...erver-location
s/

tl;dr i don't even know where i got that IP from. Nor does it matter because its still giving me the same end result. Garbage.

I don't need a lecture from someone with too much time on their hands. I'm putting in my free time emailing and calling twc, tata, and now level3 in my spare time. lolbuyvpn is the dumbest thing i heard from everyone. It's no shocker why this country is such a dump. Things break and people accept it.

**misterdapi** · 12-04-2013 12:05 PM

and no. I didn't read all 500+ of your posts. Only a pyscho would do that. Listen. We don't jive. II get what you are trying to do, that's cool. If we met in real life we wouldn't get along. We are both fighting the same cause here. Props for pointing out the issue with the IP, however it still points to a Square website in the same town and for me. Thats close enough. Sure, I've been sending traceroutes to a variety of locations including the multiple game servers that i use. I get that information from my computer. I see what the program is connected to. Where did i get that IP you are saying is Edios? idk, most likely when i was connecting to european server. idk honestly. I'm not wasting my time with this anymore. You and I don't get along, You come off like a dick arm chair expert. Just being honest. I myself don't have a lot of patience with people and have very limited hours due to my career and family and day to day stuff.

I'm sorry I was rude to you.

**Raist** · 12-04-2013 01:03 PM

Originally Posted by misterdapi

and no. I didn't read all 500+ of your posts. Only a pyscho would do that. Listen. We don't jive. II get what you are trying to do, that's cool. If we met in real life we wouldn't get along. We are both fighting the same cause here. Props for pointing out the issue with the IP, however it still points to a Square website in the same town and for me. Thats close enough. Sure, I've been sending traceroutes to a variety of locations including the multiple game servers that i use. I get that information from my computer. I see what the program is connected to. Where did i get that IP you are saying is Edios? idk, most likely when i was connecting to european server. idk honestly. I'm not wasting my time with this anymore. You and I don't get along, You come off like a dick arm chair expert. Just being honest. I myself don't have a lot of patience with people and have very limited hours due to my career and family and day to day stuff.

I'm sorry I was rude to you.

IDK if we wouldn't get along, I'm usually very patient with people that have different opinions. Unfortunately, this isn't a matter of opinion. Your approach is grossly inaccurate and could potentially waste a LOT of time and effort diagnosing the wrong path--ultimately it might not make enough of an impact and leave you back at square one (or perhaps square 5 where your route starts changing--but certainly not at square 22, which is the number of hops needed to get to your gameserver).

To address issues with communications to the server you are using... you need to be investigating the connection to that server. Plain and simple. Sorry you didn't see the value/significance of that. hopefully we can further clarify it.

Pointing to websites in the same town doesn't always cut it. It might if they were setup with the same communication needs and so the routes were the same--but this is clearly not the case. For starters, one is a cluster(s) for hosting websites, and the other is clusters hosting a real time online game. There are MAJOR differences in what level of service is needed for each of those to function acceptably for the users. Even if you throw out the difference in what each requires to effectively host their different content and the level of traffic coming/going to them (and their is a considerably different volume level involved here, which matters a lot with the diagnoses as well because our problems stem from an issue with managing congestion), there is no ignoring the difference in the routing path to get to them. While they are in the same city, they are NOT in the same city block. It is a 4-5 mile drive between them, and they are on a different circuit. The route changes significantly early on, and goes for considerably longer getting to the game server. One comes into Montreal via a TATA segment, and the other via a Level3 segment.

This throws several monkey wrenches into the mix--pretty much to the point that by focusing on the wrong one, you completely miss the boat on the other. IDK if this will line up decently or not, but lets try looking at them side-by side...hopefully the visual will help clarify it better:

Code:

Tracing route to 199.91.189.28 over a maximum of 30 hops			Tracing route to 184.107.107.176 over a maximum of 30 hops
								
1 6 ms 4 ms 2 ms READYSHARE [192.168.1.1] 					1 9 ms 8 ms 8 ms READYSHARE [192.168.1.1]
2 37 ms 37 ms 30 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]		2 43 ms 32 ms 34 ms cpe-75-85-32-1.socal.res.rr.com [75.85.32.1]
3 16 ms 18 ms 18 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]		3 28 ms 18 ms 18 ms tge7-2.covncafi01h.socal.rr.com [76.166.2.193]
4 24 ms 19 ms 28 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.162]		4 24 ms 23 ms 24 ms tge0-9-0-9.ontrcacp01r.socal.rr.com [72.129.6.162]
5 19 ms 24 ms 28 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0] 		5 29 ms 22 ms 25 ms agg21.lsancarc01r.socal.rr.com [72.129.5.0]
6 24 ms 28 ms 28 ms 107.14.17.132 						6 20 ms 28 ms 18 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.102]
7 22 ms 24 ms 23 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135] 		7 23 ms 28 ms 28 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 68 ms 29 ms 38 ms 66.109.9.122						8 34 ms * 34 ms ix-9-0-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.169]
9 98 ms 108 ms 98 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62] 		9 119 ms 118 ms * if-22-2.tcore2.PDI-PaloAlto.as6453.net [66.198.144.73]
10 92 ms 108 ms 98 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.17]	10 174 ms 140 ms 118 ms if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
11 95 ms 97 ms 88 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]		11 133 ms 135 ms 130 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
12 88 ms 92 ms 99 ms ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]		12 120 ms 128 ms * 66.198.96.58
13 95 ms 98 ms 97 ms ae-61-61.ebr1.Dallas1.Level3.net [4.69.151.126]		13 133 ms 158 ms 131 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
14 92 ms 98 ms 116 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]		14 134 ms 129 ms 149 ms 72.55.128.44
15 94 ms 119 ms 102 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]		15 121 ms 138 ms 118 ms 184.107.107.176
16 96 ms 98 ms 98 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]								
17 94 ms 98 ms 98 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]								
18 91 ms 128 ms 98 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]								
19 141 ms 131 ms 126 ms 10.2.2.1								
20 129 ms 171 ms 126 ms 192.34.76.2								
21 112 ms 118 ms 119 ms 199.91.189.234								
22 127 ms 138 ms 122 ms 199.91.189.28

Notice how the path changes before you even leave the LA hops. Past hop 7, they are completely different. This is a SIGNIFICANT change in the path, and if someone is looking for problems along the route, they need to see all of these hops that you are actually using--hops that won't be seen by using the wrong IP. After 15 hops, you aren't even into Montreal yet trying to get to the game server, but you've hit the IP hosting the web sites. Simply put... you are NOT following the same route getting to a webserver at 20 Place Du Commerce, Montreal, QC, H3E-1Z6, Canada ( http://myip.ms/info/whois/184.107.107.176 ) as you do getting to the game servers at 400 Boul. De Maisonneuve, Montreal, QC, H3A-1L4, CA ( http://myip.ms/info/whois/199.91.189.28 ). By focusing on having technicians flush out the route to that web server IP you will not be addressing problems that may be in the route going to the game server beyond where they have commonality, which in your case is only 6 hops out of the 22 hop route you took to get to the game server (hops 1-5 and 7--hop 6 is different). Note also that you are exhibiting issues at hops in the game server route that aren't even in the web server's route. Those points of failure would be completely uncaptured and not corrected.

So in summation, to properly address this particular issue you not only need to be bringing in the proper people to investigate the situation, but you also need to be providing the proper information about the problem---that needs to include details related to your actual connection used by your game and not some unrelated connection data. If these two important elements are not present in your process, you may be shooting in the dark--and possibly shooting yourself in the foot.

**LobsterBisque** · 12-04-2013 04:49 PM

Case in point, I have Comcast in Chicago right now. My connections are fine until they reach a certain hop in Montreal. This is where I'm experiencing 7-10% packet loss. This particular IP address belongs to TATA. It is not in my ISP, it is not technically the fault of SE either.

Now that being said SE needs to either open communications with their local ISPs to help streamline this issue or they are going to lose customers. I for one being a bard CANNOT lag on ADS or it's a wipe. This makes it not fun for me to play so I don't.

**Noahlimits** · 12-05-2013 02:03 AM

Just an update: I had them fully rewire my entire apartment complex and switch me to my own port outside. So far I'm 1000/1000 with no ping loss to my server (gilgamesh) and the NA server lobby in general. I'll check again after work, but this worked for me. I played 10 glorious minutes of lag free FFXIV... now I go to work.

**Furlamseere** · 12-05-2013 09:57 AM

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.

Thread: Packet Loss to NA servers only

Thread Tools

Search Thread

Display