Lag Spikes only 6pm-12am EST every day since 2.1

[Eijii]

I'm currently been having issues with my connection since patch 2.1 that makes endgame unplayable. I have checked my computer for Viruses and Malware, checked my cables, reset my router, checked my Ping with SE's NA Data center, checked my connection, eliminated some backround applications... did a ipconfig /flushdns... you name it. I even called my ISP(Verizon Fios) and went through nearly an hour or two of troubleshooting. I would like to mention also that past midnight EST my connection is 100% perfect up until around 5pm EST.. then the game becomes unplayable. I'm thinking this has to with SE's server and the latest updates they have done. I'm going to call SE on Monday but if anyone has found a solution if they have experienced this let me know.

[Raist]

It's likely the same as everyone else... increased congestion/loss at hops in between.

Run some traces or pathpings to the Canadian IP your client is using (the one starting with 199) and you may see signs of the slow down in the same corridors as everyone else has noted in all the other threads about lag.

[Runsell]

Me and my wife are having the exact issue as Eijii and we are from Sargatanas too. I did the exact procedures Eijii used and I called my ISP. They told me that my line and connection are excellent.

[Eijii]

Yeah, I'm convinced that it's on Square Enix's side but they haven't even said anything about it.. when tons of people are having this issue..

[Darthenron]

Open command prompt and do tracert and then your server ip from http://arrstatus.com/. I made a thread and posted my traceroutes and basically anything that had level3 in its name had huge delays like 50-70ms. I figure if people start posting their traceroutes they can see where things are going wrong and hopefully will speed up the repair process.

[Runsell]

This is early in the morning in which I don't have any issues:

C:\Windows\System32>tracert 199.91.189.23

Tracing route to 199.91.189.23 over a maximum of 30 hops


6 7 ms 9 ms 9 ms 213.140.51.249
7 31 ms 31 ms 31 ms Te0-6-0-0-grtmiabr6.red.telefonica-wholesale.net
[84.16.13.149]
8 51 ms 50 ms 50 ms Xe6-1-4-0-grtwaseq6.red.telefonica-wholesale.net
[84.16.12.45]
9 121 ms 114 ms 115 ms 213.140.53.106
10 116 ms 121 ms 117 ms be2113.mpd21.dca01.atlas.cogentco.com [10]
11 117 ms 118 ms 120 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
12 124 ms 124 ms 124 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.
50]
13 75 ms 76 ms 76 ms 38.122.42.34
14 76 ms 134 ms 75 ms 192.34.76.10
15 81 ms 75 ms 76 ms 199.91.189.242
16 75 ms 76 ms 75 ms 199.91.189.23

----------------------------------------------------------------------------------------------------------------------------------
This is after 6pm where things get nasty:

C:\Windows\System32>tracert 199.91.189.23

Tracing route to 199.91.189.23 over a maximum of 30 hops


6 32 ms 33 ms 8 ms 213.140.51.249
7 67 ms 34 ms 260 ms Te0-6-0-0-grtmiabr6.red.telefonica-wholesale.net
[84.16.13.149]
8 135 ms 109 ms 148 ms Xe6-1-4-0-grtwaseq6.red.telefonica-wholesale.net
[84.16.12.45]
9 184 ms 192 ms 165 ms 213.140.53.106
10 170 ms 177 ms 314 ms be2176.ccr21.dca01.atlas.cogentco.com [154.54.41
.54]
11 244 ms 196 ms 191 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
12 * 241 ms 193 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.
50]
13 145 ms 160 ms 117 ms 38.122.42.34
14 102 ms 168 ms 157 ms 192.34.76.10
15 100 ms 80 ms 105 ms 199.91.189.242
16 113 ms 138 ms 99 ms 199.91.189.23

-------------------------------------------------------------------------------------------------------------------------------

When I do a ping test from CMD when thing are really bad I get packet drops and high pings around 800 - 1500ms.

[Rivienne]

Yeah, I'm convinced that it's on Square Enix's side but they haven't even said anything about it.. when tons of people are having this issue..

