RunUO Community

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Upcoming changes... RunUO and UOGamers - ROUND2

Which location do you prefer?


  • Total voters
    161

Eskeshehir

Knight
As much as i would love pinging 30 in seattle...

I have to pick something thats mutually beneficial to everyone.

I'm voting chicago, because its as about dead centered in the middle of the murrica, and impacts my east coast/european/south american friends the least of the options.


You all should ask your friends where they live/and to ping these servers.

Dont pick whats closest to you, pick whats best for everyone, remember you play this game with hundreds of other kids as well.
 

hulryung

Sorceror
Dallas: 74.86.116.210 15 hops 161ms
Houston: 173.193.70.98 16 hops 170ms
San Jose: 50.23.64.58 15 hops 140ms
Washington DC: 208.43.102.250 17 hops 191ms
Seattle: 67.228.112.250 13 hops 122ms
Chicago: 64.250.112.1 15 hops 269ms

hops are counted with traceroute exclude my private router.

Chicago is worst choice for Asian. haha. As I wrote, I hope this nightmare to end soon.


C:\Users\john>tracert -d 74.86.116.210

Tracing route to 74.86.116.210 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 3 ms 2 ms 2 ms [deleted]
3 2 ms 2 ms 2 ms [deleted]
4 2 ms 3 ms 2 ms 61.78.48.106
5 1 ms <1 ms <1 ms 112.190.178.113
6 3 ms 2 ms 2 ms 112.190.174.13
7 10 ms 7 ms 7 ms 112.174.16.125
8 7 ms 7 ms 6 ms 112.174.81.58
9 7 ms 6 ms 7 ms 112.174.83.202
10 121 ms 121 ms 122 ms 112.174.87.126
11 120 ms 120 ms 120 ms 206.81.80.140
12 147 ms 148 ms 147 ms 173.192.18.145
13 161 ms 162 ms 161 ms 173.192.18.138
14 161 ms 161 ms 162 ms 173.192.18.255
15 161 ms 160 ms 162 ms 66.228.118.186
16 161 ms 161 ms 161 ms 74.86.116.210

Trace complete.

C:\Users\john>tracert -d 173.193.70.98

Tracing route to 173.193.70.98 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms [deleted]
3 2 ms 2 ms 2 ms [deleted]
4 2 ms 2 ms 3 ms 61.78.48.106
5 1 ms 3 ms 2 ms 112.190.178.113
6 1 ms 3 ms 3 ms 112.190.174.185
7 8 ms 6 ms 6 ms 112.174.16.105
8 6 ms 6 ms 7 ms 112.174.81.138
9 7 ms 6 ms 7 ms 112.174.83.202
10 121 ms 121 ms 120 ms 112.174.87.126
11 119 ms 119 ms 120 ms 206.81.80.140
12 161 ms 146 ms 146 ms 173.192.18.145
13 162 ms 161 ms 161 ms 173.192.18.138
14 170 ms 170 ms 170 ms 173.192.18.221
15 168 ms 168 ms 167 ms 50.97.18.247
16 169 ms 169 ms 168 ms 173.193.118.133
17 170 ms 170 ms 171 ms 173.193.70.98

Trace complete.

C:\Users\john>tracert -d 50.23.64.58

Tracing route to 50.23.64.58 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms [deleted]
3 3 ms 3 ms 2 ms [deleted]
4 2 ms 2 ms 2 ms 61.78.48.106
5 1 ms 2 ms 2 ms 112.190.178.113
6 3 ms 2 ms 2 ms 112.190.175.185
7 7 ms 6 ms 6 ms 112.174.56.141
8 6 ms 6 ms 7 ms 112.174.82.230
9 7 ms 6 ms 6 ms 112.174.84.202
10 121 ms 121 ms 121 ms 112.174.87.122
11 120 ms 122 ms 120 ms 206.81.80.140
12 120 ms 122 ms 121 ms 173.192.18.187
13 138 ms 139 ms 139 ms 173.192.18.147
14 139 ms 154 ms 138 ms 173.192.18.249
15 149 ms 139 ms 158 ms 50.23.118.131
16 140 ms 139 ms 141 ms 50.23.64.58

