For those with Verizon FIOS getting lag while playing FF14 on the Canada Data Center

[Zamaza]

I contacted Verizon, they said they are unable to do anything about this as the issue is with Level 3. Verizon advised that Square needs to work with Level 3. I referenced the original ticket in this thread, and also had my own created.

I've opened a ticket with SE on this as well via email, and plan on calling them tomorrow. I am no longer able to do Coil/HM/EX because of this issue and it has made me play much less over the last week. I was considering unsubscribing until I saw this and that other people are having this issue as well. ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] is where I have been having problems for around 3 weeks.

EDIT: Please open a ticket with SE about this if you have this problem and have not already!

[rweezy]

I talked to normal tech support and "premium tech support". They both could not find anything when i referenced the ticket numbers, stating they don't see anything or they need the name or phone number of the account to see any info. They both had no idea what to do. Everything else works fine for me, youtube, other games no lag, just FF so that is why I think they did not know what to do. One of the tech guys said something about game algorithm thing you can turn off on your computer to improve latency but it will lag your browsing a bit. Basically though I got nowhere :/

[Renarudo]

I live in Queens NY on FIOS and My Ping to Excalibur has never gotten over 40 ms. I can submit this and at least let them know where the problem isnt? I guess?

2 8 ms 5 ms 6 ms L100.NYCMNY-VFTTP-213.verizon-gni.net [108.6.47.1]
3 9 ms 18 ms 9 ms G0-1-4-7.NYCMNY-LCR-21.verizon-gni.net [130.81.185.56]
4 6 ms 6 ms 14 ms so-5-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.22.16]
5 9 ms 8 ms 9 ms 0.xe-8-0-0.BR3.NYC4.ALTER.NET [152.63.23.241]
6 20 ms 21 ms 18 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
7 21 ms 18 ms 19 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 17 ms 15 ms 15 ms ae-47-47.ebr2.NewYork1.Level3.net [4.69.201.33]
9 17 ms 15 ms 16 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
10 18 ms 15 ms 15 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
11 16 ms 17 ms 18 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
12 30 ms 29 ms 29 ms 192.34.76.10
13 27 ms 29 ms 26 ms 199.91.189.242
14 33 ms 32 ms 33 ms 199.91.189.38

Trace complete.


Looks like maybe using ae-11-11.car2.Montreal2.Level3.net might be 1 part of the resolution.

[Ashodai]

This might be what is happening to me since patch 2.1. Never had lag before 2.1. Anyone know the ip address for Behemoth server?

[Silkysmooth]

So, this is the trace route that I have done, now bearing in mind I am about as technically minded as a hamster.....I had to go look up traceroutes explained to work out roughly what the gaff is with this....so apparently.....I have some serious issues connecting to that IP address in Montreal......
I have no idea what this really means, so if anyone here can enlighten me as to what it means in layman's terms...ie something a caveman can understand, that would be lovely.


1 1 ms 1 ms 1 ms SkyRouter.Home
2 * * * Request timed out.
3 30 ms 31 ms 31 ms ip-84-38-37-64.easynet.co.uk [84.38.37.64]
4 28 ms 28 ms 29 ms ae99.edge3.London2.Level3.net [212.187.201.57]
5 27 ms 28 ms 27 ms ae-0-11.edge4.London2.Level3.net [4.69.200.126]

6 114 ms 103 ms 103 ms ae-3-3.ebr1.London1.Level3.net [4.69.141.189]
7 104 ms 104 ms 104 ms ae-42-42.ebr1.London1.Level3.net [4.69.167.22]
8 104 ms 103 ms 105 ms vlan104.ebr2.London1.Level3.net [4.69.143.98]
9 104 ms 103 ms 105 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

10 104 ms 105 ms 104 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]

11 105 ms 104 ms 104 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]

12 103 ms 208 ms 104 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
13 220 ms 210 ms 215 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

14 103 ms 105 ms 104 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178
4]
15 104 ms 117 ms 104 ms 192.34.76.10
16 105 ms 105 ms 105 ms 199.91.189.242
17 104 ms 105 ms 105 ms 199.91.189.38

[Silkysmooth]

