[ PC users NA / EU ] Post your traceroutes in prime times and non-prime times!

[Sovjohn]

Dear all,

After making a quite comprehensive post on the server / network lag thread (and to be honest I believe that a combination of factors is to blame, this includes network lag for people using congested links), I thought it'd be nice to collect some data to prove to SE that their bandwidth links can get congested.

Here are the instructions, meant to actually keep this test simple:

1) Find your server's IP from http://www.arrstatus.com/ (Hover over a server to find its IP)

2) From Windows, open up a command prompt (Use Run or search for cmd if you can't find it), and then type up the command:

tracert <server IP>

Where <server IP> is the complete IP of your server, no <> brackets or anything else. Example, for Balmung: tracert 199.91.189.30

3) Once the traceroute runs, save the results (You can use right click--->Mark and copy them in default Windows CMD)

4) Collect two sets of results - One for "prime time" in your area and one in a dead time (in the morning, after midnight, your choice, but a time when people aren't playing that much).

5) Paste results here, labeling them first for prime time or non-prime time to differentiate.

6) Compare your networking performance with other people from / to SE's NA/ EU datacenter.

7) Hopefully, apply more pressure to SE to -also- fix their networking providers issues, apart from any other underlying netcode issues.

I go first:

Non-prime time (23:50 BST - 01:50 EET)
Tracing route to 199.91.189.25 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  dsldevice.lan [192.168.1.1]
  2    25 ms    24 ms    24 ms  bbras-llu-kln-15L500.forthnet.gr [213.16.246.12]

  3    25 ms    24 ms    25 ms  213.16.247.73
  4    28 ms    28 ms    26 ms  core-kln-12Be3.forthnet.gr [213.16.247.17]
  5   25 ms   27 ms   28 ms  te-3-2.car1.Sofia2.Level3.net [212.162.46.109]
  6   65 ms    68 ms    65 ms  4.69.141.109
  7    71 ms    76 ms    73 ms  ae-10-10.ebr3.Frankfurt1.Level3.net [4.69.141.34]
  8    66 ms    66 ms    66 ms  ae-73-73.csw2.Frankfurt1.Level3.net [4.69.163.6]
  9    66 ms    66 ms    65 ms  ae-2-70.edge4.Frankfurt1.Level3.net [4.69.154.72]
 10    77 ms    78 ms    78 ms  4.68.111.146
 11   157 ms   156 ms   157 ms  if-7-2.tcore1.FNM-Frankfurt.as6453.net [195.219.50.2]
 12   156 ms   155 ms   156 ms  if-5-2.tcore1.AV2-Amsterdam.as6453.net [195.219.194.13]
 13   163 ms   160 ms   159 ms  if-2-2.tcore2.AV2-Amsterdam.as6453.net [195.219.194.6]
 14   173 ms   171 ms   172 ms  if-7-2.tcore2.L78-London.as6453.net [80.231.152.14]
 15   158 ms   159 ms   158 ms  if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
 16   156 ms   157 ms   155 ms  if-2-2.tcore2.MTT-Montreal.as6453.net [64.86.226.13]
 17   158 ms   158 ms   166 ms  if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
 18   159 ms   161 ms   157 ms  if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
 19   164 ms   164 ms   163 ms  66.198.96.50
 20   166 ms   166 ms   170 ms  192.34.76.2
 21   182 ms   183 ms   183 ms  199.91.189.234
 22   166 ms   165 ms   165 ms  199.91.189.25

Trace complete.

Prime time (19:00 BST - 21:00 EET)
 1     1 ms     2 ms     1 ms  192.168.1.1
  2    23 ms    22 ms    22 ms  bbras-llu-kln-15L500.forthnet.gr [213.16.246.12]

  3    23 ms    22 ms    22 ms  213.16.247.73
  4    25 ms    23 ms    23 ms  core-kln-12Be3.forthnet.gr [213.16.247.17]
  5    33 ms    35 ms    33 ms  te-3-2.car1.Sofia2.Level3.net [212.162.46.109]
  6    63 ms    63 ms    62 ms   4.69.141.109
  7    63 ms    67 ms    74 ms  ae-10-10.ebr3.Frankfurt1.Level3.net [4.69.141.34]
  8    64 ms    63 ms    63 ms  ae-93-93.csw4.Frankfurt1.Level3.net [4.69.163.14]
  9    64 ms    63 ms    63 ms  ae-4-90.edge4.Frankfurt1.Level3.net [4.69.154.200]
 10    62 ms    61 ms    62 ms  4.68.111.146
 11   158 ms   158 ms   159 ms  if-4-2.tcore1.PVU-Paris.as6453.net [80.231.153.10]
 12   298 ms   306 ms   319 ms  if-2-2.tcore1.PYE-Paris.as6453.net [80.231.154.18]
 13   332 ms   328 ms   325 ms  if-5-2.tcore1.L78-London.as6453.net [80.231.130.1]
 14   333 ms   316 ms   338 ms  if-1-2.tcore2.L78-London.as6453.net [80.231.130.122]
 15   314 ms   305 ms   303 ms  if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
 16   325 ms   328 ms   345 ms  if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.30]
 17   332 ms   315 ms   308 ms  if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
 18   315 ms   329 ms   342 ms  if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
 19   319 ms   324 ms   317 ms  66.198.96.50
 20   336 ms   327 ms   316 ms  192.34.76.2
 21   316 ms   312 ms   305 ms  199.91.189.234
 22   322 ms   318 ms   321 ms  199.91.189.25

[shikarin]

I'll just say that I agree there is likely some kind of congestion happening somewhere between the client and the dc. But that is something that may or may not be in SE's control.

[whilke]

I'll just say that I agree there is likely some kind of congestion happening somewhere between the client and the dc. But that is something that may or may not be in SE's control.

Any company running a AAA MMO is absolutely in control of a good chunk of their general network path. They choose which backbones to peer from, how many, and how. They can then make sure that specific internet segments route through specific paths that they want.

Unless the issue is somewhere in your local ISP, or their uplink if they are a small carrier, SE should have some control over it.

[Misaky]

i doubt this thread will help on anything, SE is just dam greedy.
They only care about the Japanese market, the rest of the world is just extra money to earn with the minimal effort possible.