Frequent 90k drops

Printable View

12-11-2014, 04:14 AM
Zephanoa

Frequent 90k drops

I know this is a common issue so I will try to give as much details as possible. I am pretty sure the issue is by packets that are being dropped between the data center and my internet connection. Generally all the characters freeze except for mine and then it suddenly goes in to super quick motion to catch up and then I 90k. I can then retry to get in from the character selection screen 5-7 times and it lets me back in.

My internet is stable and know it is not an issue with my modem and routers as all other connections remain stable. I am led to believe my cable internet connection as soon as it transfers to att in Kansas city internet to get to the data center is the issue. I have seen a high amount of ms between jumps. This can happen multiple times in a night and seems to have been worse since patch 2.4 dropped.
12-11-2014, 10:43 AM
Zephanoa

Here is a tracert; here it looks like the problem is even further upstream; infact the issue looks like its Canada inet.

2 12 ms 12 ms 7 ms 173-26-34-1.client.mchsi.com [173.26.34.1]
3 9 ms 58 ms 9 ms 172.30.81.25
4 13 ms 10 ms 7 ms 172.30.3.209
5 13 ms 14 ms 18 ms 12.94.137.41
6 26 ms 26 ms 23 ms cr1.kc9mo.ip.att.net [12.122.150.10]
7 27 ms 27 ms 21 ms cr2.dlstx.ip.att.net [12.122.2.169]
8 29 ms 27 ms 31 ms ggr3.dlstx.ip.att.net [12.122.138.17]
9 21 ms 23 ms 25 ms 192.205.36.222
10 23 ms 38 ms 29 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
11 38 ms 41 ms 36 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.
113]
12 49 ms 50 ms 51 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
86]
13 63 ms 60 ms 59 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
14 67 ms 69 ms 68 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
.206]
15 71 ms 78 ms 74 ms 38.140.46.2
16 159 ms 212 ms 242 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
17 76 ms 76 ms 77 ms 72.55.128.44
18 75 ms 76 ms 76 ms 184.107.107.176
12-11-2014, 03:03 PM
Raist

Quote:

Originally Posted by Zephanoa

Here is a tracert; here it looks like the problem is even further upstream; infact the issue looks like its Canada inet.

2 12 ms 12 ms 7 ms 173-26-34-1.client.mchsi.com [173.26.34.1]
3 9 ms 58 ms 9 ms 172.30.81.25
4 13 ms 10 ms 7 ms 172.30.3.209
5 13 ms 14 ms 18 ms 12.94.137.41
6 26 ms 26 ms 23 ms cr1.kc9mo.ip.att.net [12.122.150.10]
7 27 ms 27 ms 21 ms cr2.dlstx.ip.att.net [12.122.2.169]
8 29 ms 27 ms 31 ms ggr3.dlstx.ip.att.net [12.122.138.17]
9 21 ms 23 ms 25 ms 192.205.36.222
10 23 ms 38 ms 29 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
11 38 ms 41 ms 36 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.
113]
12 49 ms 50 ms 51 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
86]
13 63 ms 60 ms 59 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
14 67 ms 69 ms 68 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
.206]
15 71 ms 78 ms 74 ms 38.140.46.2
16 159 ms 212 ms 242 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
17 76 ms 76 ms 77 ms 72.55.128.44
18 75 ms 76 ms 76 ms 184.107.107.176

For the upteenth time.... that's a webserver--it hosts websites for projects from the EIDOS library. No connection to gameplay, and hosted on a completely different ISP's segments physically across town. All the game's servers in Canada start with 199 and are hosted on Ormuco segments.

If you aren't going to look up the actual IP your client uses, at least use one of the lobby servers. Here they are again:

neolobby02.ffxiv.com
neolobby04.ffxiv.com
neolobby06.ffxiv.com

And you are showing signs of congestion starting earlier in your route that is likely stacking and making things much worse than they otherwise would be. One spot right near the start of your route, and another near the handoff to the routing partner Cogent. In that short sample, you are showing potentially almost 50ms of jitter where you should have around 5 or less...that can lead to some heavy skewing of the packet queues.
12-12-2014, 02:46 AM
Zephanoa

Quote:

Originally Posted by Raist

For the upteenth time.... that's a webserver--it hosts websites for projects from the EIDOS library. No connection to gameplay, and hosted on a completely different ISP's segments physically across town. All the game's servers in Canada start with 199 and are hosted on Ormuco segments.

If you aren't going to look up the actual IP your client uses, at least use one of the lobby servers. Here they are again:

neolobby02.ffxiv.com
neolobby04.ffxiv.com
neolobby06.ffxiv.com

And you are showing signs of congestion starting earlier in your route that is likely stacking and making things much worse than they otherwise would be. One spot right near the start of your route, and another near the handoff to the routing partner Cogent. In that short sample, you are showing potentially almost 50ms of jitter where you should have around 5 or less...that can lead to some heavy skewing of the packet queues.

Okay I will look in to the IP the client uses and post that trace. Sorry if a lot of leg work has been done on this before, I appreciate the information.
12-12-2014, 09:52 AM
Zephanoa

I just shipped this to my ISP but I wanted to share here too;

TRACERT:

C:\Users\Zero X Divide>tracert 199.91.189.39

Tracing route to 199.91.189.39 over a maximum of 30 hops

1 10 ms 8 ms 8 ms 173-26-162-1.client.mchsi.com [173.26.162.1]
2 8 ms 12 ms 9 ms 172.30.81.25
3 7 ms 7 ms 8 ms 172.30.3.209
4 14 ms 14 ms 14 ms 12.94.137.41
5 28 ms 29 ms 26 ms cr2.kc9mo.ip.att.net [12.122.150.138]
6 22 ms 26 ms 26 ms cr1.dlstx.ip.att.net [12.122.28.85]
7 30 ms 25 ms 26 ms gar26.dlstx.ip.att.net [12.123.16.85]
8 * * * Request timed out.
9 * * 73 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

10 71 ms * * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

11 64 ms 64 ms 73 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
12 68 ms 69 ms 72 ms 192.34.76.10
13 65 ms 73 ms 70 ms 199.91.189.242
14 70 ms 73 ms 71 ms 199.91.189.39

Trace complete.

PING:

Reply from 199.91.189.39: bytes=32 time=68ms TTL=236
Reply from 199.91.189.39: bytes=32 time=67ms TTL=236
Reply from 199.91.189.39: bytes=32 time=68ms TTL=236
Reply from 199.91.189.39: bytes=32 time=67ms TTL=236
Reply from 199.91.189.39: bytes=32 time=68ms TTL=236
Request timed out.
Reply from 199.91.189.39: bytes=32 time=70ms TTL=236
Reply from 199.91.189.39: bytes=32 time=68ms TTL=236
Reply from 199.91.189.39: bytes=32 time=71ms TTL=236
Reply from 199.91.189.39: bytes=32 time=65ms TTL=236
Reply from 199.91.189.39: bytes=32 time=67ms TTL=236
Reply from 199.91.189.39: bytes=32 time=71ms TTL=236
Reply from 199.91.189.39: bytes=32 time=70ms TTL=236
Request timed out.
Reply from 199.91.189.39: bytes=32 time=68ms TTL=236
Reply from 199.91.189.39: bytes=32 time=73ms TTL=236
Request timed out.
Request timed out.
Reply from 199.91.189.39: bytes=32 time=69ms TTL=236
Reply from 199.91.189.39: bytes=32 time=71ms TTL=236
Reply from 199.91.189.39: bytes=32 time=71ms TTL=236
Reply from 199.91.189.39: bytes=32 time=70ms TTL=236
Reply from 199.91.189.39: bytes=32 time=69ms TTL=236
Reply from 199.91.189.39: bytes=32 time=70ms TTL=236
Request timed out.
Reply from 199.91.189.39: bytes=32 time=70ms TTL=236
Reply from 199.91.189.39: bytes=32 time=69ms TTL=236
Request timed out.
Reply from 199.91.189.39: bytes=32 time=68ms TTL=236
Reply from 199.91.189.39: bytes=32 time=73ms TTL=236
Request timed out.
Reply from 199.91.189.39: bytes=32 time=71ms TTL=236
Reply from 199.91.189.39: bytes=32 time=72ms TTL=236
Request timed out.
Reply from 199.91.189.39: bytes=32 time=71ms TTL=236

Ping statistics for 199.91.189.39:
Packets: Sent = 2026, Received = 1973, Lost = 53 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 1197ms, Average = 70ms
12-12-2014, 12:08 PM
Raist

Nice capture there Zephanoa... snagged problems between the exchange points for Level3. We see that happen a lot. Hopefully others have been chiming in through their ISP and someone steps up to the plate to break up the congestion for you. When I catch it with LEvel3, Time Warner just pulls me away from them and sticks me on TATA or Cogent... if nothing else, maybe they can do the same for you if they don't get anywhere with the Level3 issues. Crossing the fingers for you! :)