Square, your NA/EU data centre has serious issues...

[Istym]

...because I can play fine on JP server.

So yeah must be my ISP or equipment or or or or

LOL-worthy

So um please advise?

[Raist]

Run a trace to your world server, and lookup the details on the IP's where the trace derails. Pretty confident you will find it is either Cogent, i-Web, or TATA at fault--- not SE. Need to be in contact with your ISP to see if they can help resolve your routing issues.

[Istym]

No no no been there done that max hop i ever saw was 110ms.

[Istym]

199.91.189.74

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 1 ms 3 ms 2 ms <removed>
2 21 ms 27 ms 23 ms sr11.enncl.isp.sky.com []
3 25 ms 32 ms 29 ms 02780812.bb.sky.com [2.120.8.18]
4 29 ms 31 ms 32 ms ip-84-38-37-94.easynet.co.uk [84.38.37.94]
5 29 ms 28 ms 27 ms ae3.lon10.ip4.tinet.net [77.67.74.93]
6 114 ms 146 ms 105 ms xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125]
7 105 ms 105 ms 107 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
8 110 ms 106 ms 107 ms 192.34.76.2
9 106 ms 105 ms 105 ms 199.91.189.234
10 131 ms 105 ms 110 ms 199.91.189.74

Trace complete.

tracert 199.91.189.21

Tracing route to 199.91.189.21 over a maximum of 30 hops

1 4 ms 5 ms 3 ms
2 15 ms 23 ms 15 ms sr11.enncl.isp.sky.com []
3 34 ms 33 ms 29 ms 02780812.bb.sky.com [2.120.8.18]
4 27 ms 27 ms 31 ms ip-84-38-37-96.easynet.co.uk [84.38.37.96]
5 29 ms 57 ms 43 ms ae3.lon10.ip4.tinet.net [77.67.74.93]
6 105 ms 114 ms 141 ms xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125]
7 108 ms 109 ms 109 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
8 111 ms 111 ms 113 ms 192.34.76.2
9 105 ms 106 ms 107 ms 199.91.189.234
10 133 ms 107 ms 109 ms 199.91.189.21

Trace complete.

tracert 204.62.14.156

Tracing route to 204-62-14-156.static.6sync.net [204.62.14.156]
over a maximum of 30 hops:

1 6 ms 1 ms 2 ms
2 20 ms 17 ms 24 ms sr11.enncl.isp.sky.com []
3 35 ms 29 ms 34 ms 02780812.bb.sky.com [2.120.8.18]
4 32 ms 27 ms 32 ms te0-1-0-5.er10.thlon.ov.easynet.net [89.200.134.
127]
5 26 ms 24 ms 27 ms 195.50.122.113
6 97 ms 98 ms 95 ms vl-3606-ve-230.csw2.London1.Level3.net [4.69.166
.22]
7 94 ms 95 ms 94 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]

8 93 ms 96 ms 99 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

9 99 ms 96 ms 93 ms ae-2-2.ebr1.Newark1.Level3.net [4.69.132.98]
10 93 ms 94 ms 96 ms ae-12-51.car2.Newark1.Level3.net [4.69.156.6]
11 98 ms 92 ms 103 ms GIGLINX-INC.car2.Newark1.Level3.net [4.28.188.13
0]
12 95 ms 98 ms 98 ms 204-62-14-156.static.6sync.net [204.62.14.156]

Trace complete.

Although its currently off peak, again tracing whatever IP's Netstat shows I do not see any of the entries you mention, nor do I when I run this during peak times and the hop times do not increase overly much during peak times.

What I do see however is a company that actually stopped selling their product (digital sales) because their servers could not cope, and I see a situation where by their servers still cannot cope.

Its not rocket science as much as some may try make it so.

Also how many of these tracert reports are lying around the forums with peoples actual IPs left in them. Could that be a contributing factor with all the stolen accounts we are seeing spamming RMT links like its open season.

[Istym]

And here are the outputs from tracert during peak time.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Istym>tracert 199.91.189.21

Tracing route to 199.91.189.21 over a maximum of 30 hops

