atlas.cogentco.com servers and bad reouting cause lagspikes

Those servers, and bad routing in the USA cause all the problems we can read of lag spikes and delay between client and server (AOES lag and many others)

if you try to write on google atlas.cogentco.com LAG you will found THOUNSAND of post of various games where this chap and shoddy server company have caused very many lag issue in all the EU and North America area.

i dont get why a serious company like square enix goes to savings money on servers giving a so bad and low quality service to his players.

to made a soultion they have made a data center, that only refresh more often the location of player, a simple and useless solution 2 try one more time save money intese of get decent servers.

5 months are passed, where square enix promise and promise and promise, and never did nothing 2 improve the situation.

its an obvious say that the EUROPEAN SERVER ARE IN THE AMERICA???!?!?!?!?!?! THA FAQ?

also if this is the reason nr 1 for the lag issues of the europeans, cogentco.com made almost lag all North America player, also ppl with 100 mega optical fiber connection... that's sadly creazy my friends..... situation can not go on like that

also cogentco.com, blames AT&T, one for the 4 biggest ISP company of the USA in an endless blaming circle without an exit.

this situation with cogentco is knowed on all the most famous mmos, evreyone who pass from their servers, ALWAYS ALWAYS AND ALWAYS got lag spikes costantly making the game UNPALAYBE.

the point i really dunt get is:

square enix before made decision 2 go with cogentco they should know what lind company they are, they have a buisiness staff for this kind of choises and bla bla bla, so:

why i normal player know all those things about cogentco issues and got scared only by hear their name?, and squarenix choose for routing with them their servers? they are so stingy that want kidding us all like the worst idiots?

1 1 ms <1 ms <1 ms WL309 [192.168.0.1]
2 51 ms 97 ms 99 ms dsldevice.lan [192.168.1.254]
3 24 ms 24 ms 24 ms 10.245.142.1
4 23 ms 24 ms 23 ms 10.2.102.18
5 25 ms 24 ms 24 ms 10.251.47.201
6 24 ms 24 ms 24 ms 10.251.42.23
7 24 ms 23 ms 24 ms 10.251.43.1
8 24 ms 24 ms 24 ms 10.247.124.209
9 24 ms 23 ms 24 ms 10.251.47.194
10 24 ms 24 ms 24 ms 10.2.6.49
11 24 ms 24 ms 24 ms 10.254.0.250
12 25 ms 24 ms 24 ms 10.254.12.25
13 25 ms 24 ms 25 ms 93-63-100-129.ip27.fastwebnet.it [93.63.100.129]

14 25 ms 24 ms 24 ms 93-63-100-170.ip27.fastwebnet.it [93.63.100.170]

15 25 ms 24 ms 24 ms 89.96.200.110
16 25 ms 25 ms 25 ms te8-7.ccr01.mil01.atlas.cogentco.com [149.6.152.
209]
17 29 ms 30 ms 29 ms te0-0-0-12.ccr21.zrh01.atlas.cogentco.com [154.5
4.62.10]
18 35 ms 35 ms 35 ms be2023.ccr21.muc01.atlas.cogentco.com [130.117.0
.249]
19 40 ms 40 ms 40 ms be2228.ccr21.fra03.atlas.cogentco.com [154.54.38
.49]
20 47 ms 47 ms 46 ms be2261.ccr21.ams03.atlas.cogentco.com [154.54.37
.29]
21 56 ms 57 ms 57 ms be2182.ccr21.lpl01.atlas.cogentco.com [154.54.77
.246]
22 127 ms 126 ms 129 ms be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44
.137]
23 128 ms 126 ms 128 ms 38.122.42.34
24 135 ms 135 ms 134 ms 192.34.76.10
25 138 ms 137 ms 138 ms 199.91.189.242
26 135 ms 134 ms 134 ms 199.91.189.42

Those are tecnical data that made the game UNPLAYABE.

i will stop refresh my monthly subscription because the service for what i pay is a............ bettter if i dont express my self.

I don't even know where to start with this. About the only legitimate point you brought up was the location of the EU servers, as that's about the only thing SE actually has direct control over.

If it helps

My issue doesn't seem to be latency so much as packets being dropped.

Tracing route to 199.91.189.30 over a maximum of 30 hops