Trace complete.

C:\Users\john>tracert -d 208.43.102.250

Tracing route to 208.43.102.250 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 3 ms 2 ms 2 ms [deleted]
3 2 ms 3 ms 2 ms [deleted]
4 3 ms 2 ms 2 ms 61.78.48.106
5 73 ms 46 ms 36 ms 112.190.178.113
6 3 ms 2 ms 3 ms 112.190.175.185
7 7 ms 8 ms 6 ms 112.174.56.105
8 6 ms 7 ms 7 ms 112.174.82.134
9 6 ms 6 ms 7 ms 112.174.84.34
10 121 ms 122 ms 121 ms 112.174.87.126
11 120 ms 120 ms 120 ms 206.81.80.140
12 156 ms 148 ms 147 ms 173.192.18.145
13 148 ms 147 ms 147 ms 173.192.18.169
14 173 ms 173 ms 172 ms 173.192.18.130
15 189 ms 189 ms 190 ms 173.192.18.154
16 201 ms 190 ms 191 ms 173.192.18.193
17 190 ms 191 ms 191 ms 208.43.118.134
18 193 ms 191 ms 191 ms 208.43.102.250

Trace complete.

C:\Users\john>tracert -d 67.228.112.250

Tracing route to 67.228.112.250 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 3 ms 2 ms 2 ms [deleted]
3 3 ms 3 ms 3 ms [deleted]
4 2 ms 3 ms 2 ms 61.78.48.106
5 2 ms 2 ms 2 ms 112.190.178.113
6 120 ms 21 ms 37 ms 112.190.175.245
7 9 ms 7 ms 6 ms 112.174.56.165
8 7 ms 12 ms 7 ms 112.174.82.130
9 6 ms 6 ms 6 ms 112.174.84.34
10 121 ms 121 ms 121 ms 112.174.87.126
11 120 ms 121 ms 121 ms 206.81.80.140
12 122 ms 121 ms 121 ms 173.192.18.199
13 122 ms 123 ms 122 ms 67.228.118.134
14 122 ms 120 ms 122 ms 67.228.112.250

Trace complete.

C:\Users\john>tracert -d 64.250.112.1

Tracing route to 64.250.112.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 3 ms 2 ms 2 ms [deleted]
3 3 ms 2 ms 2 ms [deleted]
4 1 ms 3 ms 2 ms 61.78.48.106
5 1 ms 3 ms 2 ms 112.190.176.113
6 2 ms 2 ms 2 ms 112.190.175.9
7 8 ms 7 ms 6 ms 112.174.56.69
8 7 ms 6 ms 7 ms 112.174.82.54
9 6 ms 6 ms 7 ms 112.174.84.38
10 177 ms 177 ms 176 ms 112.174.88.246
11 190 ms 189 ms 206 ms 198.32.176.13
12 217 ms 218 ms 218 ms 69.22.143.165
13 229 ms 228 ms 228 ms 69.22.142.6
14 * 270 ms 270 ms 69.31.111.150
15 229 ms 229 ms 229 ms 69.31.105.62
16 269 ms 269 ms 269 ms 64.250.112.1

Trace complete.
 

Ryan

RunUO Founder
Staff member
Dallas: 74.86.116.210 15 hops 161ms
Houston: 173.193.70.98 16 hops 170ms
San Jose: 50.23.64.58 15 hops 140ms
Washington DC: 208.43.102.250 17 hops 191ms
Seattle: 67.228.112.250 13 hops 122ms
Chicago: 64.250.112.1 15 hops 269ms

Interestingly enough - I ran a test going BACK toward you.

Our current location is 23 hops with pretty high jitter.

Chicago is 16 hops with next to no jitter.
 

hulryung

