SICK OF THE LAG FEST

[Raist]

C:\Users\Hellshiver>pathping 199.91.189.57

IP assignments have changed with the infrastructure changes they just made. Noted in another thread that my client is now using an IP I haven't seen it use since back around patch 2.2. Since Beta4, I have tracked 4 differnt IP's in use for my Midgard connection. This is the first time I've seen it go back to a previously used IP address (199.91.189.31). Both the .57 and .60 IP's that are noted at the ARR status page appear to no longer be a valid IP's for world servers--or at least those particular IP's appear to be down or otherwise inaccessible to a lot of players if they are still assigned as valid IP addresses.

There are about 15 IP's in the range of what we've previously seen in use that are no longer responding from a lot of locations (some I couldn't get to respond no matter where I hit them from, but they USED to respond), amongst several other blocks of IP addresses within that 199.91.189.xxx subnet. I forwarded a list of the IP's I found issues with to SE, and I got a reply back today that they have forwarded my report on to the proper department for review. If it is just a matter of downed IP's for some reason, hopefully it will be resolved soon.

Just to be sure your assigned IP's haven't changed as well, you guys may want to load resmon or run netstat to see just what IP you are actually connecting to, and then run some traces there just to be sure you are getting an accurate picture.

[DragonBorn]

Yeah I have been lagging constantly and dcing, I don't have a problem with dcing when I am stood around but it seems to happen when I am doing coil or other dutys mainly and at the worse possible times, it does not help that you lose the lb if someone dcs. At this rate I might have to stop paying my sub till heavensward which I don't want to but will do if the game continues being nigh-unplayable.
I had never lagged before and certainly have never lagged this bad in anything before.

[MoldyOne]

i just ran netstat and it shows me as being connected to Famfrit, not Malboro which might explain my lag a bit if its going through another server

[Raist]

i just ran netstat and it shows me as being connected to Famfrit, not Malboro which might explain my lag a bit if its going through another server

no...they've assigned you a different IP to use. Since the first major revamp shortly after the initial 2.0 launch, the world services have always been hosted on multiple IP addresses (at least 3 per world have been documented)--the ARR site has always only shown one of the IP's that may be used. So some of the traces/pings being done by some players may be failing because the IP they are testing against is no longer valid.

It appears some of the IP's we have been using in the past have either been dropped from the pool or they have otherwise been knocked out of commission. Either way, something has changed in their topology--which could be in line with the notice of the last maintenance where they noted there would be infrastructure changes.

There was also a recent notice about issues they found on Ormuco's end that supposedly have been addressed. But it seems the old 199.91.189.57 and 199.91.189.60 IP's posted on the ARR site for a handful of servers appear to still be unresponsive. That may simply be due to the infrastructure changes though, and not because there is something "wrong', but more that the configurations have changed. They need to find the new IP's and update the site I guess.

[LlamaLove]

IP assignments have changed with the infrastructure changes they just made. ...
...
Just to be sure your assigned IP's haven't changed as well, you guys may want to load resmon or run netstat to see just what IP you are actually connecting to, and then run some traces there just to be sure you are getting an accurate picture.

Good call. Was still drinking my coffee when I ran that yesterday.

Connecting to Hyperion, seems IP is 199.91.189.45

Current pathping:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Hellshiver>pathping 199.91.189.45

Tracing route to 199.91.189.45 over a maximum of 30 hops

  0  My PC
  1  My Router
  2  tge7-1.ftunaz0901h.socal.rr.com [76.166.20.121]
  3  tge1-2.yumaaz1401r.socal.rr.com [72.129.49.64]
  4  tge2-14-0-12.lsancarc01r.socal.rr.com [72.129.49.26]
  5  bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.212]
  6  0.ae1.pr1.lax00.tbone.rr.com [107.14.17.250]
  7  ix-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.81]
  8  if-3-2.tcore1.PDI-Palo-Alto.as6453.net [66.198.127.25]
  9  if-2-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.127.2]
 10  if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
 11  if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
 12  66.198.96.50
 13  192.34.76.2
 14  199.91.189.234
 15  199.91.189.45

Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           My PC
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  My Router
                                0/ 100 =  0%   |
  2   12ms     0/ 100 =  0%     0/ 100 =  0%  tge7-1.ftunaz0901h.socal.rr.com [76.166.20.121]
                                0/ 100 =  0%   |
  3   15ms     0/ 100 =  0%     0/ 100 =  0%  tge1-2.yumaaz1401r.socal.rr.com [72.129.49.64]
                                0/ 100 =  0%   |
  4   24ms     0/ 100 =  0%     0/ 100 =  0%  tge2-14-0-12.lsancarc01r.socal.rr.com [72.129.49.26]
                                0/ 100 =  0%   |
  5   24ms     0/ 100 =  0%     0/ 100 =  0%  bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.212]
                                0/ 100 =  0%   |
  6   22ms     0/ 100 =  0%     0/ 100 =  0%  0.ae1.pr1.lax00.tbone.rr.com [107.14.17.250]
                                0/ 100 =  0%   |
  7   19ms     0/ 100 =  0%     0/ 100 =  0%  ix-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.81]
                                0/ 100 =  0%   |
  8   32ms     0/ 100 =  0%     0/ 100 =  0%  if-3-2.tcore1.PDI-Palo-Alto.as6453.net [66.198.127.25]
                                0/ 100 =  0%   |
  9   31ms     0/ 100 =  0%     0/ 100 =  0%  if-2-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.127.2]
                                0/ 100 =  0%   |
 10   84ms     0/ 100 =  0%     0/ 100 =  0%  if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
                                0/ 100 =  0%   |
 11   98ms     0/ 100 =  0%     0/ 100 =  0%  if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
                                0/ 100 =  0%   |
 12  103ms     0/ 100 =  0%     0/ 100 =  0%  66.198.96.50
                                0/ 100 =  0%   |
 13  101ms     0/ 100 =  0%     0/ 100 =  0%  192.34.76.2
                                0/ 100 =  0%   |
 14   94ms     0/ 100 =  0%     0/ 100 =  0%  199.91.189.234
                                0/ 100 =  0%   |
 15   93ms     0/ 100 =  0%     0/ 100 =  0%  199.91.189.45