0 COMPUTERXXXX.md.comcast.net. [10.0.0.4]
1 10.0.0.1
2 c-98-231-152-1.hsd1.md.comcast.net [98.231.152.1]
3 xe-0-2-0-32767-sur01.rockville.md.bad.comcast.net [68.85.138.225]
4 68.86.204.185
5 he-3-3-0-0-10-cr01.newyork.ny.ibone.comcast.net [68.86.94.61]
6 ae12.edge1.NewYork2.level3.net [4.68.127.1]
7 vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 ae-47-47.ebr2.NewYork1.Level3.net [4.69.201.33]
9 ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
10 ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
11 ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
12 192.34.76.10
13 199.91.189.242
14 199.91.189.30

Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 COMPUTERXXXX.md.comcast.net. [10.0
.0.4]
0/ 100 = 0% |
1 8ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 27ms 0/ 100 = 0% 0/ 100 = 0% c-98-231-152-1.hsd1.md.comcast.net
[98.231.152.1]
0/ 100 = 0% |
3 33ms 1/ 100 = 1% 1/ 100 = 1% xe-0-2-0-32767-sur01.rockville.md.
bad.comcast.net [68.85.138.225]
0/ 100 = 0% |
4 26ms 1/ 100 = 1% 1/ 100 = 1% 68.86.204.185
0/ 100 = 0% |
5 32ms 0/ 100 = 0% 0/ 100 = 0% he-3-3-0-0-10-cr01.newyork.ny.ibon
e.comcast.net [68.86.94.61]
0/ 100 = 0% |
6 38ms 0/ 100 = 0% 0/ 100 = 0% ae12.edge1.NewYork2.level3.net [4.
68.127.1]
0/ 100 = 0% |
7 35ms 0/ 100 = 0% 0/ 100 = 0% vlan52.ebr2.NewYork2.Level3.net [4
.69.138.254]
0/ 100 = 0% |
8 29ms 0/ 100 = 0% 0/ 100 = 0% ae-47-47.ebr2.NewYork1.Level3.net
[4.69.201.33]
1/ 100 = 1% |
9 65ms 2/ 100 = 2% 1/ 100 = 1% ae-5-5.car1.Montreal2.Level3.net [
4.69.141.5]
0/ 100 = 0% |
10 61ms 2/ 100 = 2% 1/ 100 = 1% ae-11-11.car2.Montreal2.Level3.net
[4.69.141.1]
0/ 100 = 0% |
11 38ms 2/ 100 = 2% 1/ 100 = 1% ORMUCO-COMM.car2.Montreal2.Level3.
net [4.59.178.74]
0/ 100 = 0% |
12 39ms 2/ 100 = 2% 1/ 100 = 1% 192.34.76.10
0/ 100 = 0% |
13 52ms 1/ 100 = 1% 0/ 100 = 0% 199.91.189.242
1/ 100 = 1% |
14 41ms 2/ 100 = 2% 0/ 100 = 0% 199.91.189.30

Barking up the wrong tree. SE isn't using Cogent Communications.... they use Ormuco. Your ISP has agreements with Cogent to carry their subscribers data across North America.

Now, if your traces are also showing issues in the Ormuco segments, SE may be able to assist there--but that is about as far as they can go to rectify it. Only other thing they can do is address issues with how the ISP's are identifying their packets. O2 found an issue with their packets that was preventing them from being identified properly... never did hear whether SE addressed that or not. Outside of addressing such concerns once they are identifed by an ISP or bringing up congestion issues with their provider (again, Ormuco and not Cogent), there isn't much SE can do to address an issue that is found with your ISP or your ISP's partners, unless they contact SE for information to assist them with the problems they found (like O2 did about 2 months back).

So basically, if you are only seeing issues on your ISP or their partner's segments (ie: Cogentco)--you need to be working with your ISP.

Just tried Titan EX and lag was aweful. It's the same issue from back in October all over again ;_;

Code:

|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | Wireless_Broadband_Router.home - 0 | 1504 | 1504 | 0 | 0 | 2 | 0 | | L100.BLTMMD-VFTTP-52.verizon-gni.net - 0 | 1504 | 1504 | 4 | 7 | 94 | 7 | | G0-7-2-4.BLTMMD-LCR-21.verizon-gni.net - 1 | 1500 | 1499 | 5 | 9 | 28 | 9 | | so-1-1-0-0.RES-BB-RTR1.verizon-gni.net - 0 | 1504 | 1504 | 7 | 14 | 103 | 9 | | 0.xe-2-0-1.BR1.IAD8.ALTER.NET - 3 | 1377 | 1345 | 0 | 10 | 67 | 9 | | ae17.edge1.washingtondc12.level3.net - 2 | 1403 | 1377 | 0 | 37 | 98 | 34 | |vl-3602-ve-226.ebr2.Washington12.Level3.net - 1 | 1493 | 1490 | 30 | 38 | 52 | 40 | | 4.69.201.61 - 1 | 1500 | 1499 | 31 | 39 | 49 | 39 | | ae-81-81.csw3.NewYork1.Level3.net - 1 | 1500 | 1499 | 30 | 39 | 56 | 40 | | ae-82-82.ebr2.NewYork1.Level3.net - 0 | 1504 | 1504 | 31 | 39 | 50 | 41 | | ae-5-5.car1.Montreal2.Level3.net - 0 | 1504 | 1504 | 32 | 65 | 454 | 36 | | ae-11-11.car2.Montreal2.Level3.net - 13 | 993 | 865 | 20 | 39 | 242 | 22 | | ORMUCO-COMM.car2.Montreal2.Level3.net - 0 | 1504 | 1504 | 33 | 40 | 51 | 39 | | 192.34.76.10 - 3 | 1359 | 1322 | 35 | 43 | 139 | 40 | | 199.91.189.242 - 3 | 1357 | 1320 | 35 | 39 | 88 | 38 | | 199.91.189.25 - 3 | 1353 | 1315 | 35 | 39 | 49 | 38 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.

- Furlamseere