Sorceror
Interestingly enough - I ran a test going BACK toward you.

Our current location is 23 hops with pretty high jitter.

Chicago is 16 hops with next to no jitter.


Yes. you're right. let me show you traceroute result to current servers.
hops and ping delay to login server is 21, 190ms
hops and ping delay to login2 server is 14, 218ms (this result shows why did I keep requested to support shard selection feature in Sallos)
If you would like to make alternate network interface like login2, how about to change sallos or sallos server as well?

Code:
C:\Users\john>tracert -d login.uogamers.com
 
Tracing route to login.uogamers.com [8.26.59.200]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    3 ms    2 ms    3 ms  [deleted]
  3    3 ms    3 ms    3 ms  [deleted]
  4    2 ms    2 ms    2 ms  61.78.48.106
  5    10 ms    1 ms    2 ms  112.190.178.113
  6    2 ms    2 ms    2 ms  112.190.175.17
  7    8 ms    7 ms    8 ms  112.174.56.165
  8    7 ms    6 ms    7 ms  112.174.82.230
  9    7 ms    6 ms    7 ms  112.174.84.202
10  133 ms  133 ms  132 ms  112.174.87.106
11  135 ms  137 ms  135 ms  4.28.172.25
12  146 ms  145 ms  147 ms  4.69.152.62
13  134 ms  134 ms  134 ms  4.69.153.17
14  174 ms  175 ms  174 ms  4.69.132.58
15  190 ms  185 ms  188 ms  4.69.151.182
16  199 ms  199 ms  199 ms  4.69.132.62
17  183 ms  190 ms  182 ms  4.69.140.189
18  182 ms  189 ms  182 ms  4.69.151.178
19  249 ms  189 ms  190 ms  4.69.136.213
20  191 ms  190 ms  190 ms  4.69.132.205
21  189 ms  187 ms  188 ms  4.53.64.46
22  191 ms  190 ms  190 ms  8.26.59.200
 
Trace complete.
 
C:\Users\john>tracert -d login2.uogamers.com
 
Tracing route to login2.uogamers.com [209.173.138.20]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    2 ms    2 ms    2 ms  [deleted]
  3    2 ms    2 ms    2 ms  [deleted]
  4    2 ms    2 ms    2 ms  61.78.48.106
  5    1 ms    1 ms    2 ms  112.190.178.113
  6    2 ms    1 ms    2 ms  112.190.174.21
  7    9 ms    11 ms    11 ms  112.174.16.145
  8    6 ms    6 ms    7 ms  112.174.81.58
  9    7 ms    6 ms    6 ms  112.174.83.206
10  151 ms  150 ms  151 ms  112.174.88.186
11  176 ms  175 ms  176 ms  66.192.252.41
12  202 ms  204 ms  203 ms  66.192.244.202
13  212 ms  204 ms  203 ms  207.250.147.226
14  205 ms  205 ms  204 ms  209.173.129.46
15  218 ms  217 ms  218 ms  209.173.138.20
 
Trace complete.
 
C:\Users\john>
 

ickyfloyd

Squire
Ping statistics for 64.250.112.1:
Packets: Sent = 127, Received = 127, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 39ms, Average = 20ms

oh hello chicago :)
 
Dallas: 53
Houston: 61
San Jose: 30
DC: 90 - usually in actual game 125+
Seattle: 15
Chicago: 66ish


I voted for San Jose because that was the best ping for the Asian community. Even the Aussies don't ping good in Chicago. Dallas from what I read in this thread isn't good for them and they have the highest population (Asians). My second pick would be Texas as it's central as well and has better ping then chicago.

It sounds like you already made up your mind, though.
66 is better then 90 - 125+
 

Ryan

RunUO Founder
Staff member
Dallas: 53
Houston: 61
San Jose: 30
DC: 90 - usually in actual game 125+
Seattle: 15
Chicago: 66ish


