Problems with connection (R0) lag

Come on Sqeenix, step up your customer service. Im tired of seeing everyone teleporting via lag.

I'm thinking everyone having this issue should visit this thread once a day and state their location, ISP, etc. and spread the word for anyone else with the same issue to do so. Something to get the attention of SE. The crappy part is that I'll bet a large number of people assume the issue is just from the packed servers right now and aren't contacting SE yet.

Better yet, everyone open a ticket: https://support.na.square-enix.com/c...p?id=5382&la=1

It lets you state which ISP you have and what not. Also I would include a link to this thread in the ticket so they might see its a real widespread issue.

Having the same issue here, Verizon Fios in Northern VA. It started for me on Monday while I was still connected to the servers in the middle of the day after hours of smooth gameplay. Just put a support ticket in with this and the BT/EE thread linked in it, since it seems like they're the same issue.

A lot of people using Verizon it seems.

Well, I'm from Malaysia and I'm not using that. Either way; problem still persists.

Let it also be RE-stated that this was NOT a problem in Phase 3 and Phase 4 for me.

That and JP servers are still running smooth even though NA/EU lags like a slug on shit. (sorry)

Additional: And tonight in particular I keep getting error 9000

I'm also in the Northern VA - Alexandria area and I am having the same experience as the rest of you. Same Verizon Fios provider with the same upload/dl speeds and this is really pissing me off. Luckily I play with great people so lv 48 on my PGL but its made the game a pain in the ass to play. Please Square Enix fix this so I can make progress!!

BUMP!

I'm not home to try this but does changing DNs settings to something other than Verizon's defaults help at all?

Quote:

Originally Posted by Ferrin

Funnily enough I barely lag at all from 5am - 10am (GMT+8)

And then it starts.

*sigh*

The only started happening about 2 days ago has well, but yeah the mornings are starting to get affected as well.

I thought it was just my old computer not being able to handle the game well (it's nearly 8 years old). I, too, have the stuttering, loading and lag spikes, but other games run just fine. It adds an extra level of difficulty to the game; I have to calculatehow long it will take for my actions on the keyboard to actually happen onscreen.

For the record, I'm on Comcast in Northern New England (USA).

As an aside, I'm not quite sure what sending and receiving numbers I should be expecting. I assume higher numbers are better? Is there some minimum I should be looking for? And (forgive me if this next part is a stupid or unrelated question) will fixing this problem help me have higher FPS (currently, my FPS is 5-7 in town and maybe 12-15 out in the wild)?

Quote:

Originally Posted by Badwrong

If you don't mind me asking, where are you connecting to and from with the VPN?

I'm in Northern VA with FIOS, connecting to a "US East" VPN host. I have had no problems since tunneling outside of the Verizon network via the VPN client. I have 6 less hops than before.

Here is my tracert from Verizon:
Tracert results (excluding first 2 hops):

3 12 ms 10 ms 9 ms G1-6-2-4.WASHDC-LCR-22.verizon-gni.net [130.81.3
7.48]
4 8 ms 14 ms 24 ms ae6-0.RES-BB-RTR1.verizon-gni.net [130.81.199.14
6]
5 8 ms 9 ms 10 ms 0.ae2.BR3.IAD8.ALTER.NET [152.63.7.221]
6 9 ms 10 ms 9 ms ix-20-0.tcore1.AEQ-Ashburn.as6453.net [66.198.15
4.53]
7 * 40 ms 25 ms if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1
]
8 21 ms 22 ms 21 ms if-11-2.tcore2.NJY-Newark.as6453.net [216.6.87.1
38]
9 27 ms 27 ms 26 ms if-4-4.tcore2.NYY-NewYork.as6453.net [66.198.111
.18]
10 21 ms 22 ms 22 ms if-2-2.tcore2.MTT-Montreal.as6453.net [64.86.226
.13]
11 29 ms 29 ms 26 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
12 23 ms 26 ms 24 ms 64.86.31.42
13 26 ms 24 ms 25 ms te8-3.dr10.mtl.iweb.com [67.205.127.238]
14 27 ms 28 ms 27 ms 72.55.128.44
15 24 ms 22 ms 23 ms 184.107.107.176

And here is my tracert while tunneling through the VPN:

2 18 ms 20 ms 26 ms vl224-c3-11-c6-1.pnj1.choopa.net [68.232.186.241
]
3 23 ms 24 ms 23 ms ethernet11-2-br2.pnj1.choopa.net [108.61.80.13]

4 17 ms 24 ms 21 ms vl20-br1.pnj1.choopa.net [108.61.65.41]
5 20 ms 20 ms 21 ms execulink.com [198.32.160.23]
6 25 ms 27 ms 29 ms te8-2.cr2.mtl.iweb.com [67.205.127.117]
7 28 ms 27 ms 26 ms te8-4.dr10.mtl.iweb.com [67.205.127.82]
8 29 ms 26 ms 28 ms 72.55.128.44
9 29 ms 29 ms 29 ms 184.107.107.176

As you can see, the route shares very few of the same hops, so it's tough to say precisely where the problem might be.

Quote:

Originally Posted by Badwrong

I'm thinking everyone having this issue should visit this thread once a day and state their location, ISP, etc. and spread the word for anyone else with the same issue to do so. Something to get the attention of SE. The crappy part is that I'll bet a large number of people assume the issue is just from the packed servers right now and aren't contacting SE yet.

Better yet, everyone open a ticket: https://support.na.square-enix.com/c...p?id=5382&la=1

It lets you state which ISP you have and what not. Also I would include a link to this thread in the ticket so they might see its a real widespread issue.

Just did this. Forgot the link though. S**T.

Could you link a site where you got your VPN from? I'd like to give it a try when I get home.

Northern Virginia and Verizon customer, same issues. Lag spikes of up to 20 sec although certain times of the day were better than others. Dungeons and fates are just not possible to complete and even dailies are a pain. Saturday and sunday was smooth as silk and then it started Monday. I have a toon on Japanese server with no issues.

