Problems with connection (R0) lag

[Kurlaran]

Alright it seems that two us in the same city are getting routed different directions, but it is definitely timing out in La before routing in different directions. While the two of you getting routed through atlas are timing out later as well. Maybe it is a Cox issue after all. At least for some of us.

[cenie]

Alright it seems that two us in the same city are getting routed different directions, but it is definitely timing out in La before routing in different directions. While the two of you getting routed through atlas are timing out later as well. Maybe it is a Cox issue after all. At least for some of us.

It's beginning to look like a Cox Communication issue in the Southwest United States.

[Keolan]

ISP: Cox Communication
State: NV

I too am seeing the same trace route results as the others have posted

[MimoIxel]

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 11 ms 16 ms 10.128.16.1
3 18 ms 38 ms 22 ms 172.21.1.68
4 11 ms 17 ms 22 ms chndcorc01-te-0-15-0-0.ph.ph.cox.net [70.169.72.
56]
5 * 26 ms 16 ms 70.169.75.153
6 42 ms 43 ms 27 ms 68.1.5.139
7 23 ms 35 ms 46 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
8 102 ms 113 ms 124 ms xe-4-0-0.mtl10.ip4.tinet.net [141.136.108.190]
9 104 ms 116 ms 134 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 104 ms 107 ms 108 ms 192.34.76.2
11 127 ms 112 ms 116 ms 199.91.189.234
12 102 ms 133 ms 105 ms 199.91.189.74

Trace complete.

Cox Cable
Surprise, AZ

[Poki]

Here's mine from Mesa, AZ (Cox)

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Strum [192.168.1.1]
2 11 ms 7 ms 7 ms 10.49.80.1
3 11 ms 9 ms 9 ms 172.21.0.156
4 12 ms 11 ms 11 ms 70.169.73.43
5 20 ms 9 ms 9 ms 70.169.75.153
6 * 22 ms 21 ms 68.1.5.139
7 22 ms 21 ms 23 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
8 101 ms 102 ms 103 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 102 ms 107 ms 105 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 102 ms 104 ms 103 ms 192.34.76.2
11 103 ms 103 ms 105 ms 199.91.189.234
12 101 ms 100 ms 101 ms 199.91.189.74


For what little it may help

[SerRedBeard]

Hey all been having this issues for the past few days.
Only time I don't r0 is inside the inn room for whatever reasons.

ISP: Time Warner
Location: Northeast Ohio
Netgear Router (WPN824), Netgear Wireless NIC (WPN311)

Outside of upgrading hardware. I have done all the suggestions SE's FAQ has suggesting including:

-Re-logging
-Reset Router and Modem
-Restarted computer
-Updated router software.
-Added Port Forwarding via TCP
-Direct connection to Router
-Direct connection to Modem
-Connection reset from ISP's side.
-Removed and reseated NIC card.

Below is the Tracert

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 192.168.1.1
2 41 ms * 31 ms cpe-71-74-224-1.neo.res.rr.com [71.74.224.1]
3 * 15 ms 16 ms gig4-2.lornoh1-rtr1.neo.rr.com [24.164.104.73]
4 129 ms 19 ms 26 ms network-184-059-246-106.neo.rr.com [184.59.246.1
06]
5 * 20 ms 20 ms network-065-029-001-032.midwest.rr.com [65.29.1.
32]
6 26 ms 31 ms 24 ms 107.14.19.58
7 24 ms 30 ms 25 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
8 29 ms 27 ms 22 ms te0-7-0-10.ccr21.iad02.atlas.cogentco.com [154.5
4.10.193]
9 26 ms 32 ms * be2042.ccr21.dca01.atlas.cogentco.com [154.54.26
.125]
10 * 33 ms 32 ms te0-0-0-8.ccr21.jfk02.atlas.cogentco.com [154.54
.42.18]
11 * 62 ms 54 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.
50]
12 46 ms * 50 ms 38.122.42.34
13 44 ms 49 ms 50 ms 10.2.2.1
14 88 ms 51 ms 48 ms 192.34.76.2
15 44 ms 46 ms 44 ms 199.91.189.234
16 80 ms 67 ms 65 ms 199.91.189.74

Trace complete.

[Hatsworth]

This started very recently and it's making the game really annoying to play.

ISP: Cox
State: NV

1 0 0 0 206.123.64.46 -
2 0 0 0 64.124.196.225 xe-4-2-0.er2.dfw2.us.above.net
3 0 0 0 64.125.29.121 xe-3-0-0.er1.dfw2.us.above.net
4 0 0 0 209.58.47.21 ix-7-1-2-0.tcore1.dt8-dallas.as6453.net
5 102 98 100 66.110.56.6 if-2-2.tcore2.dt8-dallas.as6453.net
6 91 90 90 66.110.57.82 if-8-2.tcore1.lvw-losangeles.as6453.net
7 Timed out 91 91 66.198.127.25 if-3-2.tcore1.pdi-paloalto.as6453.net
8 97 92 92 66.198.127.6 if-1-2.tcore1.nyy-newyork.as6453.net
9 92 92 92 216.6.99.1 if-11-2.tcore2.nyy-newyork.as6453.net
10 92 103 92 216.6.99.30 if-5-2.tcore2.mtt-montreal.as6453.net
11 92 113 91 216.6.115.89 if-0-2.tcore1.mtt-montreal.as6453.net
12 96 96 96 64.86.31.42 -
13 97 97 97 67.205.127.238 te8-3.dr10.mtl.iweb.com
14 96 96 96 72.55.128.44 -
15 97 97 97 184.107.107.176 -
Trace complete

