Problems with connection (R0) lag

[Mattlex]

Dear SE, please can you aknowledge that you are aware of this issue and are looking into a fix? It is affecting a lot of people who are unable to enjoy the game because the lag spikes are happening a lot and. It is affecting people with different ISP's and locations so it must be something that was changed server side.

[Bebekurenai]

In for the bump, boyfriend and I also with the same problem, since Tuesday 5-10 seconds lag and making dungeons impossible. On Sky UK.

[configer]

Yes allso a sky fiber user , elastic banding i think the phrase is , its impossable to play . the problem is ive phoned sky and they cant find a problem . And i dont see SE adding to this at all.....

[Riko_Futatabi]

I've contacted Sky twice today querying things and they do say that they don't block anything and everything else connects fine(web browsing etc.). It's just this rubber-banding during play it must be these data centers, I connect to NA data center from the UK - (184.107.107.176). I noticed when doing multiple ping tests via my Sky HUBs IP address page that occasionally there's packet loss to the NA data center IP, but that should be obvious with this rubber-banding going on!

Done this a few times in command prompt this is just a snip from it:

C:\Users\UKGC>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=96ms TTL=55
Reply from 184.107.107.176: bytes=32 time=97ms TTL=55
Request timed out.
Request timed out.

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 97ms, Average = 96ms

C:\Users\UKGC>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=97ms TTL=55
Reply from 184.107.107.176: bytes=32 time=97ms TTL=55
Reply from 184.107.107.176: bytes=32 time=97ms TTL=55
Reply from 184.107.107.176: bytes=32 time=98ms TTL=55

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 98ms, Average = 97ms

C:\Users\UKGC>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=97ms TTL=55
Request timed out.
Reply from 184.107.107.176: bytes=32 time=97ms TTL=55
Reply from 184.107.107.176: bytes=32 time=97ms TTL=55

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 97ms, Average = 97ms

[TiaJ]

Same thing is happening to me, Im currently awaiting a reference number from Sky regarding the issue.

[pompey_dan]

I'm also from the UK using Sky internet, I was having problems especially on Tuesday, Titan was unplayable.

SOLUTION: unfortunately was to use Pingzapper, this sorted the problem for me right away, was perfect after. You can try it for free for one hour at a time before it disconnects you, it is only something like £3 a month without contract but it is defiantly worth it as this problem seems similar to the FiOS routing problems the Americans are having, my FC friend using FiOS also downloaded and started to use Pingzapper and it sorted his problems out too.

quoted from the other thread on this to try help people in the UK using Sky/BT.

[edgefusion]

Just want to add I'm also on Sky in the UK and experiencing the same crippling lag as everyone. Instances are unplayable, I really hope it gets sorted out ASAP.

[Jyan91]

Just want to add I'm also on Sky in the UK and experiencing the same crippling lag as everyone. Instances are unplayable, I really hope it gets sorted out ASAP.

same here, also with sky and having these problems

[Musaid]

quoted from the other thread on this to try help people in the UK using Sky/BT.

Just tested Pingzapper and it sorted out the problem. However, I'd prefer that I didn't have to use it when I didn't need to before this.

[Musaid]

Still having the problem, even after the maint.