Quote:

Originally Posted by Badwrong

I'm thinking everyone having this issue should visit this thread once a day and state their location, ISP, etc. and spread the word for anyone else with the same issue to do so. Something to get the attention of SE. The crappy part is that I'll bet a large number of people assume the issue is just from the packed servers right now and aren't contacting SE yet.

Better yet, everyone open a ticket: https://support.na.square-enix.com/c...p?id=5382&la=1

It lets you state which ISP you have and what not. Also I would include a link to this thread in the ticket so they might see its a real widespread issue.

I have done this and reference this post. I highly agree that everyone should do the same. Good luck everyone.

Quote:

Originally Posted by Tibban

Could you link a site where you got your VPN from? I'd like to give it a try when I get home.

https://www.privateinternetaccess.com/

Quote:

Originally Posted by Tibban

I'm not home to try this but does changing DNs settings to something other than Verizon's defaults help at all?

This was one of the first things I tried, I switched to Google's DNS servers along with putting my computer on the router's DMZ and neither did anything.

The VPN works though I still find it dumb that I have to use it in order to play the game.

So ... I'm not affected by this, but a friend is, so I have a interest in seeing this resolved. Unfortunately that means that I can't really do any debugging from my end of things.

From reading this thread, I've gathered that there are 2 main groups that are experiencing this issue ( or at least are vocal about it): FIOS and Malaysia.

To give a relevant networking crash course: The way the net works is that it isn't just a straight connection between you and the Final Fantasy server - because there is no direct cable connecting you and them. Instead, your packets travel through multiple routing server hubs. Some call em nodes, some call em hops, just keep in mind that there are more things involved than just "you" and "final fantasy server".

Now, due to the fact that only a specific set of people are experiencing this issue, I will assume that the problem isn't directly on the Final Fantasy server, but rather on a routing server inbetween - that would explain why this problem seems largely isolated to people who have their location in common.* ( It is only possible for this to be a Final Fantasy server problem if their firewall or router is improperly configured for a specific IP set, however I doubt that as they don't seem to employ IP blocking. It would be pointless overhead. )

So, getting back to the matter at hand: debugging the problem.

The goal is to determine the point of failure.

While this won't immediately solve the issue, it will let you contact your ISP with concrete information to ask for a fix ( something like "My connection to canada has to go through server <hostname><ip> and it seems to go unresponsive every 2 minutes." )

They might still be difficult about it and not take you serious, but by having some actual data they might be more cooperative.

The traceroute is a excellent idea, but you essentially need to keep repeating it until the traceroute itself hits the point of failure - which would be a timeout.
It would also need to be repeated multiple times to get hard data on this ( is it always the same route server that fails, or maybe a set of them ? ).

More info on tracert can be found here: http://support.microsoft.com/kb/162326

To assist in gathering the data, I've written a small batch script.
Create a new text file somewhere on your computer, for example at C:\ for easy access.
Name it something like nettest.bat, when prompted that it may make the file unusable, click yes.
Right click the file and select edit, a text-editor will open.
Paste the following:

Code:

@echo off set /a "wait = 5" set "server=neolobby02.ffxiv.com" :while1 echo Checking server. Output goes to log.txt echo %date% %time% >> log.txt tracert -d %server% >> log.txt echo Press CTRL + C To Stop! echo Waiting %wait% seconds ... timeout /t %wait% /nobreak goto :while1 endlocal

Now just double-click the file and it will start querying the final fantasy lobby server. All US/EU servers in that center, so you don't need to query the actual game server itself.

What this does is:
It will automatically, every 5 seconds do a tracert command to the lobby server, saving the output in a log.txt file.

So, let this run for a while. Maybe 20 or 30 minutes. Close it with CTRL + C and then search the log.txt file for occurences of "*" instead of a time - the star denotes a timeout.

Please report back with information such as:
- How long you've let the test run
- Which IP/Server had the most * / timeout
- General frequency of * occuring.

Make sure you also state where you are from, so the data can be attributed to the proper group.

I'm hoping that we can see a common trend among multiple people from a group, so that we can narrow it down to a single, or a handful of servers causing issues.

Having the exact same issue, and I am in the Maryland/D.C. area with Verizon FIOS. It would appear the issue is on verizon's side, but I would still hope that SE would work with us to resolve the issue.

SE confirmed the issue with BT/EE in that thread hopefully theyll ours soon

I hope they manage to fix it.. I'd NOT want to use a VPN to play.

Also, if it helps the Malaysia ISP is called TMNet

I live in western PA with Atlantic Broadband as my ISP. I am experiencing the same issues of S0/R0 after being in game for a minute or so. I can stand in town and not touch a single key/button and watch the game freeze itself. A couple nights ago, somewhere around midnight EST, I was able to be online for much longer until I tried talking to an NPC vendor and then the issues started happening again.
I am about 90% sure it is NOT my ISP though. My friend in the next room is on the same router/internet connection I am and I can play on his computer flawlessly. I am convinced this is something SE must fix on their end.

I have been having this S0/R0 problem since yesturday. Happens after 5-10min of playing flawlessly. Have confirmed it not to be my PC and my connection to other games and websites is flawless. Have also played on the JP server without incident. My location is middle TN and my ISP is Wildblue... which is satellite, so I'm used to lag... but not to the point where it is utterly unplayable.

Bumping this thread.

Quote:

Originally Posted by Midsboss

So ... I'm not affected by this, but a friend is, so I have a interest in seeing this resolved. Unfortunately that means that I can't really do any debugging from my end of things.

From reading this thread, I've gathered that there are 2 main groups that are experiencing this issue ( or at least are vocal about it): FIOS and Malaysia.

To give a relevant networking crash course: The way the net works is that it isn't just a straight connection between you and the Final Fantasy server - because there is no direct cable connecting you and them. Instead, your packets travel through multiple routing server hubs. Some call em nodes, some call em hops, just keep in mind that there are more things involved than just "you" and "final fantasy server".