I do not believe it is on SE's side but on the NA Data Center ISP side, which is outside of SE's direct control (though they should investigate and talk to the ISP to solve it). I noticed this problem the first time on the 27th. Not on patch day. In fact I did not see this problem on the 24th when I was part of a relic group from Hydra through Titan. Starting later that week however I have been unable to do Garuda, Titan, or any of the harder content past 5pm EST, and I even have trouble with Chim, Hydra and Ifrit sometimes.

My current suspicion is that the problem lies in whatever the ISP did on the 26th during maintenance.

[Eijii]

Yeah, the data centers but here are my results.... i'm pretty sure it's perfect right now tho.. the issue starts after 5pm EST till Midnight...

Tracing route to 199.91.189.33 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 3 ms 3 ms L100.NYCMNY-VFTTP-222.verizon-gni.net [108.46.149.1]
3 7 ms 7 ms 7 ms 10.127.36.144
4 5 ms 5 ms 5 ms so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.199.12]
5 6 ms 5 ms 5 ms 0.xe-11-1-0.BR1.NYC1.ALTER.NET [152.63.4.237]
6 6 ms 5 ms 5 ms ae11.edge2.NewYork.Level3.net [4.68.62.41]
7 14 ms 14 ms 15 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 15 ms 15 ms 15 ms ae-46-46.ebr2.NewYork1.Level3.net [4.69.201.29]

9 15 ms 14 ms 14 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
10 14 ms 14 ms 13 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

11 14 ms 14 ms 14 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
12 20 ms 20 ms 19 ms 192.34.76.10
13 21 ms 19 ms 19 ms 199.91.189.242
14 21 ms 20 ms 19 ms 199.91.189.33

Trace complete.

@8:13 PM EST where i'm lagg skipping A LOT!

Tracing route to 199.91.183.33 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.NYCMNY-VFTTP-222.verizon-gni.net [108.46.149.1]
3 10 ms 10 ms 7 ms 10.127.36.144
4 5 ms 6 ms 5 ms ae2-0.NY5030-BB-RTR2.verizon-gni.net [130.81.199.170]
5 6 ms 10 ms 5 ms 0.xe-1-1-1.BR2.NYC4.ALTER.NET [152.63.23.169]
6 * 123 ms 124 ms 204.255.168.26
7 25 ms 72 ms 23 ms xe-0-1-0.cr1.lga5.us.above.net [64.125.27.62]
8 34 ms 33 ms 33 ms ae6.cr1.ord2.us.above.net [64.125.24.34]
9 124 ms 71 ms 74 ms xe-5-2-1.mpr1.msp1.us.above.net [64.125.20.77]
10 45 ms 45 ms 45 ms te3-2.btb-border76.lz.above.net [208.184.53.226]

11 55 ms 55 ms 55 ms 199.91.183.33

Trace complete.




I'll try again when it gets nasty but what is the link to your post so I can post there as well? I also did a ping test to the data center and it was Avg= 33ms.

[Raist]

In most every case reported here the last 3 months (outside of when an ISP in the UK uncovered and worked with SE to resolve a problem found in the packet headers), it's been tied into packet losses/delays on the segments managed by your ISP's routing partner. In the above traces, that would be Cogent Communications (cogentco) and Level3.

Your ISP purchases access to their routes to carry your data from their local segments to Ormuco's (SE's ISP). Your best move would be to forward the trace data to your ISP and request that tier3 or higher support investigate the matter further. This is an issue between your ISP and their routing partner, which is done in an effort to provide you with internet service--putting it more squarely in your ISP's court than SE's.

[Runsell]

I used battleping yesterday and the lag was almost none (just a few lag spike). I noticed that my ISP put my traffic to spain then return to the US. I live in Puerto Rico so I used New York server with battleping and the game was somehow much better. I am going to do some test today later in the night, not using any battleping server to see how it goes. If I get so much lag I will rapidly will connect to battleping to see the final results.

Raist, I work in networking configuring CISCO routers and switches. I don't work in a Tier 3 department but I do know how it works since the tier 3 department in the company I work is next to mine.
How should I approach when I call my ISP??, Should I just call them and tell them that I need a change in the routing??