Shard Move

[MadeInQuebec]

I don't know, but if I look at these results: http://startping.com/ping/login.uodemise.com/54b5606c8c3dcfc116a2db16

It all looks pretty darn good overall for all over the world. Except South Korea, they don't like Demise...

I'm not sure how reliable this website is, but is sure looks similar to what Ryan was claiming earlier.

 

[Ryan]

The server we're using to monitor from Brazil is 177.52.130.97 (It's in Sao Paulo).

We will be providing a login2.uodemise.com hopefully later today which will use internap for it's traffic - hopefully it will route better.

Regards,
Ryan

 

[Diz]

My pings gone down from average 45-50 to average 35-40, and the server actually moved farther away from me than it was previously.

So I'd say whatever Ryan and co. did, they did it right.

 

[Ryan]

Technically speaking all traffic that went to us, routed through Chicago anyway, we took out the physical distance of Chicago -> Indianapolis, IN -> Cincinnati, OH

 

[LendariuM]

C:\Users\Administrator>ping 177.52.130.97 -t
Pinging 177.52.130.97 with 32 bytes of data:
Reply from 177.52.130.97: bytes=32 time=24ms TTL=54
Reply from 177.52.130.97: bytes=32 time=23ms TTL=54
Reply from 177.52.130.97: bytes=32 time=25ms TTL=54
Reply from 177.52.130.97: bytes=32 time=22ms TTL=54
Reply from 177.52.130.97: bytes=32 time=26ms TTL=54
Reply from 177.52.130.97: bytes=32 time=26ms TTL=54
Reply from 177.52.130.97: bytes=32 time=29ms TTL=54
Reply from 177.52.130.97: bytes=32 time=23ms TTL=54
Reply from 177.52.130.97: bytes=32 time=22ms TTL=54
Ping statistics for 177.52.130.97:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 29ms, Average = 24ms

 

[Escaravelho]

