I doubt its the providers fault seeing as there are different providers for us. The only common thing is SE
I doubt its the providers fault seeing as there are different providers for us. The only common thing is SE
Signature by Okiba Key
"The real way to a woman's heart is to have a lot of gold so she can rob you mores - Alisanne Wonderland
Absolutely spot on with this thread. The lack of any word from SE has left me feeling rather defeated. It's a clear issue for many players. Every day I liase with my isp but im still no further toward a solution and at this point im starting to feel remorse for incessantly hounding them.
And yet, plenty of people are playing against the same servers without issues.
The major problem exists between your providers and SE's provider.
Most commonly the problem has been traced to Level 3 Communications backbone nodes.
I connect from Sweden, and have not had any issues with lag spikes. My connection to SE also doesn't go through Level 3 nodes.
You could always try to convince SE to move their NA datacenter elsewhere.
Last edited by Nekodar; 01-20-2014 at 10:27 PM.
I'm also on Sky broadband in the UK. Last week the lag started to get really bad in CT (stops then runs at super speed to catch up). Tried to help some FC members get their relics on Titan HM any attack other than the bombs was unavoidable (i was even frozen in the air for awhile). It's not just running dungeons that are a problem, crafting, doing any of the miner or btn leve quests takes forever to load and is now impossible to actually get speed completion (took over 9 minutes to complete 4 nodes - that's madness).
Wish the old issue i had of being stuck in cast animation when running CT was still just limited to that particular raid because at least I could glide to hide behind a comet with the behemoth battle. I'm finding in order to survive I'm having to hide behind the comets well in advance of the grrrrr warning. This shouldn't be the case, please do something about this and soon.
You're probably right about the Level 3 node issue; most tech savvy people who discuss this in forums seem to draw the same conclusion. However, I have yet to find anyone getting a comment from SE or their ISP to confirm this. So is the problem being ignored in the hopes that it'll go away? And what are the odds that SE would actually consider moving their NA data center elsewhere?And yet, plenty of people are playing against the same servers without issues.
The major problem exists between your providers and SE's provider.
Most commonly the problem has been traced to Level 3 Communications backbone nodes.
I connect from Sweden, and have not had any issues with lag spikes. My connection to SE also doesn't go through Level 3 nodes.
You could always try to convince SE to move their NA datacenter elsewhere.
Spot on. A lot of people are either blaming specific ISP's or Square, or saying it's nothing to do with one or the other without really knowing what's happening. The problem is between both parties, as there are plenty of players on different ISPs that are unaffected.
Regardless, the lack of official response to this problem is still ridiculous.
I'm also in the UK with SKy Broadband and have the same problem. Fed up of not being able to run primals and being almost useless in dungeons. This needs fixing!
After post 2.15 I felt like it was "resolved" but no after a few days it started all over again. please CM's at least post so that we'll know you know there's a problem and youre working on it
Signature by Okiba Key
"The real way to a woman's heart is to have a lot of gold so she can rob you mores - Alisanne Wonderland
Also having problems since last wednesday (22 jan) with packet loss. (lag spikes then fast forward) on Moogle (EU) server.
(Server IP: 199.91.189.50)
Trace route shows packet loss at these points as soon as it goes to atlas.cogentco.com services
6 * 29 ms 29 ms te0-2-0-5.ccr21.lon01.atlas.cogentco.com [130.117.14.205]
7 30 ms 29 ms * be2316.mpd21.lon13.atlas.cogentco.com [154.54.73.113]
8 36 ms * 36 ms be2285.ccr21.lpl01.atlas.cogentco.com [130.117.49.126]
The next point has no packet loss, even with ping tests.
9 137 ms 137 ms 135 ms be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44.137]
So at least for me problems lies in the three bolded IP's.
Ping tests for problem IP's:
Ping statistics for 130.117.14.205:
Packets: Sent = 251, Received = 204, Lost = 47 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 137ms, Average = 29ms
Ping statistics for 154.54.73.113:
Packets: Sent = 77, Received = 57, Lost = 20 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 29ms, Average = 28ms
Ping statistics for 130.117.49.126:
Packets: Sent = 94, Received = 83, Lost = 11 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms,Maximum = 43ms, Average = 41ms
Last edited by Aleo; 01-27-2014 at 11:11 PM.
Keep posting. The general rule they're likely to follow is that if you stop complaining, it must not be bothering you anymore. Keep your threads bumped, and if you can post any data, such as trace routes, do it. I plan to bump mine with new trace routes daily. I can't right now because I'm at work
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.