1 2 ms 4 ms 1 ms
2 16 ms 15 ms 16 ms sr11.enncl.isp.sky.com []
3 27 ms 36 ms 27 ms 02780812.bb.sky.com [2.120.8.18]
4 33 ms 43 ms 34 ms ip-84-38-37-96.easynet.co.uk [84.38.37.96]
5 37 ms 31 ms 28 ms ae3.lon10.ip4.tinet.net [77.67.74.93]
6 111 ms 138 ms 105 ms xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125]
7 105 ms 113 ms 105 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
8 106 ms 104 ms 109 ms 192.34.76.2
9 106 ms 106 ms 112 ms 199.91.189.234
10 106 ms 109 ms 180 ms 199.91.189.21

Trace complete.

tracert 204.62.14.156

Tracing route to 204-62-14-156.static.6sync.net [204.62.14.156]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms
2 18 ms 15 ms 16 ms sr11.enncl.isp.sky.com []
3 28 ms 41 ms 28 ms 02780812.bb.sky.com [2.120.8.18]
4 29 ms 31 ms 31 ms te0-1-0-5.er10.thlon.ov.easynet.net [89.200.134.
127]
5 * 30 ms 23 ms 195.50.122.113
6 93 ms 101 ms 98 ms vl-3606-ve-230.csw2.London1.Level3.net [4.69.166
.22]
7 93 ms 94 ms 92 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]

8 96 ms 93 ms 92 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

9 95 ms 99 ms 93 ms ae-2-2.ebr1.Newark1.Level3.net [4.69.132.98]
10 98 ms 97 ms 104 ms ae-12-51.car2.Newark1.Level3.net [4.69.156.6]
11 101 ms 94 ms 102 ms GIGLINX-INC.car2.Newark1.Level3.net [4.28.188.13
0]
12 93 ms 97 ms 92 ms 204-62-14-156.static.6sync.net [204.62.14.156]

Trace complete.

tracert 199.91.189.74

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 2 ms 1 ms 1 ms
2 24 ms 15 ms 15 ms sr11.enncl.isp.sky.com []
3 34 ms 31 ms 31 ms 02780812.bb.sky.com [2.120.8.18]
4 25 ms 31 ms 31 ms ip-84-38-37-94.easynet.co.uk [84.38.37.94]
5 28 ms 28 ms 29 ms ae3.lon10.ip4.tinet.net [77.67.74.93]
6 105 ms 105 ms 105 ms xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125]
7 104 ms 106 ms 105 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
8 105 ms 105 ms 105 ms 192.34.76.2
9 105 ms 107 ms 105 ms 199.91.189.234
10 108 ms 106 ms 106 ms 199.91.189.74

Trace complete.

So as you can see your theories are incorrect and the issues I have are due to the Square Enix server quality @ its EU/NA datacentre.

[Raist]

did you not notice you are getting intermittent time outs in your trace? Also the marked variances in your delays?

These are the signs people have been making note of in the other threads. Each trace you run is a snapshot at a fixed point in time--after taking multiple snapshots, you can start to see certain sections of your routing is unstable. For instance, take a closer look at what is going on when you come around easynet and into tinet. You sometimes experience a marked increase in typical delay, and in one of your sessions you actually experienced a time out. If more samples were taken, you may see more of this behavior occur--possibly in the same spots, maybe at other points.

[Istym]

Yada yada yada post your SE employee number and be done with it

[Raist]

I'm employed by Honda.

Again, you don't seem to be getting the point. You are looking at only a few isolated points of time. And even though it is a limited sample set, in one of those runs a potential issue is clearly marked in your trace. For whatever reason, you just aren't seeing it.

[Istym]

Your jumping on every minute detail and using that to deflect attention from the true issue here. All I am seeing is either a shill, or a fan boy spending a mega amount of time running around the forums defending SE.

Also since maintainence this morning everything has been fine.

So the issue I was having up until this point were down 100% to SE as they obv fixed some issue they were having with their data centre this morning.

GTFO my thread ^^

[worldofneil]

GTFO my thread ^^

SE don't reply to threads on this Technical Support forum, the only people that do are other players, like him. If you don't want these players to post their replies then I'm afraid you're going to get no replies at all.

Unless you're only saying you don't want replies that you don't agree with?