Since you are in Europe, you probably connect to one of the NTT service nodes located in New York City. (Outside of your ISP's network, it acts as a proxy between you and the FFXIV NA servers which are located in Sacramento, CA, USA)Quote:
Originally Posted by Kurando
There are multiple nodes before you reach the FFXIV NA Datacenters as you bounce from nodes to nodes as intermediaries.
(As Baingoleth pointed out, this is one of the NYC affected nodes -> *.nycmny01.us.bb.gin.ntt.net)
Try to do a tracert/traceroute.
Any plans to address severe server issues?
Printable View
-
11-08-2017, 08:56 PMAkaeiNox
-
11-08-2017, 09:08 PMHyoMinPark
SE did put out something about DDoS attacks; I wasn’t really affected until last night when my static and I were raiding. Every other pull half of us were visibly dc’ing/red-dotting.
-
11-08-2017, 09:46 PMAltena
I have had 0 connection problems for the last couple of months, aside from a couple of hickups that were purely due to my choice of routing.
Yes, I use a VPN.
I am an Aussie.. And I play on the NA servers.
The problems are really not with SE servers, but are with the route between your home and the SE servers.
You have to realise that if you are having problems but some others aren't, then the problem area is likely somewhere between your own house and the destination - not the destination itself..
If it was the destination, absolutely everyone would be affected, because it is the only common denominator here..
Not everyone drives the same way to work as you do.
If there is a crash on the highway on your route to work, doesn't mean your work building is collapsing. -
11-08-2017, 10:02 PMKaoru_Nagisa
Been having recent bouts of severe, sudden lag before things are fine again. DC'ing now and then but that happens to me sometimes, though I oddly have only dc'd from the lag once... while doing absolutely nothing save for hanging out in Ul'dah.
Had both myself and the ninja in a Copperbell Leveling Roulette run nearly dc though. We both said things just completely stopped for a good minute or so before suddenly everything played through fast-forward and put us back to normal. We didn't have any other problems after that (was at the slime boss), but it was so bad I actually swore off doing Rabanasty last night out of fear half the raid would experience that. Saw plenty of people in the Quicksand and Tamamizu with the dc symbol too.
Whatever's going on, I hope it gets fixed soon/stops entirely. x.x;
EDIT: Oddly, I've only been seeing reports in from primarily Aether servers with a few others scattered across. Though even there, it seems spotty on who gets affected - both myself and that ninja did, but our BLM and CNJ were fine. Was really strange. -
11-09-2017, 01:30 AMNiraves
Standing in Quarrymill, I'm looking around at a sea of red circles. At least seven players all randomly lit up with the disconnecting symbol. Its getting a little ridiculous. I'm scared to even try to craft anything because if I dc in the middle of it I'm out a potential million gil profit.
-
11-09-2017, 03:11 AMRLofOBFL
Just bumping this bc I basically can't do any semi hard content with this awful lag spikes that happen randomly(usually when I am about to clear something).
-
11-09-2017, 03:16 AMrxnin
Bump, Savage clears has truly been savage this week.
-
11-09-2017, 03:30 AMZarkovitch
If only server where on chicago not middle nowhere like sacramento even montreal got some outage still better than sacramento current situation.
-
11-09-2017, 04:01 AMreiichiThe amount of packetloss has significantly decreased after their move to the NTT datacenter. But NTT also only has two datacenters in the US. San Jose and Washington DC. Given that they were receiving numerous complaints about a datacenter on the east coast, they picked the west coast one as anyone on continental northern america should typically be just fine. Europeans were given their own datacenter and if they were looking for a stable gameplay experience, would be encouraged to go and play there. It also improved the connection for players in Austrailia if they were connecting to NA servers.Quote:
Originally Posted by Zarkovitch
Chicago, Houston, and Dallas are not options while using NTT's backbone. And if SE were to switch datacenters AGAIN for some reason, it'd still depend on the provider, their backbone, their peering with other providers' backbones and last-mile (home/corporate) ISPs for a connection. And 10-20ms of negligible connection latency wouldn't be worth that. A more stable connection is valued much more important than one in an arbitrarily nicer geographical location. -
11-09-2017, 04:50 AMErudito
I agree that there is something wrong. Either with the servers or the connection. I have been getting some very nasty lag for the past 3 days consistently. Are we under attack again?
-
11-09-2017, 05:34 AMDaniolaut
I am going to edit the original post showing all posts from as many players as possible stating having issues. If we can continue to bump this thread maybe Square-Enix will take notice and at least make an announcement.
-
11-09-2017, 05:36 AMValkyrie_Lenneth
They did, it's on the lodestone
-
11-09-2017, 05:58 AMdotsforlifeTake your own advice.Quote:
Originally Posted by Daniolaut
-
11-09-2017, 07:49 AMCuddlyRyuu
Three days I get a random DC icon and the Error 90002, I have to reconnect. I don't have a bad connection in any other Online games, it's going well and I'm very competitive in them so I'd have noticed if something was wrong. I am content doing my crafting dailies on my alt but I do need my daily expert too, I still didn't do it today but Monday it was bad for 3 of us, the healer was fine. Yesterday my partner DPS complained and the tank dced during a pull, I asked what error he got: 90002. I was fine all the way through but once I was out, I got DCed again. Today during my Ixal/Moogle dailies I got DCed, I didn't log for long since I came from work 48 minutes ago to do them before doing something else. At this point, it's annoying. I think most doesn't complain since it's random and they might wait for the fix or until DDoS attack to be reduced, I sure didn't mind that much and thought it'd be fixed soon but now it's ridiculous.
-
11-09-2017, 08:10 AMLastFireAce
I'm pretty sure was just concast and no XIV because evrything was bad on my end, all good now.
-
11-09-2017, 08:12 AMMesarthim
The first day: Every node to the server starting from the fifth to last started lagging massively
Second day: The second node on the NTT network after leaving my own ISP network lagged out at least twice as bad as the first day and this hit me a lot harder than the first day lag.
Today: Same as two days ago.
I'll just be glad it doesn't flat out disconnect me like some other people. Whatever the case may be my connection to the server is being disrupted solely on the NTT network. -
11-09-2017, 08:15 AMChandraNoctis
Level 3 is also reporting outages today.
-
11-09-2017, 08:34 AMKewitt
SE just replaced there old super boss "Duty Finder" with "Lag Spikes" to keep our gear in check as "Duty Finder" hasn't been an issue in a while....
Also These lag spikes wiped my Rabanastre party 3 times today. Something that wasn't an issue when the servers where in Canada. I never saw so many people having issues.
Is SE getting a DDOS attack or just the data centre? Please address this. -
11-09-2017, 09:16 AMRiko_FutatabiHi I've had connection issues since patch 4.06a.
It's been over 2 months that I've had these issues. My route to server, look at this awful mess! Ahahaha...
Code:|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| SkyRouter.Home - 0 | 125 | 125 | 0 | 0 | 2 | 0 |
| 97e7fe6a.skybroadband.com - 0 | 125 | 125 | 5 | 5 | 10 | 6 |
| be365.pr2.hobir.isp.sky.com - 0 | 125 | 125 | 16 | 17 | 20 | 18 |
| ae-3.r02.londen03.uk.bb.gin.ntt.net - 0 | 125 | 125 | 16 | 17 | 21 | 17 |
| ae-3.r24.londen12.uk.bb.gin.ntt.net - 0 | 125 | 125 | 16 | 16 | 25 | 17 |
| ae-5.r24.nycmny01.us.bb.gin.ntt.net - 34 | 54 | 36 | 82 | 82 | 87 | 83 |
| ae-2.r20.sttlwa01.us.bb.gin.ntt.net - 29 | 60 | 43 | 0 | 158 | 184 | 156 |
| ae-0.r21.sttlwa01.us.bb.gin.ntt.net - 44 | 46 | 26 | 0 | 154 | 161 | 154 |
| ae-3.r23.snjsca04.us.bb.gin.ntt.net - 0 | 125 | 125 | 170 | 171 | 180 | 171 |
| ae-45.r01.snjsca04.us.bb.gin.ntt.net - 0 | 125 | 125 | 171 | 171 | 174 | 171 |
| ae-1.r00.scrmca02.us.bb.gin.ntt.net - 0 | 125 | 125 | 169 | 169 | 172 | 170 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 0 | 125 | 125 | 169 | 169 | 172 | 169 |
| 204.2.229.234 - 18 | 76 | 63 | 174 | 175 | 179 | 179 |
| 204.2.229.10 - 0 | 125 | 125 | 172 | 173 | 175 | 173 |
|________________________________________________|______|______|______|______|______|______|
-
11-09-2017, 09:30 AMRiko_FutatabiSEs Data centers are the only ones that attack themselves.Quote:
Originally Posted by Kewitt
(Lol sorry, just being dumb because I'm tired, so tired. Time for bed.) -
11-09-2017, 09:36 AMBaingoleth
SE NA NOC said this:
http://forum.square-enix.com/ffxiv/t...=1#post4472965
From the various traceroutes I can find around the forums and with that NOC post we can fairly say that NTT is having trouble with DDOS attacks. The trouble with mitigating DDOS attacks is that they can be a moving target. You build an ACL to mitigate and the attacker changes tactics or moves to another IP block. Redundant links and multiple routes to the destination having trouble can help but again, the attacker might adjust. At least we know there is something that can explain some of trouble expressed in this thread. You can know for certain if you are affected by doing a traceroute when you are having trouble and seeing if you have high latency or lost packets at an NTT hop. I would imagine SE would like to get these DDOS issues cleared up and NTT would like to get these DDOS issues cleared up. It's bad for business when end users can't use the products and services for which they are paying.
Is everyone who posted trouble in this thread affected by these DDOS attacks? I don't know. No one in this thread has posted any network diagnostics with any evidence.
I hope your connection trouble clears up and you can get back to playing FFXIV and if you can provide a traceroute with any indication where your connection trouble is, some players who read these forums can help you make sense of it. I'm sure SE is watching this thread also. -
11-09-2017, 09:38 AMBaingolethOh, I see Riko_Futatabi posted his traceroute again. Yeah... That nycmny01 has been a problem for some time now...Quote:
Originally Posted by Riko_Futatabi
If it was the router, I'd expect it would be fixed by now. It makes me wonder if the problem is an impairment on the physical medium across the Atlantic. -
11-09-2017, 09:53 AMValkyrie_LennethAnd a couple of us got on the OP's ignore list for "not knowing what we are talking about and trolling" lol.Quote:
Originally Posted by Baingoleth
What do you know, ISP's having network issues. -
11-09-2017, 10:02 AMBaingolethTo make it more clear, SE informed us that their ISP is having issues.Quote:
Originally Posted by Valkyrie_Lenneth
And yeah, people are getting on the OP's ignore list seems a little overboard. I think that player is just getting really frustrated with the game trouble and unfortunately some posters are taking the brunt of his frustration. -
11-09-2017, 12:01 PMZarabeth
I've been having the same problem. I just go do something else. Hopefully it will get fixed soon.
-
11-09-2017, 02:12 PMKhanscott
Using Charter Spectrum, disconnects have been persistent for the past week or so. Was in a match, which I finished while this happened, of Dead by Daylight on a separate window and was in the Star Citizen PTU on my laptop when FFXIV d/ced. So my end is not the issue. (disclaimer: it has been on my end in the past, hence that "torture test" to remove all doubt)
-
11-09-2017, 03:24 PMreiichiUnfortunately, other services working fine doesn't mean your end of the connection is perfectly fine. It just means the paths to those game servers are not affected. They're likely not even hosted in one of the two USA NTT datacenters. I know it's tempting and even seems like it could be evidence for correlation, the Internet doesn't actually work that way.Quote:
Originally Posted by Khanscott
--
[to all]
Like Baingoleth and I keep advising, post a traceroute when you're having connection trouble. You can easily find an IP for your server on https://arrstatus.com which nicely shows the datacenter IPs. (No, ARR Status hiding them will not somehow lessen an attack. You can pull this information on your computer too.) To get a traceroute, open up the command line (cmd.exe) and type in "tracert IPHERE". Or if you're one of the few Mac users, "traceroute IPHERE" from the Terminal. -
11-09-2017, 10:24 PMeternalstar01
So, I did a traceroute and it looks like it's probably a mess on my end...
What do I do with this?
https://i.imgur.com/eu7sD5J.png -
11-10-2017, 12:15 AMClaviusnexYou can also execute a netstat -b command and look for ffxiv_dx11.exe in the results. The IP address of the server will be displayed in the foreign address column.Quote:
Originally Posted by reiichi
-
11-10-2017, 03:09 AMCylla
I don't blame the OP either with feeling frustrated. Three days been having this problem and today is the worst. Since getting on at 11am EST and it now 12:41PM... I've gotten 90k three times and a few handful of lag spikes. The game is unplayable at this point. I'm with TWC/Spectrum Fiber. 99% up time. Only ever had to call them out once due to a hardware issue. Can also say that playing other games like D3, Killer Instinct, WoW and anything in between I have not had lag or d/c issues. So yeah, I'm just as frustrated and wish I hadn't re-sub the day after it started.
-
11-10-2017, 05:15 AMreiichiFrom a traceroute perspective, that all looks pretty good. None of them timed out in the middle and a ping of 40-50ms is what most people would refer to as "extremely good." (While SE claims the game will work fine with 200ms and better, I'd probably still shoot for 150ms or lower myself for a smoother experience.)Quote:
Originally Posted by eternalstar01
It's probably safe to say that NTT is still getting DDoSed though, which can cause issues all around. I have an almost perfect route to the datacenter and yesterday was spotty here and there. -
11-10-2017, 10:42 AMBaingolethThat traceroute looks good except for 100ge10-2.core1.yvr1.he.net. 2 responses took 17ms and one response took 71ms. That's not terrible but not something I'd like to see so early in the route. That router belongs to Hurricane Electric, Inc.Quote:
Originally Posted by eternalstar01
A few questions. Did you run the traceroute at the time you were experiencing trouble? If you run the traceroute multiple times, is there always jitter like this on that hop? What if you do a "ping 184.105.64.113" a few times? Does the ping time vary a lot with that hop?
If all your traces keep coming up looking okay within the ntt.net hops, you aren't affected by this DDoS problem that people are reporting. -
11-11-2017, 12:33 AMeternalstar01Sadly not, I was logged out of the game when I ran it... Would have been a great idea to run it during a spike! Today seems to be a lot smoother. No spikes yet, even in a DF.Quote:
Originally Posted by Baingoleth
-
11-11-2017, 01:10 PMBaingoleth
I am experiencing this right now. There is an attack at ae-41.r02.snjsca04.us.bb.gin.ntt.net
Code:Tracing route to 204.2.229.88 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 2 ms 2 ms 10.252.10.1
3 16 ms 16 ms 16 ms 154.11.12.203
4 46 ms 48 ms 45 ms sea-b2-link.telia.net [213.248.74.220]
5 55 ms 57 ms 55 ms ntt-ic-327522-sea-b2.c.telia.net [80.239.195.59]
6 56 ms 55 ms 55 ms ae-9.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.117]
7 46 ms 46 ms 47 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
8 68 ms 69 ms 70 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
9 879 ms 851 ms 900 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
10 * 368 ms * ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
11 345 ms 93 ms 72 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
12 72 ms * 72 ms 204.2.229.234
13 72 ms 72 ms 72 ms 204.2.229.88
-
11-11-2017, 01:32 PMBaingoleth
Another NOC post about this:
http://forum.square-enix.com/ffxiv/t...8Nov.-10-11%29 -
11-11-2017, 01:48 PMBaingoleth
Just happened again. Same hop:
Code:Tracing route to 204.2.229.88 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.254
2 2 ms 2 ms 2 ms 10.252.10.1
3 17 ms 16 ms 16 ms 154.11.12.203
4 48 ms 45 ms 46 ms sea-b2-link.telia.net [213.248.74.220]
5 55 ms 55 ms 55 ms ntt-ic-327522-sea-b2.c.telia.net [80.239.195.59]
6 55 ms 55 ms 55 ms ae-9.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.117]
7 60 ms 46 ms 46 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
8 68 ms 68 ms 68 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
9 * * 907 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
10 * * * Request timed out.
11 73 ms 72 ms 72 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
12 * 72 ms 71 ms 204.2.229.234
13 72 ms 73 ms 76 ms 204.2.229.88