Now, due to the fact that only a specific set of people are experiencing this issue, I will assume that the problem isn't directly on the Final Fantasy server, but rather on a routing server inbetween - that would explain why this problem seems largely isolated to people who have their location in common.* ( It is only possible for this to be a Final Fantasy server problem if their firewall or router is improperly configured for a specific IP set, however I doubt that as they don't seem to employ IP blocking. It would be pointless overhead. )

So, getting back to the matter at hand: debugging the problem.

The goal is to determine the point of failure.

While this won't immediately solve the issue, it will let you contact your ISP with concrete information to ask for a fix ( something like "My connection to canada has to go through server <hostname><ip> and it seems to go unresponsive every 2 minutes." )

They might still be difficult about it and not take you serious, but by having some actual data they might be more cooperative.

The traceroute is a excellent idea, but you essentially need to keep repeating it until the traceroute itself hits the point of failure - which would be a timeout.
It would also need to be repeated multiple times to get hard data on this ( is it always the same route server that fails, or maybe a set of them ? ).

More info on tracert can be found here: http://support.microsoft.com/kb/162326

To assist in gathering the data, I've written a small batch script.
Create a new text file somewhere on your computer, for example at C:\ for easy access.
Name it something like nettest.bat, when prompted that it may make the file unusable, click yes.
Right click the file and select edit, a text-editor will open.
Paste the following:

Code:

@echo off set /a "wait = 5" set "server=neolobby02.ffxiv.com" :while1 echo Checking server. Output goes to log.txt echo %date% %time% >> log.txt tracert -d %server% >> log.txt echo Press CTRL + C To Stop! echo Waiting %wait% seconds ... timeout /t %wait% /nobreak goto :while1 endlocal

Now just double-click the file and it will start querying the final fantasy lobby server. All US/EU servers in that center, so you don't need to query the actual game server itself.

What this does is:
It will automatically, every 5 seconds do a tracert command to the lobby server, saving the output in a log.txt file.

So, let this run for a while. Maybe 20 or 30 minutes. Close it with CTRL + C and then search the log.txt file for occurences of "*" instead of a time - the star denotes a timeout.

Please report back with information such as:
- How long you've let the test run
- Which IP/Server had the most * / timeout
- General frequency of * occuring.

Make sure you also state where you are from, so the data can be attributed to the proper group.

I'm hoping that we can see a common trend among multiple people from a group, so that we can narrow it down to a single, or a handful of servers causing issues.

I did what you suggested and ran the traceroute batch script. Guess what, im timing out from FFXIV's lobby server at EVERY instance of a timeout.

Quote:

Thu 08/29/2013 14:48:34.68

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

1 2 ms 1 ms 1 ms 192.168.2.1
2 2 ms 1 ms 1 ms 192.168.1.1
3 13 ms 21 ms 11 ms 173.66.42.1
4 16 ms 17 ms 17 ms 130.81.109.156
5 22 ms 13 ms 16 ms 130.81.199.130
6 18 ms 13 ms 16 ms 152.63.30.17
7 20 ms 17 ms 17 ms 152.63.33.13
8 35 ms 35 ms 43 ms 152.179.50.30
9 68 ms 76 ms 69 ms 89.149.185.41
10 71 ms 56 ms 69 ms 216.221.156.110
11 72 ms 53 ms 58 ms 192.34.76.2
12 50 ms 51 ms 54 ms 199.91.189.234
13 66 ms 75 ms 60 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:48:52.14

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.2.1
2 4 ms 1 ms 5 ms 192.168.1.1
3 26 ms 32 ms 13 ms 173.66.42.1
4 73 ms 23 ms 44 ms 130.81.109.156
5 15 ms 34 ms 15 ms 130.81.199.130
6 14 ms 33 ms 24 ms 152.63.30.17
7 25 ms 18 ms 29 ms 152.63.33.13
8 60 ms 79 ms 67 ms 152.179.50.30
9 58 ms 65 ms 72 ms 89.149.185.41
10 82 ms 56 ms 52 ms 216.221.156.110
11 89 ms 91 ms 58 ms 192.34.76.2
12 46 ms 45 ms 56 ms 199.91.189.234
13 57 ms 67 ms 57 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:49:10.18

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

1 3 ms 2 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.1.1
3 54 ms 35 ms 8 ms 173.66.42.1
4 31 ms 29 ms 13 ms 130.81.109.156
5 16 ms 12 ms 35 ms 130.81.199.130
6 34 ms 95 ms 10 ms 152.63.30.17
7 12 ms 13 ms 39 ms 152.63.33.93
8 59 ms 68 ms 60 ms 152.179.50.30
9 59 ms 96 ms 56 ms 89.149.185.41
10 56 ms 58 ms 54 ms 216.221.156.110
11 79 ms 80 ms 81 ms 192.34.76.2
12 63 ms 64 ms 56 ms 199.91.189.234
13 59 ms 58 ms 54 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:49:28.13

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

1 2 ms 7 ms 2 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.1.1
3 19 ms 22 ms 33 ms 173.66.42.1
4 26 ms 12 ms 11 ms 130.81.109.156
5 24 ms 13 ms 37 ms 130.81.199.130
6 52 ms 76 ms 66 ms 152.63.30.17
7 23 ms 15 ms 45 ms 152.63.33.93
8 55 ms 60 ms 55 ms 152.179.50.30
9 50 ms 50 ms 52 ms 89.149.185.41
10 54 ms 64 ms 58 ms 216.221.156.110
11 70 ms 65 ms 65 ms 192.34.76.2
12 51 ms 50 ms 44 ms 199.91.189.234
13 48 ms 51 ms 48 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:49:46.19

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

