- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Spoke with a level 2 verizon tech, he said that they will not fix this issue as it is not their responsability.
Spoke wtih a square enix support rep (after much hassle) and they said that they will not fix this issue as it is not their responsability.
So basically we are all **bleep** (Surely out of luck :P).
There are now multiple threads on multiple forums about this but verizon continues not to care.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Horrid lag in Final Fantasy XIV here in Bradenton, FL as well. Damned near unplayable.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having the same problom & i'm from texas please fix it
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Reston,VA Same problem.
FFXIV Exodus Server. VerizonTech Support is clueless. Punching the clock.
Can we add a "If you work as an IT Professional and Don't Want to Be Told to Restart Your Device Again and get a real Fing Technichician (if you are lottery ticket lucky) on the Line Press 9" to the dialing tree please?
THX
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, still waiting for Verizon to sort out their packetloss.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You guys are not alone in this issue. I have expereienced this issue on both Final Fantasy and Planetside 2 since that time and with no other games or locations. After much searching and working around without the help of Verizon support (as all they will ever do is say things like , restart your router, or speed test, and the occasional I have restarted your junction box in your home) I found an article about Verizon's service and how it is lost with Alter.Net and pingplotter and traceroute both came back for both games with that exact same domain between them.
It seems like Verizon is taking the stance that they aren't to blame since it's not their location, and who could honestly blame them. Sadly other companies have taken it upon themselves to contact companies and secure more reliable routes through their systems and Verizon isn't doing the same.
Guess if you want to play any game or visit any website that travels through that domain you're most likely in trouble.
Guess it's a good thing we have so many other options available to us, but I am truely disheartened that I will have to give up a service i love to enjoy doing things I always had in the past.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Skybroadband finally replied about the packetloss blaming level3 and they are looking into it: http://helpforum.sky.com/t5/Fibre-Broadband/Final-Fantasy-XIV-troubles/td-p/1579761/page/2
So when will my fios contact level3 also?
Heres my pings:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Paul>tracert 199.91.189.57
Tracing route to 199.91.189.57 over a maximum of 30 hops
1 3 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 5 ms L100.DLLSTX-VFTTP-53.verizon-gni.net [173.71.42.
1]
3 8 ms 6 ms 7 ms G0-3-4-2.DLLSTX-LCR-22.verizon-gni.net [130.81.2
15.206]
4 6 ms 6 ms 7 ms ae4-0.DFW9-BB-RTR2.verizon-gni.net [130.81.199.6
6]
5 7 ms 7 ms 8 ms 0.xe-3-0-3.BR1.DFW13.ALTER.NET [152.63.98.245]
6 53 ms 8 ms 8 ms ae6.edge2.dallas3.level3.net [4.68.62.165]
7 69 ms 69 ms 67 ms vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
8 66 ms 63 ms 66 ms ae-91-91.ebr1.Dallas1.Level3.net [4.69.151.162]
9 67 ms 68 ms 68 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]
10 68 ms 66 ms 67 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
11 64 ms 67 ms 67 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177]
12 49 ms 49 ms 49 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
13 66 ms 67 ms 66 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
14 80 ms 64 ms 68 ms 192.34.76.10
15 65 ms 64 ms 64 ms 199.91.189.242
16 64 ms 64 ms 66 ms 199.91.189.57
Trace complete.
C:\Users\Paul>
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since Ravnis mentioned Planetside 2 ...
Since last Wednesday Fios customers have been experiencing terrible latency with the VA datacenter servers. By comparing Traderoutes with people who are and are not experiencing problems, I strongly suspect that the problem is occurring around here:
llnw-gw.customer.alter.net [152.179.29.230]
Of course I'm not sure what to do with that information. It's a Limelight Networks gateway and neither SOE nor Verizon controls it so all I can do is beg Customer Service to look into it and take ridiculous steps myself like going through a VPN.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Netflix is primarily using LLNW and Level 3 for content delivery these days. As a result, Verizon is blatantly allowing peering points with LLNW and Level 3 to become overly saturated.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This issue is happening with me as well and it has to do with Level3 for me in Pennsylvania. I tried calling tech support and handing them traceroutes but they just asked me to reset my router or restart my computer. I asked to be transferred to higher tier of support and they denied me. Verizon please look at this issue SE cant solve the issue. The ISP's that are having these issues and solving them are the ones who need to get in touch with Level3 and Cogent.