Trace complete.

Hop 12 is still Tata Communications.
Hop 13-15 is Ormuco.

[Echelon]

I've been getting the Stuttering lag as well. I have good ping, before I log in my connection to the realm said its Excellent, and yet.Stuttering and 15 sec lag spikes from Last night when I tried to tank Final Coil. Whatever happened during the server maintenance or data center maintenance needs to be changed back.

[Echelon]

I've been getting the Stuttering lag as well. I have good ping, before I log in my connection to the realm said its Excellent, and yet.Stuttering and 15 sec lag spikes from Last night when I tried to tank Final Coil. Whatever happened during the server maintenance or data center maintenance needs to be changed back.

I ran trace to my server..

Tracing route to 199.91.189.28 over a maximum of 30 hops

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 33 ms 25 ms 25 ms 99-16-144-2.lightspeed.austtx.sbcglobal.net [99.
16.144.2]
3 26 ms 25 ms 25 ms 70.143.193.38
4 27 ms 26 ms 27 ms 12.83.80.141
5 26 ms 27 ms 27 ms gar26.dlstx.ip.att.net [12.123.16.85]
6 * * * Request timed out.
7 69 ms 68 ms 68 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

8 69 ms 68 ms 69 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

9 69 ms 69 ms 69 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
10 67 ms 66 ms 105 ms 192.34.76.10
11 67 ms 67 ms 67 ms 199.91.189.242
12 67 ms 68 ms 68 ms 199.91.189.28

Trace complete.

Everytime I do a trace the 6th ping is a timed out..should I be concerned?

[Tayolynn]

I've been getting the same lag, specifically on the second of 11pm PST or 9PM Hawaii time. It lasts from an hour or more. It's the only time I can play and if this keeps up, my play time comes down from 3 hrs to 2-1 hr. Might as well just give up and unsub till expansion.

[Echelon]

Here my trace on prime time..

WITH the ports foward.

Tracing route to 199.91.189.28 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  homeportal [192.168.1.254]
  2     *        *        *     Request timed out.
  3    25 ms    28 ms    25 ms  70.143.193.38
  4    25 ms    27 ms    27 ms  12.83.80.141
  5    28 ms    27 ms    27 ms  gar26.dlstx.ip.att.net [12.123.16.85]
  6     *        *        *     Request timed out.
  7    68 ms    68 ms    68 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

  8    69 ms    68 ms    68 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

  9    69 ms    68 ms    69 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 10    69 ms    69 ms    68 ms  192.34.76.10
 11    68 ms    68 ms    67 ms  199.91.189.242
 12    69 ms    68 ms    69 ms  199.91.189.28

Trace complete.

And without ports foward.

Tracing route to 199.91.189.28 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  homeportal [192.168.1.254]
  2     *        *        *     Request timed out.
  3    25 ms    25 ms    25 ms  70.143.193.38
  4    27 ms    27 ms    27 ms  12.83.80.141
  5    25 ms    26 ms    27 ms  gar26.dlstx.ip.att.net [12.123.16.85]
  6     *        *        *     Request timed out.
  7    69 ms    68 ms    68 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

  8    73 ms    70 ms    69 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

  9    69 ms    69 ms    68 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
 10    67 ms    66 ms    67 ms  192.34.76.10
 11    67 ms    68 ms    67 ms  199.91.189.242
 12    67 ms    68 ms    68 ms  199.91.189.28

Trace complete.

not sure what going on but from what I gather...it should not be my end. I am rubber banding not stuttering....that is more accurate to what I am dealing with...its is quite annoying and hoping someone could give an explanation..if it's Squares end or my providers end, but I digress because I was totally fine on Monday until Tuesday came around and since then I've been rubber banding.

[Saix_Serge]

This is just a thought- but depending on how much Square changed, your ISP could be considering FFXIV as Peer to Peer again. This happened I think about half a year ago where certain ISPs would blatantly throttle FFXIV traffic in peak hours due to them thinking it was P2P. Square got around to the problem eventually and got it fixed, but now with recent changes, things could have reverted back. I've had some lag the past few days but there were several tornado warnings- whether or not the lag was due to that or not I do not know. If it's a P2P problem though (again) the only way around the packet loss is through a VPN.