1 3 ms 1 ms 1 ms 192.168.2.1
2 2 ms 4 ms 2 ms 192.168.1.1
3 42 ms 64 ms 75 ms 173.66.42.1
4 53 ms 21 ms 20 ms 130.81.109.156
5 42 ms 46 ms 35 ms 130.81.199.130
6 67 ms 67 ms 94 ms 152.63.30.17
7 27 ms 15 ms 27 ms 152.63.33.13
8 42 ms 46 ms 64 ms 152.179.50.30
9 73 ms 49 ms 64 ms 89.149.185.41
10 52 ms 53 ms 57 ms 216.221.156.110
11 52 ms 98 ms 68 ms 192.34.76.2
12 89 ms 65 ms 55 ms 199.91.189.234
13 72 ms 62 ms 51 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:50:04.11

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

1 2 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.1.1
3 46 ms 13 ms 9 ms 173.66.42.1
4 42 ms 13 ms 28 ms 130.81.109.156
5 16 ms 15 ms 11 ms 130.81.199.130
6 83 ms 18 ms 26 ms 152.63.30.17
7 15 ms 41 ms 12 ms 152.63.33.13
8 39 ms 56 ms 62 ms 152.179.50.30
9 59 ms 63 ms 52 ms 89.149.185.41
10 50 ms 75 ms 65 ms 216.221.156.110
11 54 ms 46 ms 49 ms 192.34.76.2
12 84 ms 71 ms 67 ms 199.91.189.234
13 103 ms 67 ms 58 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:50:22.15

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

1 15 ms 1 ms 2 ms 192.168.2.1
2 3 ms 2 ms 2 ms 192.168.1.1
3 37 ms 44 ms 85 ms 173.66.42.1
4 112 ms 12 ms 18 ms 130.81.109.156
5 54 ms 15 ms 12 ms 130.81.199.130
6 16 ms 35 ms 13 ms 152.63.30.17
7 15 ms 16 ms 31 ms 152.63.33.13
8 52 ms 45 ms 55 ms 152.179.50.30
9 53 ms 72 ms 62 ms 89.149.185.41
10 75 ms 64 ms 54 ms 216.221.156.110
11 63 ms 46 ms 59 ms 192.34.76.2
12 51 ms 77 ms 70 ms 199.91.189.234
13 56 ms 81 ms 74 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:50:40.12

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.2.1
2 4 ms 3 ms 3 ms 192.168.1.1
3 11 ms 23 ms 16 ms 173.66.42.1
4 14 ms 40 ms 38 ms 130.81.109.156
5 58 ms 62 ms 32 ms 130.81.199.130
6 36 ms 32 ms 16 ms 152.63.30.17
7 18 ms 49 ms 37 ms 152.63.33.13
8 82 ms 58 ms * 152.179.50.30
9 64 ms 56 ms 76 ms 89.149.185.41
10 79 ms 58 ms 49 ms 216.221.156.110
11 57 ms 53 ms 65 ms 192.34.76.2
12 49 ms 84 ms 47 ms 199.91.189.234
13 80 ms 70 ms 58 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:51:01.18

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

1 3 ms 2 ms 3 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.1.1
3 23 ms 12 ms 24 ms 173.66.42.1
4 38 ms 31 ms 36 ms 130.81.109.156
5 12 ms 54 ms 95 ms 130.81.199.130
6 22 ms 23 ms 24 ms 152.63.30.17
7 13 ms 27 ms 33 ms 152.63.33.13
8 29 ms 45 ms 52 ms 152.179.50.30
9 73 ms 61 ms 52 ms 89.149.185.41
10 52 ms 77 ms 64 ms 216.221.156.110
11 71 ms 68 ms 62 ms 192.34.76.2
12 50 ms 54 ms 56 ms 199.91.189.234
13 * 79 ms 44 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:51:23.18

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

1 1 ms 7 ms 2 ms 192.168.2.1
2 1 ms 3 ms 6 ms 192.168.1.1
3 26 ms 11 ms 12 ms 173.66.42.1
4 21 ms 14 ms 29 ms 130.81.109.156
5 23 ms 31 ms 13 ms 130.81.199.130
6 26 ms 14 ms 28 ms 152.63.30.17
7 26 ms 12 ms 34 ms 152.63.33.93
8 32 ms 70 ms 31 ms 152.179.50.30
9 52 ms 113 ms 75 ms 89.149.185.41
10 64 ms 52 ms 62 ms 216.221.156.110
11 60 ms 55 ms 52 ms 192.34.76.2
12 45 ms 56 ms 57 ms 199.91.189.234
13 50 ms 69 ms 63 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:51:41.13

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

1 2 ms 1 ms 2 ms 192.168.2.1
2 3 ms 4 ms 4 ms 192.168.1.1
3 10 ms 9 ms 22 ms 173.66.42.1
4 44 ms 14 ms 24 ms 130.81.109.156
5 46 ms 11 ms 11 ms 130.81.199.130
6 18 ms 17 ms 40 ms 152.63.30.17
7 11 ms 61 ms 27 ms 152.63.33.93
8 37 ms 28 ms 23 ms 152.179.50.30
9 49 ms 88 ms 59 ms 89.149.185.41
10 59 ms 52 ms 51 ms 216.221.156.110
11 127 ms 48 ms 60 ms 192.34.76.2
12 52 ms 69 ms 55 ms 199.91.189.234
13 54 ms 55 ms 60 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:51:59.18

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

1 1 ms 1 ms 5 ms 192.168.2.1
2 3 ms 1 ms 3 ms 192.168.1.1
3 18 ms 30 ms 16 ms 173.66.42.1
4 35 ms 14 ms 14 ms 130.81.109.156
5 188 ms 18 ms 12 ms 130.81.199.130
6 14 ms 25 ms 44 ms 152.63.30.17
7 48 ms 13 ms 41 ms 152.63.33.13
8 37 ms 35 ms 56 ms 152.179.50.30
9 89 ms 81 ms 57 ms 89.149.185.41
10 70 ms 57 ms 52 ms 216.221.156.110
11 55 ms 67 ms 76 ms 192.34.76.2
12 80 ms 79 ms 54 ms 199.91.189.234
13 53 ms 53 ms 52 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:52:17.15

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