Microsoft Windows [versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.

C:\>ping 177.52.130.97 -t
Disparando 177.52.130.97 com 32 bytes de dados:
Resposta de 177.52.130.97: bytes=32 tempo=26ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=27ms TTL=52
Resposta de 177.52.130.97: bytes=32 tempo=27ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=31ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=26ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=30ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=24ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=29ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=23ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=30ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=52
Resposta de 177.52.130.97: bytes=32 tempo=29ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=23ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=27ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=27ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=22ms TTL=52
Resposta de 177.52.130.97: bytes=32 tempo=30ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=24ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=27ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=34ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=25ms TTL=52
Resposta de 177.52.130.97: bytes=32 tempo=21ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=35ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=30ms TTL=52
Resposta de 177.52.130.97: bytes=32 tempo=26ms TTL=52
Resposta de 177.52.130.97: bytes=32 tempo=27ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=28ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=30ms TTL=53
Resposta de 177.52.130.97: bytes=32 tempo=26ms TTL=53

 

[Ryan]

Neither of those pings really help

if you could do a pathping login.uodemise.com, it would help though.

 

[LendariuM]

LOGIN:

C:\Users\Administrator>tracert login.uodemise.com
Tracing route to login.uodemise.com [104.128.48.66]
over a maximum of 30 hops:
1 9 ms 11 ms 18 ms bfbeaa01.virtua.com.br [191.190.170.1]
2 10 ms 11 ms 40 ms c937e864.virtua.com.br [201.55.232.100]
3 108 ms 103 ms 18 ms embratel-T0-2-0-0-tacc01.cas.embratel.net.br [200.174.243.5]
4 134 ms 127 ms 127 ms 200.230.231.198
5 131 ms 137 ms 131 ms ebt-BP11942-intl04.mianap.embratel.net.br [200.230.220.10]
6 147 ms 163 ms 157 ms ip67-94-116-69.z116-94-67.customer.algx.net [67.94.116.69]
7 178 ms 173 ms 164 ms 207.88.14.153.ptr.us.xo.net [207.88.14.153]
8 175 ms 175 ms 175 ms te-3-2-0.rar3.atlanta-ga.us.xo.net [207.88.12.5]
9 161 ms 163 ms 167 ms te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
10 172 ms 170 ms 171 ms ae0d0.mcr2.chicago-il.us.xo.net [216.156.0.166]
11 174 ms 175 ms 251 ms ae1d0.mcr1.chicago-il.us.xo.net [216.156.1.81]
12 169 ms 170 ms 167 ms te-4-3.er1.Chi1.Servernap.net [66.252.3.168]
13 162 ms 163 ms 159 ms po-13.csr1.Chi3.Servernap.net [66.252.0.65]
14 159 ms 171 ms 159 ms te-9-1.ddr4.Chi3.Servernap.net [66.252.0.161]
15 * * * Request timed out.
16 181 ms 179 ms 179 ms 104.128.48.66
Trace complete.



LOGIN2:

Tracing route to login2.uodemise.com [104.128.48.66]
over a maximum of 30 hops:
1 13 ms 11 ms 12 ms bfbeaa01.virtua.com.br [191.190.170.1]
2 26 ms 41 ms 12 ms c937e864.virtua.com.br [201.55.232.100]
3 13 ms 26 ms 31 ms embratel-T0-2-0-0-tacc01.cas.embratel.net.br [200.174.243.5]
4 148 ms 133 ms 133 ms 200.230.231.198
5 130 ms 130 ms 128 ms ebt-BP11942-intl04.mianap.embratel.net.br [200.230.220.10]
6 143 ms 143 ms 152 ms ip67-94-116-69.z116-94-67.customer.algx.net [67.94.116.69]
7 165 ms 163 ms 180 ms 207.88.14.153.ptr.us.xo.net [207.88.14.153]
8 175 ms 174 ms 175 ms te-3-2-0.rar3.atlanta-ga.us.xo.net [207.88.12.5]
9 * 175 ms * te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
10 185 ms * 177 ms ae0d0.mcr2.chicago-il.us.xo.net [216.156.0.166]
11 177 ms 171 ms 171 ms ae1d0.mcr1.chicago-il.us.xo.net [216.156.1.81]
12 171 ms 168 ms 172 ms te-4-3.er1.Chi1.Servernap.net [66.252.3.168]
13 163 ms 177 ms 181 ms po-13.csr1.Chi3.Servernap.net [66.252.0.65]
14 159 ms 160 ms 174 ms te-9-1.ddr4.Chi3.Servernap.net [66.252.0.161]
15 * * * Request timed out.
16 185 ms 183 ms 191 ms 104.128.48.66
Trace complete.




Note: Before the change I was playing under 150 - 160.

 

[Ryan]

There's nothing wrong with 180ms

 

[LendariuM]

Okay mate, thanks for checking, however the difference that the casting has when you change from 150 to 180 - 200 is very high

I have no issues to give a time and stop playing ...


Thanks anyway.

 

[Escaravelho]

All Brazilians are complaining that the shard is catching and high ping.

 

[ThePope]

Sao Paulo average ping today, is indeed almost 400ms. Hope for you guys it get better!

 

[Metoda]

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Wszelkie prawa zastrzeżon

C:\Users\czarująca uśmiechem>ping 177.52.130.97 -t

Pinging 177.52.130.97 with 32 bytes of data:
Reply from 177.52.130.97: bytes=32 time=304ms TTL=52
Reply from 177.52.130.97: bytes=32 time=301ms TTL=52
Reply from 177.52.130.97: bytes=32 time=299ms TTL=52
Reply from 177.52.130.97: bytes=32 time=299ms TTL=52
Reply from 177.52.130.97: bytes=32 time=300ms TTL=52
Reply from 177.52.130.97: bytes=32 time=301ms TTL=52
Reply from 177.52.130.97: bytes=32 time=296ms TTL=52
Reply from 177.52.130.97: bytes=32 time=304ms TTL=52
Reply from 177.52.130.97: bytes=32 time=305ms TTL=52
Reply from 177.52.130.97: bytes=32 time=296ms TTL=52
Reply from 177.52.130.97: bytes=32 time=300ms TTL=52
Reply from 177.52.130.97: bytes=32 time=294ms TTL=52
Reply from 177.52.130.97: bytes=32 time=294ms TTL=52
Reply from 177.52.130.97: bytes=32 time=302ms TTL=52
Reply from 177.52.130.97: bytes=32 time=295ms TTL=52
Reply from 177.52.130.97: bytes=32 time=303ms TTL=52
Reply from 177.52.130.97: bytes=32 time=302ms TTL=52
Reply from 177.52.130.97: bytes=32 time=296ms TTL=52
Reply from 177.52.130.97: bytes=32 time=312ms TTL=52
Reply from 177.52.130.97: bytes=32 time=299ms TTL=52
Reply from 177.52.130.97: bytes=32 time=301ms TTL=52
Reply from 177.52.130.97: bytes=32 time=304ms TTL=52
Reply from 177.52.130.97: bytes=32 time=299ms TTL=52

From Poland

 

[LendariuM]

CRAP host with crap routes "INDEED" !!!!!!!!!!!

 

[Cold Blood]

well lots of Chinese get lag as well even with their awesome proxy. im not sure the reason of it and will check it out in days later.

 

[Ryan]

CRAP host with crap routes "INDEED" !!!!!!!!!!!

How about you offer something other than whining and conjecture?

I asked you to run pathping not a traceroute. If you can't follow simple suggestions we cannot help you.

Steadfast is in E. Cermak in Chicago, the worlds largest carrier hotel with the worlds best routing. We can fix issues if we can get the data we ask for. Otherwise we can't do anything... and I wont listen to your continued whining.

 

[The Instigator]

Damn 1.1 million square feet... I wish I owned that

 

[Ryan]

Feel free to view routes from around the world (China was just added and will propogate over the next 24 hours):

http://www.uogamers.com/community/index.php?pages/demise-monitoring/

 

[LendariuM]

Please don´t give a bad understanding about what I said man, your shard is awesome, however the host is not, at MS - DOS we can see maybe a good ping, but the experiencing we are seeyng inside the game there is no relationship, I have ping 180 - 200 in MS - DOS but in game I have 300+ ... I can provide you several screens if you want ... just let me know ...

 

[Ryan]

Please don´t give a bad understanding about what I said man, your shard is awesome, however the host is not, at MS - DOS we can see maybe a good ping, but the experiencing we are seeyng inside the game there is no relationship, I have ping 180 - 200 in MS - DOS but in game I have 300+ ... I can provide you several screens if you want ... just let me know ...

"In game ping" is not real.