Well, new patch, still laggy as hell, last night at peak time, I was tanking Svara in Coerthas, I suffered a 40 second lag spike where everything froze...by the time it sorted itself, svara was dead and I was alone....I can't even do wanderers palace, let alone raids.....
I've checked my graphics card, that's working fine, I've done ping tests, that's fine.....It would be nice if Square would just acknowledge the problem rather than this blanket ignorance......I wonder if they feel that if they acknowledge the problem they'll then be held accountable...by ignoring it, it's not their problem...
Going to cancel my automatic subscription right now.....impossible to do the most simple of tasks in game now....

[MikeBoston26]

Contacted Verizon and referenced OP's ticket number. They could not add on to it as it was not opened under my account so I created a ticket of my own. They ran some command and told me the problem was fixed. I knew it wasn't. I ran another tracert with them on the line to prove it. They contacted the networking team and came back with "they are aware of the issue and are working to fix it." Not sure I believe that, but at least yet another ticket was created and maybe the flood will draw some attention.

[Wobbler]

To the creative folks that some how managed to get my email address, emailing me your traceroutes isn't going to help If you're with Verizon, give them a call on the number listed in the first post.

Also for those that are wondering how to your server IP, there is two ways, the easy and the harder.

The easy is to head over to http://www.arrstatus.com/ and mouse over your server. Some people have reported that this is incorrect however for both the servers that I have played on it has been right.

The hard way is to download wireshark, start packet capture on your network device used for communications for FF14 (usually your NIC or Wireless NIC prolly listed as Local Are Connect).

Start the game (if you're paranoid you can already have it running).

Click statistics, endpoints.

Click the IPv4 tab and just look for the address where the majority of your traffic is going.

The main assumption with this approach is that you don't have anything else with a lot of traffic going on at the time, eg watching videos, streaming movies, etc

[Leelya]

4.69.141.5 is from United States(US) in region North America

Whois query for 4.69.141.5...

Results returned from whois.arin.net:

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#


#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=4....se&ext=netref2
#

NetRange: 4.0.0.0 - 4.255.255.255
CIDR: 4.0.0.0/8
OriginAS:
NetName: LVLT-ORG-4-8
NetHandle: NET-4-0-0-0-1
Parent:
NetType: Direct Allocation
RegDate: 1992-12-01
Updated: 2012-02-24
Ref: http://whois.arin.net/rest/net/NET-4-0-0-0-1

OrgName: Level 3 Communications, Inc.
OrgId: LVLT
Address: 1025 Eldorado Blvd.
City: Broomfield
StateProv: CO
PostalCode: 80021
Country: US
RegDate: 1998-05-22
Updated: 2012-01-30
Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
Ref: http://whois.arin.net/rest/org/LVLT

OrgNOCHandle: NOCSU27-ARIN
OrgNOCName: NOC Support
OrgNOCPhone: +1-877-453-8353
OrgNOCEmail: noc.coreip@level3.com
OrgNOCRef: http://whois.arin.net/rest/poc/NOCSU27-ARIN

OrgAbuseHandle: APL8-ARIN
OrgAbuseName: Abuse POC LVLT
OrgAbusePhone: +1-877-453-8353
OrgAbuseEmail: security@level3.com
OrgAbuseRef: http://whois.arin.net/rest/poc/APL8-ARIN

OrgTechHandle: IPADD5-ARIN
OrgTechName: ipaddressing
OrgTechPhone: +1-877-453-8353
OrgTechEmail: ipaddressing@level3.com
OrgTechRef: http://whois.arin.net/rest/poc/IPADD5-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#

Not sure if this would be a good place to start since that is the device that all of the lag originates from, but it might be worth a shot since Verizon is wiping their hands clean of it.

[Pawtucket]

unfortunately i spoke with verizon extensively regarding this and the end result is verizon isn't responsible for this issue since its outside of their network/range of control. we need to contact the source of the issue, which is level3. we can also contact SE and let them know that the route they've chosen to use for use is not performing up to any sort of standard.

i attempted to hold verizon responsible for this, telling them that since i'm their customer and i'm unhappy, that it is ultimately their responsibility to make me happy and thus reach out to level3 and attempt to resolve this issue... don't think that worked out so well

to further expand on why we should contact SE, this is a problem THEY created with the addition of their "data centers" to reduce their so called "login server" issues if i remember correctly. nobody had any of these issues before 2.1