1 2 ms 3 ms 2 ms 192.168.2.1
2 3 ms 5 ms 4 ms 192.168.1.1
3 22 ms 36 ms 13 ms 173.66.42.1
4 23 ms 12 ms 41 ms 130.81.109.156
5 98 ms 12 ms 36 ms 130.81.199.130
6 114 ms 66 ms 116 ms 152.63.30.17
7 20 ms 15 ms 25 ms 152.63.33.93
8 35 ms 38 ms 58 ms 152.179.50.30
9 57 ms 50 ms 117 ms 89.149.185.41
10 48 ms 53 ms 67 ms 216.221.156.110
11 81 ms 56 ms 56 ms 192.34.76.2
12 84 ms 56 ms 58 ms 199.91.189.234
13 64 ms 59 ms 61 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:52:35.16

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.2.1
2 2 ms 2 ms 3 ms 192.168.1.1
3 12 ms 9 ms 10 ms 173.66.42.1
4 62 ms 16 ms 41 ms 130.81.109.156
5 123 ms 48 ms 87 ms 130.81.199.130
6 49 ms 42 ms 62 ms 152.63.30.17
7 35 ms 10 ms 28 ms 152.63.33.13
8 45 ms 61 ms 64 ms 152.179.50.30
9 72 ms 65 ms 61 ms 89.149.185.41
10 90 ms 71 ms 66 ms 216.221.156.110
11 80 ms 68 ms 54 ms 192.34.76.2
12 57 ms 78 ms 74 ms 199.91.189.234
13 63 ms 53 ms 50 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:52:53.13

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.2.1
2 3 ms 4 ms 3 ms 192.168.1.1
3 36 ms 11 ms 11 ms 173.66.42.1
4 15 ms 13 ms 46 ms 130.81.109.156
5 29 ms 14 ms 29 ms 130.81.199.130
6 21 ms 12 ms 14 ms 152.63.30.17
7 29 ms 15 ms 36 ms 152.63.33.13
8 30 ms 34 ms 54 ms 152.179.50.30
9 52 ms 45 ms 66 ms 89.149.185.41
10 75 ms 68 ms 51 ms 216.221.156.110
11 57 ms 57 ms 76 ms 192.34.76.2
12 71 ms 69 ms 57 ms 199.91.189.234
13 63 ms 58 ms 63 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:53:11.12

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.2.1
2 2 ms 7 ms 3 ms 192.168.1.1
3 9 ms 9 ms 7 ms 173.66.42.1
4 21 ms 46 ms 12 ms 130.81.109.156
5 27 ms 14 ms 31 ms 130.81.199.130
6 72 ms 33 ms 13 ms 152.63.30.17
7 11 ms 31 ms 29 ms 152.63.33.13
8 50 ms 38 ms 53 ms 152.179.50.30
9 57 ms 53 ms 50 ms 89.149.185.41
10 94 ms 50 ms 59 ms 216.221.156.110
11 52 ms 51 ms 49 ms 192.34.76.2
12 81 ms 60 ms 63 ms 199.91.189.234
13 47 ms 45 ms 43 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:53:29.12

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

1 2 ms 1 ms 2 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.1.1
3 39 ms 19 ms 9 ms 173.66.42.1
4 14 ms 41 ms 13 ms 130.81.109.156
5 31 ms 13 ms 12 ms 130.81.199.130
6 13 ms 28 ms 24 ms 152.63.30.17
7 44 ms 47 ms 26 ms 152.63.33.93
8 59 ms 40 ms 31 ms 152.179.50.30
9 55 ms 74 ms 65 ms 89.149.185.41
10 64 ms 57 ms 62 ms 216.221.156.110
11 71 ms 59 ms 59 ms 192.34.76.2
12 60 ms 63 ms 58 ms 199.91.189.234
13 76 ms 71 ms * 199.91.189.74
14 49 ms 51 ms 53 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:53:51.13

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

1 2 ms 2 ms 4 ms 192.168.2.1
2 3 ms 4 ms 1 ms 192.168.1.1
3 29 ms 11 ms 38 ms 173.66.42.1
4 17 ms 13 ms 32 ms 130.81.109.156
5 125 ms 102 ms 21 ms 130.81.199.130
6 35 ms 62 ms 31 ms 152.63.30.17
7 29 ms 14 ms 26 ms 152.63.33.93
8 50 ms 53 ms 59 ms 152.179.50.30
9 63 ms 59 ms 49 ms 89.149.185.41
10 49 ms 51 ms 56 ms 216.221.156.110
11 95 ms 73 ms 54 ms 192.34.76.2
12 70 ms 61 ms 61 ms 199.91.189.234
13 63 ms 66 ms 62 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:54:09.15

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

1 2 ms 1 ms 1 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.1.1
3 38 ms 10 ms 9 ms 173.66.42.1
4 19 ms 12 ms 18 ms 130.81.109.156
5 130 ms 62 ms 13 ms 130.81.199.130
6 36 ms 13 ms 12 ms 152.63.30.17
7 29 ms 37 ms 12 ms 152.63.33.13
8 31 ms 35 ms 69 ms 152.179.50.30
9 54 ms 61 ms 54 ms 89.149.185.41
10 119 ms 51 ms 49 ms 216.221.156.110
11 58 ms 65 ms 75 ms 192.34.76.2
12 53 ms 57 ms 54 ms 199.91.189.234
13 * 73 ms 52 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:54:31.18

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