I voted for San Jose because that was the best ping for the Asian community. Even the Aussies don't ping good in Chicago. Dallas from what I read in this thread isn't good for them and they have the highest population (Asians). My second pick would be Texas as it's central as well and has better ping then chicago.

It sounds like you already made up your mind, though.
66 is better then 90 - 125+

Current Location:

traceroute to simon, 30 hops max, 60 byte packets
1 ip8-26-59-1.cvg.myftn.net (8.26.59.1) 0.150 ms 0.138 ms 0.129 ms
2 ge-6-2-100.car1.Cincinnati1.Level3.net (4.53.64.45) 0.593 ms 0.655 ms 0.767 ms
3 ae-2-5.bar1.Cincinnati1.Level3.net (4.69.132.206) 0.701 ms 0.712 ms 0.734 ms
4 ae-10-10.ebr2.Chicago1.Level3.net (4.69.136.214) 9.215 ms 14.041 ms 14.037 ms
5 ae-5-5.ebr2.Chicago2.Level3.net (4.69.140.194) 7.431 ms 7.484 ms 6.956 ms
6 4.69.158.233 (4.69.158.233) 6.852 ms 4.69.158.237 (4.69.158.237) 6.888 ms 6.909 ms
7 COMCAST-IP.edge1.Chicago2.Level3.net (4.71.248.38) 10.367 ms COMCAST-IP.edge1.Chicago2.Level3.net (4.71.248.70) 10.221 ms COMCAST-IP.edge1.Chicago2.Level3.net (4.71.248.22) 10.288 ms
8 pos-1-14-0-0-cr01.denver.co.ibone.comcast.net (68.86.85.118) 36.332 ms 36.330 ms 36.318 ms
9 pos-0-13-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.86.214) 61.073 ms 60.633 ms 60.643 ms
10 so-1-1-0-0-ar03.troutdale.or.bverton.comcast.net (68.86.95.94) 61.613 ms 61.728 ms 61.722 ms
11 be-3-ur10.beaverton.or.bverton.comcast.net (68.85.243.166) 62.943 ms 63.139 ms 63.284 ms
12 te-3-0-0-ten09.beaverton.or.bverton.comcast.net (68.85.149.26) 63.175 ms 63.169 ms 63.198 ms


New Location:

traceroute to simon, 30 hops max, 60 byte packets
1 64.250.113.225 (64.250.113.225) 0.380 ms 0.373 ms 0.396 ms
2 64.250.112.141 (64.250.112.141) 1.202 ms 1.191 ms 1.194 ms
3 xe-1-0-5-1208.ar2.ord1.us.nlayer.net (69.31.105.61) 5.942 ms 5.824 ms 5.901 ms
4 ae3.ar1.ord1.us.nlayer.net (69.31.111.243) 2.886 ms 2.875 ms 2.862 ms
5 173.167.57.125 (173.167.57.125) 2.447 ms 2.442 ms 2.422 ms
6 be-11-cr01.350ecermak.il.ibone.comcast.net (68.86.84.101) 4.963 ms 4.115 ms 4.089 ms
7 pos-1-5-0-0-cr01.chicago.il.ibone.comcast.net (68.86.88.37) 4.668 ms 4.663 ms 4.643 ms
8 pos-1-12-0-0-cr01.denver.co.ibone.comcast.net (68.86.85.250) 29.513 ms 29.562 ms 29.570 ms
9 pos-0-14-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.85.209) 53.576 ms 53.567 ms 53.554 ms
10 so-6-0-0-0-ar03.troutdale.or.bverton.comcast.net (68.86.95.98) 56.963 ms 55.690 ms 57.364 ms
11 be-3-ur10.beaverton.or.bverton.comcast.net (68.85.243.166) 57.655 ms 57.354 ms 57.663 ms
12 te-3-0-0-ten09.beaverton.or.bverton.comcast.net (68.85.149.26) 58.451 ms 57.202 ms 57.100 ms
 
I've never had 63 ms in game for the current location, it's always 100+ Maybe you just have a better internet. Comcast here sucks in that regard. Unless I mistook the ping results.

