SE NTT Router Issue

[Zephanoa]

I am experiencing issues as of this post with lag. The issue is on NTT's end. Please open an incident with your ISP to resolve this issue.


4 15 ms 17 ms 11 ms po-116-rur202.burien.wa.seattle.comcast.net [68.87.205.217]
5 17 ms 16 ms 13 ms be-221-ar01.seattle.wa.seattle.comcast.net [69.139.162.53]
6 14 ms 18 ms 12 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
7 15 ms 13 ms 19 ms be-10847-pe02.seattle.wa.ibone.comcast.net [68.86.86.226]
8 166 ms 151 ms 131 ms ae-31.a00.sttlwa01.us.bb.gin.ntt.net [129.250.66.149]
9 138 ms 130 ms 130 ms ae-9.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.117]
10 127 ms 130 ms 127 ms ae-5.r23.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
11 185 ms * 83 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
12 * 162 ms 161 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
13 164 ms 147 ms 152 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 101 ms 111 ms 106 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 114 ms * * 204.2.229.234
16 131 ms 130 ms 140 ms 204.2.229.10


Ping for the time frame as of this post. Started just before I posted:
Reply from 204.2.229.10: bytes=32 time=157ms TTL=51
Reply from 204.2.229.10: bytes=32 time=155ms TTL=51
Request timed out.
Reply from 204.2.229.10: bytes=32 time=154ms TTL=51
Reply from 204.2.229.10: bytes=32 time=155ms TTL=51
Reply from 204.2.229.10: bytes=32 time=155ms TTL=51
Reply from 204.2.229.10: bytes=32 time=152ms TTL=51
Reply from 204.2.229.10: bytes=32 time=148ms TTL=51
Reply from 204.2.229.10: bytes=32 time=170ms TTL=51
Request timed out.
Reply from 204.2.229.10: bytes=32 time=158ms TTL=51
Reply from 204.2.229.10: bytes=32 time=159ms TTL=51
Reply from 204.2.229.10: bytes=32 time=158ms TTL=51
Reply from 204.2.229.10: bytes=32 time=146ms TTL=51
Reply from 204.2.229.10: bytes=32 time=150ms TTL=51
Reply from 204.2.229.10: bytes=32 time=147ms TTL=51
Reply from 204.2.229.10: bytes=32 time=164ms TTL=51
Reply from 204.2.229.10: bytes=32 time=162ms TTL=51
Reply from 204.2.229.10: bytes=32 time=163ms TTL=51
Reply from 204.2.229.10: bytes=32 time=157ms TTL=51
Reply from 204.2.229.10: bytes=32 time=190ms TTL=51
Request timed out.
Reply from 204.2.229.10: bytes=32 time=160ms TTL=51
Reply from 204.2.229.10: bytes=32 time=159ms TTL=51
Reply from 204.2.229.10: bytes=32 time=162ms TTL=51
Reply from 204.2.229.10: bytes=32 time=167ms TTL=51
Reply from 204.2.229.10: bytes=32 time=193ms TTL=51

Just to list out troubleshooting:
Turning on/off firewall
Forwarding ip/ports
Moving from router to modem direct
Changing DNS servers
Making sure no av was on
Rebooting
Refreshing isp ip
All did not fix the issue.

[Zephanoa]

This is from a related post found here: http://forum.square-enix.com/ffxiv/t...ag-disconnects

SNIP

Essentially this, very well put (better than I could word). Once our ISP reaches NTT's network it is completely out of the control of our ISP. This is why I frequently mention San Jose's routers being the issue. Once we reach our first NTT router it is up to that router configuration to determine where to go next and not the ISP.

Using Kerwin's and my hops: http://forum.square-enix.com/ffxiv/t...T-Router-Issue here is what I believe is going on in steps:

1. You to ISP
2. ISP to NTT
3. NTT Routes to nearest NTT WAN Router Junction to Data Center (San Jose Routers Labeled *.SNJSCA04.*)
4. Lag or flooded connectivity occurs at the NTT WAN Routers/Load-balancers at SNJSCA04 junction causing connections to drop or be delayed.
-> Could be a bad configuration of load balancing (Config issue).
-> Could be that the total allotted broadband spectrum at NTT is full on hardware, or is Soft capped.
-> Could be a DOS attack, or a DOS issue caused by heavy activity at specific times.
5. San Jose routes to physical DC that SE's NA servers reside. (Sacramento routers labeled *.SCRMCA02.*)
6. Sacramento routers route to SE's physical/virtual hardware at 204.2.229.X

Using the above deduction. We can surmise that SE is indeed right, its not the data center; but it is a choke point at the routers (that NTT owns) short ways up stream.

[Zephanoa]

Just to confirm this occurred again this afternoon at roughly 5:30 PDT in which the ping reached 150ms average and the choke point was at NTT routers. This lasted for about 45ish minutes before returning to normal.

[Zephanoa]

The issues occurred today at the same time. Also, I used a VPN service to connect to San Jose through a different route and had the same issues at the same time. I feel like this proves that it is -not- a home user ISP issue and an SE issue. I will keep continuing to update this post until SE acknowledges the problem.

[Zephanoa]

3rd forum post I have commented on that has linked data to this post. This is magical. http://forum.square-enix.com/ffxiv/t...s-of-5-17-2018


Speaking of, why hasn't this post been commented on yet by support staff? Its going on a week now without a response.