What is the point of the new NA servers and NA DC maintenance?

[hunkygladiator]

If it's going to lag like hell and have constant ping spikes felt by everyone in the instance?

Is this a server downgrade or what?

[Atelier-Bagur]

dont know what you're talking about, because on my end the game is running fine.




and I play this on windowed mode mind you, which would affect performance.

[hunkygladiator]

dont know what you're talking about, because on my end the game is running fine.




and I play this on windowed mode mind you, which would affect performance.

https://forum.square-enix.com/ffxiv/...ince-patch-6.3

EVERYTHING ON MY END IS FINE SO IT IS FINE FOR EVERYONE

[Atelier-Bagur]

https://forum.square-enix.com/ffxiv/...ince-patch-6.3

EVERYTHING ON MY END IS FINE SO IT IS FINE FOR EVERYONE

You're linking me a thread that was made during the beginning of the year and not made during the previous month when they replaced the servers. Also how do you explain me not getting lag spikes if this were a total server issue then? Is the server somehow giving me and probably many others, special treatment to not run like butt or something?

[hunkygladiator]

Is the server somehow giving me and probably many others, special treatment to not run like butt or something?

Genius, please think hard about all the times Facebook, Google, Twitter, Reddit etc. partially go down and the respective companies come out and say they're fixing the problem when 90% of people can still access it.

This is literally "Welcome to crappy NA ISPs: the thread."


People really don't understand two facts.
1: How the internet works
2: How bad the infrastructure in the US is

The issue is at Square's end lmao. Look at the traceroutes.

SE support on this is a joke. I've been having this issue since roughly 6.38 as well and its murdering any possibility of ultimate prog because the game becomes a slide show in the middle of our raid times.

I have two internet lines (separate ISP's) and generally could get around latency issues by switching to the other outbound connection, but now the issue is inside NTT's network and SE claims they can't do anything about it and I need my ISP to fix the routes.



If the whois data isn't lying (and it rarely is for tier providers) NTT owns the server IP's all the way back to that dallas hop. Neither of my ISP's have control over this. Nor this



Even tooling output wasn't enough to sway them that its an NTT issue:

|---------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                      |
|                       Host               -   %  |  Sent |  Recv | Best | Avrg | Wrst | Last |
|-------------------------------------------------|-------|-------|------|------|------|------|
|                      leaving my network -     0 | 11513 | 11513 |    0 |    0 |    7 |    0 |
|                            ISP network  -     0 | 11513 | 11513 |    0 |    0 |   29 |    1 |
|                            ISP network -      0 | 11513 | 11513 |    2 |    2 |    7 |    2 |
|                     Leaving ISP network -     0 | 11513 | 11513 |    7 |   11 |   31 |   13 |
|     ae-5.a00.dllstx14.us.bb.gin.ntt.net -     1 | 11509 | 11508 |    7 |   33 |   95 |   26 |
|     ae-2.r20.dllstx14.us.bb.gin.ntt.net -    29 | 5427  | 3885  |    0 |   33 |   81 |   18 |
|     ae-2.r24.lsanca07.us.bb.gin.ntt.net -     5 | 9712  | 9242  |   31 |   52 | 1906 |   37 | <- according to SE, this is my ISP's issue
|     ae-5.a01.scrmca03.us.bb.gin.ntt.net -     1 | 11388 | 11355 |   41 |   62 |  168 |   41 | <- these as well
|     ae-1.a00.scrmca03.us.bb.gin.ntt.net -     1 | 11402 | 11373 |   41 |   60 |  170 |   41 | <-|
|xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net -    1 | 11419 | 11394 |   41 |   57 |  100 |   41 | <-|
|                            204.2.29.241 -    79 | 2794  |  593  |    0 |   57 |   97 |   41 | <-|
|                             204.2.29.86 -     1 | 11422 | 11398 |   41 |   56 |   94 |   42 |
|_________________________________________________|_______|_______|______|______|______|______|

No sir, that is clearly my ISP, and not just one of my ISP's, BOTH of them.

[Valkyrie_Lenneth]

Genius, please think hard about all the times Facebook, Google, Twitter, Reddit etc. partially go down and the respective companies come out and say they're fixing the problem when 90% of people can still access it.



The issue is at Square's end lmao. Look at the traceroutes.

Square doesn't own NTT. Only the last two hops are SE's network. The rest is NTT. Which has issues. Before NTT, we had Level3 issues in the last hop before heading into Montreal, CA. Everyone has forgotten the Level3 memes, but it was the same back then.



Whether or not you will have latency issues in XIV is heavily dependent on which ISP you have and where you are located. There are people in Sacramento playing who have had far more issues with packet loss than I have, in the Seattle area. My ping to the server is almost always 25, except when my roommates are using all the bandwidth. I have only rarely had disconnect issues, and that's when Ziply is having problems, or the actual servers themselves are. I'm not saying there aren't issues for people. I'm saying 99% of the time its not who they they it is.


NA ISPs are literal dogcrap, because they have no incentive to provide good routing for consumers, and no incentives to upgrade their decades old infrastructure that wasn't meant for low latency gaming.



It functions for web browsing, as that doesn't care about dropped packets, same as video streaming, because of buffering, and that's all most consumers care about.

[Valkyrie_Lenneth]

https://forum.square-enix.com/ffxiv/...ince-patch-6.3

EVERYTHING ON MY END IS FINE SO IT IS FINE FOR EVERYONE

This is literally "Welcome to crappy NA ISPs: the thread."


People really don't understand two facts.
1: How the internet works
2: How bad the infrastructure in the US is

[hunkygladiator]

and I play this on windowed mode mind you, which would affect performance.

I also play on a bit of a potato PC so I know that's going to happen now and then.

Lmao you guys don't even know the difference between lag due to graphics and lag due to networking.

[TaleraRistain]

Lmao you guys don't even know the difference between lag due to graphics and lag due to networking.

Whatever you want to believe. I do know the difference. And I mention playing on a potato PC because my point is that occasional lag of either sort isn't something new so I don't usually bother running something like a traceroute to confirm the actual cause. I just chalk it up to sometimes I get some lag, either network related or performance related. And some of those people are describing their client freezing up which is something that can also happen with performance related issues. But I don't experience it to the level of those in that thread. And I read through trying to see if there were patterns or commonalities that could be identified that could explain why they experience that but people like Atelier and I playing on the same servers don't.

[TaleraRistain]

I'd never deny others were having issue. I can't say I've experienced the level described in the thread linked, though. I do get the occasional packet loss and slight input lag but nothing that makes the game unplayable. I also play on a bit of a potato PC so I know that's going to happen now and then.