[Mustikos]

I am also having this issue and it stared a day or so ago but it got worse tonight. At around 11:15 pm cst the internet connection with my modem stop responding and it finally came back up over an hour later and since then the rubber banding has been horrible. I checked other games and did a few speed test and everything was fine on them at least.

I live in NW Arkansas.

Here is my trace:

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 7 ms 7 ms 7 ms 10.52.160.1
2 8 ms 7 ms 6 ms 70.183.68.109
3 15 ms 15 ms 15 ms kscydsrj02-ae0.rd.ks.cox.net [70.183.71.93]
4 17 ms 15 ms 15 ms 70.183.71.66
5 14 ms 15 ms 19 ms 70.183.71.64
6 26 ms 24 ms 26 ms 68.1.5.140
7 28 ms 26 ms 27 ms te0-7-0-32.ccr21.dfw03.atlas.cogentco.com [154.5
4.10.53]
8 29 ms 29 ms 27 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
9 39 ms 39 ms 39 ms be2141.mpd22.mci01.atlas.cogentco.com [154.54.5.
157]
10 51 ms 47 ms 52 ms te0-5-0-1.ccr21.ord01.atlas.cogentco.com [154.54
.84.74]
11 65 ms 64 ms 63 ms be2082.ccr22.yyz02.atlas.cogentco.com [154.54.28
.10]
12 72 ms 71 ms 70 ms be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25
.26]
13 70 ms 72 ms 73 ms 38.122.42.34
14 * * * Request timed out.
15 74 ms 70 ms 70 ms 192.34.76.2
16 73 ms 73 ms 75 ms 199.91.189.234
17 71 ms 72 ms 69 ms 199.91.189.74

Trace complete.

[Skoll8]

After this last maintenance I started experiencing this rubber banding issue. I'm also out of Buckeye, AZ (just west of Phoenix) using Cox Cable. Prior to the patch, it just seemed like I had a moderate delay. The whole thing where you have to be out of the red circle a second before it disappears or you'll get hit, and I can start running with over 0.5 seconds left on my cast time, etc. Now I have that plus the lag spike every 5-7 seconds or so. So is this an issue with Cox Cable? Or is there something that SE can actually do about this routing problem? Here is my tracert.

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms router.knight [192.168.8.1]
2 11 ms 9 ms 9 ms 10.147.192.1
3 11 ms 11 ms 11 ms 172.21.7.186
4 16 ms 10 ms 19 ms 70.169.75.153
5 26 ms * 22 ms 68.1.5.139
6 * 22 ms 30 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
7 102 ms 100 ms 104 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
8 103 ms 103 ms 106 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
9 103 ms 106 ms 102 ms 192.34.76.2
10 102 ms 102 ms 102 ms 199.91.189.234
11 103 ms 106 ms 105 ms 199.91.189.74

[Tyberius]

ISP: Cox
State: Ca

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Cisco30786 [192.168.1.1]
2 * * * Request timed out.
3 8 ms 7 ms 7 ms cv1xcmtk05-gex030000.sd.sd.cox.net [68.6.11.222]
4 * * * Request timed out.
5 11 ms 9 ms 7 ms fed1dsrj02-xe130.0.rd.sd.cox.net [68.6.8.4]
6 27 ms 29 ms 28 ms sanjbprj02-ae0.0.rd.sj.cox.net [68.1.5.186]
7 28 ms 29 ms 29 ms te0-7-0-30.ccr21.sjc03.atlas.cogentco.com [154.54.10.125]
8 30 ms 35 ms 30 ms be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.105]
9 33 ms 31 ms 30 ms te0-1-0-5.ccr22.sfo01.atlas.cogentco.com [66.28.4.5]
10 62 ms 73 ms 69 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
11 82 ms 81 ms 80 ms te0-2-0-3.ccr22.ord01.atlas.cogentco.com [154.54.6.202]
12 95 ms 95 ms 87 ms be2080.ccr22.yyz02.atlas.cogentco.com [154.54.42.6]
13 96 ms 95 ms 95 ms be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25.26]
14 94 ms 94 ms 95 ms 38.122.42.34
15 * * * Request timed out.
16 98 ms 98 ms 96 ms 192.34.76.2
17 97 ms 97 ms 97 ms 199.91.189.234
18 93 ms 94 ms 97 ms 199.91.189.74

Trace complete.