I can live with 57 ping, of course assume the ping isn't based on your super fast internet compared to mine who always drops packets. 10 dropped packets in 10 places on the route which is typical for the internet around here for some reason. It even drops packets on the first hop station. Both of mine posted 64-66 ping btw on my trace route.


I was just thinking of the Asian's who will be boned from what one of them posted on the results.

C:\Users\Name>tracert 64.250.112.1

Tracing route to 64.250.112.1 over a maximum of 30 hops

1 * 1 ms * 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * 11 ms 9 ms ae-3-0-ar03.troutdale.or.bverton.comcast.net [68
.85.243.165]
6 16 ms 18 ms * pos-2-2-0-0-cr01.seattle.wa.ibone.comcast.net [6
8.86.95.97]
7 44 ms 44 ms 42 ms pos-0-6-0-0-cr01.denver.co.ibone.comcast.net [68
.86.87.49]
8 * 66 ms * pos-0-12-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.85.249]
9 * 68 ms 71 ms pos-1-14-0-0-cr01.350ecermak.il.ibone.comcast.ne
t [68.86.88.22]
10 * * 936 ms be-12-pe03.350ecermak.il.ibone.comcast.net [68.8
6.84.190]
11 66 ms * 66 ms 173.167.57.126
12 67 ms 75 ms 67 ms ae7.ar2.ord1.us.nlayer.net [69.31.111.242]
13 69 ms 66 ms 67 ms as23367.xe-1-0-5-1208.ar2.ord1.us.nlayer.net [69
.31.105.62]
14 * 64 ms * 0001-13-cs01.net.genesisadaptive.net [64.250.112
.1]
15 66 ms 66 ms * 0001-13-cs01.net.genesisadaptive.net [64.250.112
.1]
16 66 ms 65 ms 65 ms 0001-13-cs01.net.genesisadaptive.net [64.250.112
.1]

Trace complete.

C:\Users\Name>tracert 64.250.112.1

Tracing route to 0001-13-cs01.net.genesisadaptive.net [64.250.112.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 14 ms 8 ms te-0-1-0-0-ur09.beaverton.or.bverton.comcast.net
[68.85.149.17]
4 * 8 ms 11 ms be-1-ur10.beaverton.or.bverton.comcast.net [68.8
5.243.162]
5 13 ms 10 ms 10 ms ae-3-0-ar03.troutdale.or.bverton.comcast.net [68
.85.243.165]
6 16 ms 15 ms 18 ms pos-2-0-0-0-cr01.seattle.wa.ibone.comcast.net [6
8.86.95.89]
7 * 44 ms 40 ms pos-0-6-0-0-cr01.denver.co.ibone.comcast.net [68
.86.87.49]
8 66 ms 67 ms 67 ms pos-0-12-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.85.249]
9 73 ms 71 ms 71 ms pos-1-14-0-0-cr01.350ecermak.il.ibone.comcast.ne
t [68.86.88.22]
10 65 ms 64 ms 65 ms be-12-pe03.350ecermak.il.ibone.comcast.net [68.8
6.84.190]
11 65 ms * 68 ms 173.167.57.126
12 * 66 ms * ae7.ar2.ord1.us.nlayer.net [69.31.111.242]
13 * 65 ms 65 ms as23367.xe-1-0-5-1208.ar2.ord1.us.nlayer.net [69
.31.105.62]
14 66 ms * 64 ms 0001-13-cs01.net.genesisadaptive.net [64.250.112
.1]

Trace complete.
 

Ryan

RunUO Founder
Staff member
Dropped packets in route do not matter... it's destination dropped packets that matter.

Carriers deprioritize ICMP which will cause that.
 
Ok.

Thanks for explaining it. I just hope we don't lose the Aussies and Asians. I know I'll get good ping. Oh and it's good to see you on the forums again. I haven't talked to you or seen ya since Revelations.
 
Top