1 1 ms 3 ms 2 ms 192.168.2.1
2 2 ms 5 ms 2 ms 192.168.1.1
3 115 ms 52 ms 12 ms 173.66.42.1
4 26 ms 12 ms 47 ms 130.81.109.156
5 14 ms 9 ms 33 ms 130.81.199.130
6 47 ms 19 ms 40 ms 152.63.30.17
7 41 ms 21 ms 18 ms 152.63.33.13
8 45 ms 52 ms 70 ms 152.179.50.30
9 79 ms 57 ms 50 ms 89.149.185.41
10 73 ms 63 ms 66 ms 216.221.156.110
11 54 ms 58 ms 77 ms 192.34.76.2
12 60 ms 63 ms 69 ms 199.91.189.234
13 70 ms * * 199.91.189.74
14 87 ms 69 ms 52 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:54:57.17

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

1 1 ms 1 ms 5 ms 192.168.2.1
2 2 ms 5 ms 8 ms 192.168.1.1
3 49 ms 11 ms 8 ms 173.66.42.1
4 17 ms 38 ms 15 ms 130.81.109.156
5 21 ms 14 ms 21 ms 130.81.199.130
6 74 ms 54 ms 16 ms 152.63.30.17
7 39 ms 15 ms 31 ms 152.63.33.93
8 45 ms 59 ms 53 ms 152.179.50.30
9 53 ms 52 ms 69 ms 89.149.185.41
10 51 ms 53 ms 81 ms 216.221.156.110
11 54 ms 56 ms 85 ms 192.34.76.2
12 51 ms 49 ms 51 ms 199.91.189.234
13 82 ms 56 ms 61 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:55:15.19

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

1 2 ms 1 ms 1 ms 192.168.2.1
2 3 ms 2 ms 2 ms 192.168.1.1
3 15 ms 36 ms 15 ms 173.66.42.1
4 24 ms 50 ms 13 ms 130.81.109.156
5 19 ms 12 ms 28 ms 130.81.199.130
6 100 ms 97 ms 101 ms 152.63.30.17
7 37 ms 22 ms 39 ms 152.63.33.93
8 34 ms 72 ms 77 ms 152.179.50.30
9 56 ms 56 ms 76 ms 89.149.185.41
10 71 ms 61 ms 78 ms 216.221.156.110
11 75 ms 65 ms 51 ms 192.34.76.2
12 81 ms 54 ms 49 ms 199.91.189.234
13 66 ms * 64 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:55:37.14

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

1 2 ms 2 ms 2 ms 192.168.2.1
2 3 ms 2 ms 2 ms 192.168.1.1
3 16 ms 8 ms 19 ms 173.66.42.1
4 25 ms 24 ms 27 ms 130.81.109.156
5 49 ms 16 ms 35 ms 130.81.199.130
6 41 ms 13 ms 32 ms 152.63.30.17
7 35 ms 14 ms 17 ms 152.63.33.13
8 32 ms 59 ms 44 ms 152.179.50.30
9 86 ms 75 ms 74 ms 89.149.185.41
10 72 ms 73 ms 61 ms 216.221.156.110
11 54 ms 93 ms 74 ms 192.34.76.2
12 52 ms 53 ms 88 ms 199.91.189.234
13 51 ms 48 ms 53 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:55:55.16

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.2.1
2 6 ms 2 ms 10 ms 192.168.1.1
3 11 ms 16 ms 19 ms 173.66.42.1
4 41 ms 52 ms 14 ms 130.81.109.156
5 120 ms 72 ms 16 ms 130.81.199.130
6 47 ms 14 ms 24 ms 152.63.30.17
7 24 ms 23 ms 31 ms 152.63.33.13
8 34 ms 33 ms 68 ms 152.179.50.30
9 53 ms 65 ms 118 ms 89.149.185.41
10 79 ms 81 ms 80 ms 216.221.156.110
11 80 ms 84 ms 65 ms 192.34.76.2
12 68 ms 69 ms 59 ms 199.91.189.234
13 58 ms 99 ms 49 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:56:13.17

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

1 2 ms 2 ms 2 ms 192.168.2.1
2 5 ms 2 ms 3 ms 192.168.1.1
3 26 ms 14 ms 48 ms 173.66.42.1
4 52 ms 54 ms 26 ms 130.81.109.156
5 94 ms 91 ms 67 ms 130.81.199.130
6 14 ms 39 ms 13 ms 152.63.30.17
7 14 ms 26 ms 15 ms 152.63.33.93
8 32 ms 42 ms 52 ms 152.179.50.30
9 57 ms 56 ms 56 ms 89.149.185.41
10 57 ms 49 ms 58 ms 216.221.156.110
11 52 ms 52 ms 40 ms 192.34.76.2
12 43 ms 50 ms 62 ms 199.91.189.234
13 66 ms 60 ms 61 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:56:31.14

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

1 1 ms 1 ms 4 ms 192.168.2.1
2 44 ms 2 ms 2 ms 192.168.1.1
3 20 ms 7 ms 24 ms 173.66.42.1
4 37 ms 13 ms 36 ms 130.81.109.156
5 73 ms 106 ms 63 ms 130.81.199.130
6 26 ms 12 ms 35 ms 152.63.30.17
7 26 ms 15 ms 45 ms 152.63.33.13
8 44 ms 43 ms 41 ms 152.179.50.30
9 63 ms 52 ms 57 ms 89.149.185.41
10 60 ms 71 ms 56 ms 216.221.156.110
11 60 ms 49 ms 73 ms 192.34.76.2
12 57 ms 53 ms 67 ms 199.91.189.234
13 69 ms 62 ms 56 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:56:49.13

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

1 5 ms 2 ms 4 ms 192.168.2.1
2 2 ms 2 ms 4 ms 192.168.1.1
3 11 ms 28 ms 14 ms 173.66.42.1
4 12 ms 30 ms 34 ms 130.81.109.156
5 77 ms 66 ms 80 ms 130.81.199.130
6 71 ms 38 ms 14 ms 152.63.30.17
7 44 ms 24 ms 29 ms 152.63.33.93
8 69 ms 45 ms 48 ms 152.179.50.30
9 72 ms 51 ms 64 ms 89.149.185.41
10 68 ms 43 ms 48 ms 216.221.156.110
11 51 ms 49 ms 52 ms 192.34.76.2
12 47 ms 66 ms 80 ms 199.91.189.234
13 80 ms 49 ms 48 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:57:07.15

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

