-
Yeah...So I wanted to try now that it's later in the day. I am having issue even logging in to the game at this time of day. Visual here as "Poor". https://i.imgur.com/feD2jd9.png
Damn that's awful. My latency has now become entirely unstable like it usually has been the past few weeks.
I'm getting severe packet loss, my latency has went from a very normal 76ms to fluctuating wildly between 85-117ms. I'm talking like 4-6 seconds of rubberbanding.
I can still ping google.com with no problem, and I can log in to my other games with no latency issues.
I joined a e5s just to see what would happen, but its not just me, they're all lagging so hard we can't do mechanics. Hell some of the mechanics don't even seem to exist because you lag so hard you can't see them.
I said I'd off tank because the lag spikes, but I lagged so hard that I never saw the add even spawn or attach to me, or walk to me. I just died after everyone ran in place for a few seconds on screen.
Can anyone ping the server with less than 100ms, and not get packet loss at this time of day? Is this a new issue? Is this just how its always been and I never knew?
-
Been happening here as well on two different accounts on two separate computers. Internet works fine elsewhere but FF14. This was an issue all day, and it seemed to be related to AT&T being blocked by SE or the other way around. Maybe a DDoS? Seemed to happen to others on discord who are on AT&T. FF14's IPs were getting lots of packet loss.
-
Looks like they've fixed packet loss, but not the variable ping. Earlier in the day I did a ping check, got my ~85ms consistently across 100 pings. Did a test just now, and it's consistently ~115ms.
So what's causing +30ms? Even in primetime in the past it might go up single digits, but not this huge amount.
Edit: nevermind, the packetloss is back again. It's 10:06AM in Japan right now, are they doing some kind of heavy workload testing in live servers right now?
-
Been getting this, myself, for the past couple weeks. Everything else runs perfectly except FF14, and the best I can get after switching between Data Centers a few times is "Good" when finally logging into Primal, when before, it never dipped below "Excellent". I was able to get a stable connection on the evening of 11/9, but nothing like it since.
-
Having this issue as well since Monday (11/9/2020). Constantly dropping connection in FFXIV only (S:0 repeatedly)- other online games, websites, and streaming are all fine and uninterrupted. Comcast, North East US.
-
Same issues here on Jenova, starting today around lunch CST. Major rubberbanding once every few seconds. Completely unplayable. I am a network engineer; I've run diagnostics on my home network, and ruled out any issues on my end. Zero packet loss to Google DNS over a 10 minute trace, and a rock solid 900 up/900 down fiber connection. All other games (including MMOs), streaming, et al, function normally, with no performance degradation. Using AT&T fiber, Southeastern US.
Meanwhile, traces to FFXIV show 50% packet loss. The issue occurs once I hit an Akamai-owned address block. Akamai is often used by MMOs to protect against DDoS attacks. Oddly, the connection icon within the FFXIV UI shows me with "Good" connection.
-
Having crazy lag spikes in game today. Here's my tests:
Tracing route to 204.2.229.98 over a maximum of 30 hops
3 10 ms 4 ms 4 ms 99.176.76.234
4 4 ms 4 ms 4 ms 99.15.141.86
5 8 ms 6 ms 5 ms 12.83.106.9
6 120 ms 85 ms 24 ms 12.122.29.186
7 106 ms 22 ms 132 ms 12.122.141.233
8 17 ms 17 ms 17 ms 192.205.36.158
9 20 ms 20 ms 20 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 31 ms 34 ms 31 ms ae-4.r25.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
11 112 ms 83 ms 133 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 69 ms 70 ms 69 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 72 ms 72 ms 72 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 80 ms 75 ms 75 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 72 ms 72 ms 72 ms 204.2.229.234
16 73 ms 72 ms 72 ms 204.2.229.98
Trace complete.
Microsoft Windows [Version 10.0.19041.572]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Users\Me>ping 204.2.229.98 -t
Pinging 204.2.229.98 with 32 bytes of data:
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=228ms TTL=49
Reply from 204.2.229.98: bytes=32 time=134ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Request timed out.
Reply from 204.2.229.98: bytes=32 time=71ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=164ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=248ms TTL=49
Reply from 204.2.229.98: bytes=32 time=157ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=74ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=179ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=171ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=149ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=208ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=173ms TTL=49
Reply from 204.2.229.98: bytes=32 time=239ms TTL=49
Reply from 204.2.229.98: bytes=32 time=149ms TTL=49
Reply from 204.2.229.98: bytes=32 time=228ms TTL=49
Reply from 204.2.229.98: bytes=32 time=124ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=100ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=270ms TTL=49
Reply from 204.2.229.98: bytes=32 time=76ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=213ms TTL=49
Reply from 204.2.229.98: bytes=32 time=154ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=96ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=229ms TTL=49
Reply from 204.2.229.98: bytes=32 time=169ms TTL=49
Reply from 204.2.229.98: bytes=32 time=211ms TTL=49
Reply from 204.2.229.98: bytes=32 time=269ms TTL=49
Reply from 204.2.229.98: bytes=32 time=170ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=89ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=158ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=73ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=72ms TTL=49
Reply from 204.2.229.98: bytes=32 time=159ms TTL=49
Tracing route to 204.2.229.98 over a maximum of 30 hops
3 99.176.76.234
4 99.15.141.86
5 12.83.106.9
6 12.122.29.186
7 12.122.141.233
8 192.205.36.158
9 ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 ae-4.r25.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
11 ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 204.2.229.234
16 204.2.229.98
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0/ 100 = 0% |
3 19ms 0/ 100 = 0% 0/ 100 = 0% 99.176.76.234
0/ 100 = 0% |
4 17ms 0/ 100 = 0% 0/ 100 = 0% 99.15.141.86
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% 12.83.106.9
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 12.122.29.186
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 12.122.141.233
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 192.205.36.158
0/ 100 = 0% |
9 31ms 0/ 100 = 0% 0/ 100 = 0% ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
0/ 100 = 0% |
10 58ms 0/ 100 = 0% 0/ 100 = 0% ae-4.r25.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
0/ 100 = 0% |
11 95ms 0/ 100 = 0% 0/ 100 = 0% ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
0/ 100 = 0% |
12 99ms 0/ 100 = 0% 0/ 100 = 0% ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
0/ 100 = 0% |
13 98ms 1/ 100 = 1% 1/ 100 = 1% ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
0/ 100 = 0% |
15 96ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.234
0/ 100 = 0% |
16 95ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.98
Trace complete.
-
On Siren I've been getting severe lag around primetime ever since the latest maintenance (I say primetime as that's when I start playing and it seems to calm down later at night).
Not everyone seems to get lag but several of my FC mates do.
-
All of the above issues on Exodus. Rubber Banding. Disconnecting. Game freezing up. Was in Puppet's Bunker today and the entire alliance was complaining about it. Was practically unplayable.
-
Greetings everyone!
We appreciate you all for bringing this to our attention. For us to look into your concerns properly, we would like for you to provide additional details following our template below.
• Type of Issue/Feedback: (What type of issue are you encountering? Be as detailed as possible!)
• Name of your Internet Service Provider (ISP):
• State/Country:
• Date/Time: (When did the issue start happening, at what specific times does this issue arise, if any.)
• World Name:
• Frequency: (How often does the issue occur?)
• Traceroute records (optional) (Learn how to generate traceroute record)
Thank you!