There is some major packet loss going on at NTT-GIN -- It is causing all sorts of lag and disconnects....
Code:|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 172.16.15.254 - 0 | 504 | 504 | 0 | 0 | 13 | 0 |
| 173-23-224-1.client.mchsi.com - 0 | 504 | 504 | 5 | 15 | 33 | 17 |
| 172.30.7.177 - 0 | 504 | 504 | 5 | 15 | 32 | 18 |
| 10.16.72.15 - 0 | 504 | 504 | 8 | 17 | 37 | 13 |
| 10.16.72.1 - 0 | 504 | 504 | 11 | 22 | 53 | 16 |
| 68-66-73-66.client.mchsi.com - 0 | 504 | 504 | 20 | 30 | 48 | 26 |
| po10.mplmn001er1.mchsi.com - 0 | 504 | 504 | 17 | 28 | 65 | 23 |
| mini-b2-link.ip.twelve99.net - 0 | 504 | 504 | 20 | 31 | 69 | 26 |
| chi-b23-link.ip.twelve99.net - 0 | 504 | 504 | 29 | 38 | 74 | 41 |
| ae-25.r08.chcgil09.us.bb.gin.ntt.net - 0 | 504 | 504 | 29 | 39 | 51 | 35 |
| ae-4.r23.chcgil09.us.bb.gin.ntt.net - 0 | 504 | 504 | 23 | 38 | 68 | 31 |
| ae-1.r24.snjsca04.us.bb.gin.ntt.net - 9 | 383 | 352 | 0 | 96 | 154 | 90 |
| ae-4.r00.scrmca02.us.bb.gin.ntt.net - 10 | 371 | 337 | 84 | 94 | 148 | 95 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 9 | 378 | 346 | 0 | 97 | 164 | 94 |
| 204.2.229.230 - 35 | 214 | 140 | 0 | 95 | 146 | 95 |
| 204.2.229.11 - 10 | 371 | 337 | 0 | 95 | 152 | 95 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Packet loss at gin NTT
Printable View
-
12-08-2021, 05:50 AMAmileahPacket loss at gin NTT
-
12-08-2021, 05:53 AMNightPortThis explains all the 90k errors people are getting now and confirms that these aren't related to the players internet but the servers connections. Hmm, though someone suggested that SE doesn't have a buffer for packet loss so even 1 lost packet is throwing 90k's at players.Quote:
Originally Posted by Amileah
-
12-08-2021, 06:01 AMAmileahI've been having them non stop today. Just had another 2002 during queue... Check the connection to the lobby and packet loss like crazy is happening again.Quote:
Originally Posted by NightPort
-
12-08-2021, 06:07 AMAmileah
I just sent an email to noc@gin.ntt.net with the tracert information and said they have an issue with packet loss in SNJSCA04 that is trickling down the line. *shrug* Out of our hands.
-
12-08-2021, 06:12 AMApeKingI'm amazed they responded at ALL. in the past all they have ever done is tell you to piss of if you are not a customer. Now the REAL question is will they do something about it?Quote:
Originally Posted by Amileah
-
12-08-2021, 06:16 AMAmileahOh no, they haven't responded lol the auto ticket system responded. I said to them that they had an issue with packet loss and where it was... maybe they'll take it more serious with the data, or maybe they'll tell me to piss off :3Quote:
Originally Posted by ApeKing
-
12-08-2021, 06:18 AMApeKingWell they are at least being open about being aware of it D:Quote:
Originally Posted by Amileah
-
12-08-2021, 06:19 AMMaraStormblade
Thanks for posting this, I've been getting 90006 errors and 30-60 second lag spikes all day.
-
12-08-2021, 06:24 AMAmileahThey actually did reply to me... also the packet loss has died down quite a bit.Quote:
Originally Posted by ApeKing
-
12-08-2021, 06:25 AMAmileahNot a problem! I suggest grabbing WinMTR and running a test to your DC Lobby. Yours would be neolobby02.ffxiv.com :)Quote:
Originally Posted by MaraStormblade
-
12-08-2021, 07:06 AMNightPortI think it has picked up again. Got on and was on for a good 30 minutes, got 90k'd, then 3001'd, then have sat at position 161 in que for the last 45 minutes. Seems like these issues will get better or worse as the load fluctuates. Though I am surprised they responded to you as well. Still, it's unlikely they will do much or say anything else to you.Quote:
Originally Posted by Amileah
-
12-08-2021, 07:17 AMrenachi
I posted a thread about this a few days ago https://forum.square-enix.com/ffxiv/...-s-own-network
I ran traces from various locations using a VPN, the only hop that was consistent and also consistently bad was 204.2.229.230.
Starting from different locations sends you through various NTT.net servers, while seeing loss on their servers was common, it was about 90% of the traces on hitting 204.2.229.230
So that might be an issue with NTT.net's connection to 204.2.229.230. As it appears NTT.net is the internet provider for the lobby server, hopefully SE is already working with them to get the issue fixed -
12-08-2021, 07:53 AMAngellos
Means this isn't the first time it's happened either. This was happening to me about 2-3 weeks ago non-stop all day for a few days in a row. They need to get their stuff together and hopefully keep it that way -_-
-
12-08-2021, 08:27 AMPhaylis
I work for an ISP so good traces are exactly what we need to identify issues on the network. And sending the email to NTT was smart. He could also sent in those to Mediacom as well. Its way pass the egress point in Minneapolis but sometime ISPs have agreements with other carriers and are willing to look into issues if they are a partner.
-
12-08-2021, 09:21 AMtechnole
I've been getting logged off more than twice today. Did the traceroute and it's definitely NTT's SNJSCA04 being a bugger. NTT hosts the NA data centers in Sacramento, so it's really in their hands.
-
12-08-2021, 09:22 AMDevourn
What the? Do they use duct tape and bubblegum to hold their network together? They constantly have problems. eyeroll.
-
12-08-2021, 09:26 AMAnnabellechuI've had those 2 mostly so it includes the same one as you:Quote:
Originally Posted by technole
ae-2.r23.chcgil09.us.bb.gin.ntt.net
ae-1.r24.snjsca04.us.bb.gin.ntt.net -
12-08-2021, 02:30 PMtechnoleQuote:
Originally Posted by Annabellechu
I contacted NTT NoC and they got back to me and was very kind. Traced through Dallas hub to snjsca04 and didn't see anymore packet loss on their network so it seemed like that's smoothed out now, they also believe the SE lobby server could be throttling causing the loss % at that final hop IP you mention. Definitely was much smoother this evening. Hopefully the maintenance on the lobby server tonight will help.Quote:
Originally Posted by renachi
-
12-08-2021, 11:33 PMAmileahMediacom shrugged it off as not their problem because it was outside their network by the time packet loss occurred. That is kind of what I figured from them though. I have the business support info and I could talk to them but I don't want to clog up business lines for a viddiya game :p especially when its my home having issues and not my business.Quote:
Originally Posted by Phaylis
Update --NTT-GIN did also see packet loss, they are actively monitoring it. -
12-11-2021, 04:31 AMAnnabellechu
More packet loss from snjsca04 today and I got some yesterday. What's the best route to contact them?
-
12-11-2021, 06:17 AMPsythe
Yeah this afternoon the snjsca04 hop is losing around 12% of its packets. For almost 3 hours. This morning around 2AM pacific time it was averaging 9% loss for over an hour. The last hop before the DC has been crazy with 40 - 65% loss whatever device that is(load balancer, gateway, whatever). There is at least 4 threads with network tests across the first couple of pages. All of them showing that SE should be all over their DC and/or Network providers behinds because there is no way that is within acceptable SLA. SE already has an issue with things they can not do much about but this is what that could alleviate a large group of issues with connectivity that is not related to the Queue service.
I ran tests from servers all over the globe (6 locations). I have access servers across multiple DC's and along with the various 3rd party remote testing tools all of them have shown the same issue.