1 1 ms 2 ms 2 ms 192.168.2.1
2 2 ms 2 ms 2 ms 192.168.1.1
3 11 ms 16 ms 11 ms 173.66.42.1
4 17 ms 36 ms 20 ms 130.81.109.156
5 26 ms 48 ms 14 ms 130.81.199.130
6 16 ms 20 ms 20 ms 152.63.30.17
7 35 ms 23 ms 44 ms 152.63.33.93
8 47 ms 63 ms 29 ms 152.179.50.30
9 63 ms 49 ms 61 ms 89.149.185.41
10 80 ms 86 ms 69 ms 216.221.156.110
11 64 ms 54 ms 65 ms 192.34.76.2
12 60 ms 75 ms 57 ms 199.91.189.234
13 * * 54 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:57:33.11

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.2.1
2 2 ms 2 ms 2 ms 192.168.1.1
3 14 ms 16 ms 34 ms 173.66.42.1
4 17 ms 15 ms 40 ms 130.81.109.156
5 12 ms 13 ms 35 ms 130.81.199.130
6 29 ms 13 ms 47 ms 152.63.30.17
7 34 ms 18 ms 15 ms 152.63.33.93
8 34 ms 60 ms 28 ms 152.179.50.30
9 52 ms 98 ms 59 ms 89.149.185.41
10 55 ms 46 ms 58 ms 216.221.156.110
11 77 ms 57 ms 52 ms 192.34.76.2
12 54 ms 53 ms 50 ms 199.91.189.234
13 85 ms 51 ms 59 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:57:51.13

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

1 3 ms 2 ms 2 ms 192.168.2.1
2 3 ms 7 ms 2 ms 192.168.1.1
3 19 ms 7 ms 13 ms 173.66.42.1
4 28 ms 23 ms 28 ms 130.81.109.156
5 33 ms 32 ms 18 ms 130.81.199.130
6 72 ms 31 ms 16 ms 152.63.30.17
7 27 ms 15 ms 11 ms 152.63.33.13
8 39 ms 64 ms 47 ms 152.179.50.30
9 68 ms 60 ms 67 ms 89.149.185.41
10 65 ms 61 ms 52 ms 216.221.156.110
11 80 ms 62 ms 56 ms 192.34.76.2
12 58 ms 48 ms 57 ms 199.91.189.234
13 * 69 ms * 199.91.189.74
14 67 ms 59 ms 76 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:58:17.16

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

1 5 ms 2 ms 48 ms 192.168.2.1
2 3 ms 1 ms 2 ms 192.168.1.1
3 39 ms 15 ms 9 ms 173.66.42.1
4 22 ms 23 ms 23 ms 130.81.109.156
5 30 ms 22 ms 10 ms 130.81.199.130
6 35 ms 19 ms 34 ms 152.63.30.17
7 17 ms 24 ms 19 ms 152.63.33.13
8 47 ms 58 ms 31 ms 152.179.50.30
9 84 ms 63 ms 65 ms 89.149.185.41
10 66 ms 66 ms 64 ms 216.221.156.110
11 68 ms 60 ms 54 ms 192.34.76.2
12 76 ms 60 ms 53 ms 199.91.189.234
13 44 ms * 53 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:58:39.11

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

1 2 ms 7 ms 1 ms 192.168.2.1
2 1 ms 5 ms 5 ms 192.168.1.1
3 40 ms 10 ms 29 ms 173.66.42.1
4 14 ms 30 ms 24 ms 130.81.109.156
5 14 ms 11 ms 33 ms 130.81.199.130
6 59 ms 13 ms 16 ms 152.63.30.17
7 20 ms 22 ms 33 ms 152.63.33.93
8 50 ms 52 ms 53 ms 152.179.50.30
9 54 ms 58 ms 89 ms 89.149.185.41
10 50 ms 51 ms 47 ms 216.221.156.110
11 53 ms 110 ms 53 ms 192.34.76.2
12 58 ms 53 ms 56 ms 199.91.189.234
13 73 ms 65 ms 72 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:58:57.11

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

1 2 ms 2 ms 2 ms 192.168.2.1
2 2 ms 3 ms 9 ms 192.168.1.1
3 18 ms 37 ms 10 ms 173.66.42.1
4 16 ms 39 ms 13 ms 130.81.109.156
5 46 ms 17 ms 12 ms 130.81.199.130
6 87 ms 64 ms 35 ms 152.63.30.17
7 16 ms 13 ms 76 ms 152.63.33.13
8 39 ms 29 ms 45 ms 152.179.50.30
9 77 ms 47 ms 56 ms 89.149.185.41
10 62 ms 68 ms 51 ms 216.221.156.110
11 111 ms 80 ms 46 ms 192.34.76.2
12 54 ms 62 ms 60 ms 199.91.189.234
13 56 ms 55 ms * 199.91.189.74
14 50 ms 47 ms 54 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:59:19.12

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.2.1
2 2 ms 3 ms 5 ms 192.168.1.1
3 27 ms 14 ms 46 ms 173.66.42.1
4 32 ms 15 ms 41 ms 130.81.109.156
5 194 ms 17 ms 14 ms 130.81.199.130
6 32 ms 15 ms 32 ms 152.63.30.17
7 56 ms 13 ms 43 ms 152.63.33.93
8 33 ms 56 ms 60 ms 152.179.50.30
9 64 ms 70 ms 47 ms 89.149.185.41
10 61 ms 63 ms 67 ms 216.221.156.110
11 68 ms 60 ms 68 ms 192.34.76.2
12 48 ms 82 ms 78 ms 199.91.189.234
13 * * * Request timed out.
14 49 ms 51 ms 54 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 14:59:49.12

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

1 3 ms 2 ms 2 ms 192.168.2.1
2 3 ms 3 ms 8 ms 192.168.1.1
3 13 ms 9 ms 17 ms 173.66.42.1
4 19 ms 34 ms 13 ms 130.81.109.156
5 48 ms 76 ms 50 ms 130.81.199.130
6 22 ms 14 ms 27 ms 152.63.30.17
7 34 ms 18 ms 35 ms 152.63.33.13
8 56 ms 64 ms 54 ms 152.179.50.30
9 74 ms 68 ms 65 ms 89.149.185.41
10 56 ms 58 ms 65 ms 216.221.156.110
11 53 ms 51 ms 49 ms 192.34.76.2
12 65 ms 72 ms 55 ms 199.91.189.234
13 * 62 ms * 199.91.189.74
14 * 59 ms 52 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 15:00:19.18

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.2.1
2 4 ms 4 ms 5 ms 192.168.1.1
3 22 ms 11 ms 9 ms 173.66.42.1
4 29 ms 28 ms 57 ms 130.81.109.156
5 62 ms 11 ms 28 ms 130.81.199.130
6 59 ms 33 ms 49 ms 152.63.30.17
7 14 ms 26 ms 15 ms 152.63.33.93
8 51 ms 53 ms 45 ms 152.179.50.30
9 58 ms 55 ms 59 ms 89.149.185.41
10 51 ms 50 ms 62 ms 216.221.156.110
11 54 ms 58 ms 78 ms 192.34.76.2
12 52 ms 59 ms 94 ms 199.91.189.234
13 73 ms * 81 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 15:00:41.14

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

1 1 ms 1 ms 2 ms 192.168.2.1
2 31 ms 3 ms 3 ms 192.168.1.1
3 35 ms 11 ms 9 ms 173.66.42.1
4 16 ms 42 ms 11 ms 130.81.109.156
5 28 ms 10 ms 37 ms 130.81.199.130
6 32 ms 14 ms 20 ms 152.63.30.17
7 13 ms 31 ms 23 ms 152.63.33.93
8 53 ms 65 ms 58 ms 152.179.50.30
9 107 ms 54 ms 58 ms 89.149.185.41
10 80 ms 53 ms 53 ms 216.221.156.110
11 111 ms 79 ms 82 ms 192.34.76.2
12 52 ms 51 ms 52 ms 199.91.189.234
13 57 ms 63 ms 59 ms 199.91.189.74

Trace complete.
Thu 08/29/2013 15:00:59.15

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.2.1
2 51 ms 1 ms 2 ms 192.168.1.1
3 39 ms 11 ms 19 ms 173.66.42.1
4 46 ms 21 ms 44 ms 130.81.109.156
5 88 ms 11 ms 26 ms 130.81.199.130
6 17 ms 14 ms 34 ms 152.63.30.17
7 28 ms 15 ms 41 ms 152.63.33.13

So where do I go from here?

Hi, Syrio Forel from Leviathan NA server here. Same issue, Verizon fios out of Virginia and i'm having trouble with lag in game on this server mainly. I have another toon on Midgardsormr NA and the lag is minimal but still there, about 1-2 seconds but playable as I can dodge stuff still. But yes, i'm confirming my issue as well and would like it resolved soon since Leviathan is the only server all my IRL friends made characters on so I can't play with them on other servers. Please help, thanks.

Quote:

Originally Posted by Fawnlin

https://www.privateinternetaccess.com/

Fawnlin could you give me some information on how you set up your VPN? I bought their VPN but when i turn it on, i am getting even more timeouts than I was without it.

In my opinion it is not the ISP lagging. During my gameplay i can still cast spells and run around, just receive is at 0. Feels like i am sending to the server but not getting anything back.

There is absolutely nothing wrong with my connection, my ISP or my pc. All this disconnect mess started in early access so it's not some coincidence. Talked to plenty others who continually get dc'd then can't get back in or have to try forever.

I mean I can't play.. I can't do dungeons or anything important cause of the 15-20 dc's a day. S/R is always something like 25/3000. This is going to be resolved right? I mean where is the confirmation from them about the disconnects? I guess it's all tied in eh.

Is this all to be resolved with the server upgrades they are doing? Trying to be patient but who wants to play and get dc'd daily over and over and over and then have to deal with getting back in the servers. Looking more like launch for me will be maybe weeks or longer from now.

I wanna play. I paid for 1.0 CE, I paid for 2.0 PS3 CE.. tested all the betas and supported the game.. I wanna play lol.

Still having same issues, i'm from UK using BT and its really annoying me now. No issues in P3, P4. Only started in EA and Launch.
Hopefully when they upgrade servers it will fix the issue.

I did try a VPN has someone suggested earlier and it "appeared" to help, but then again it could have been just dumb luck for all I know. Verified with my Central Texas provider (Time Warner Cable) nothing going on from my end.

One thing I have noticed, is if you are in your INN the connection S/R seems to go smoothlyn and will only start up again if I get out of the INN room. (This occurred with and without going through the VPN)

Bump for good information and hopefully a solution!

I would add this has been happening to myself as well, sporadically but typically worse midday till early evening. I'm based in San Francisco Bay Area using Comcast ISP. The worst was on monday but since then every day it gets a little better, but the lag issue still occurs.

Justice bump.

dinner time bump

Square Enix. We know this is a problem on your end already.

I'm having issues with the server as well. I'm on the NA/EU data center. I have Cox Communications in Phoenix, Arizona. 50Mb/10Mb internet connection. I can't progress past Titan because I get R0s during his Landslide attack and can't dodge it. I get 100ms ping to the server and no issues during traceroute so I'm not sure what the issue is, but it's frustrating not being able to dodge attacks that one shot you.

Bump! For visibility this evening.

Already happening more often, even when I can login just fine (HA the irony)

Bump, since we're really getting lost in the World is Full threads...

Another day. I guess I'll see how it goes this time.

Bump because this is more important than all the duplicate Error 1017 threads.

I'm giving up playing until this is fix thou... the funniest things is most of us able to login but play in a unplayable lag T.T