UOGamers 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!

  • To obtain new Razor updates, please reinstall Razor from our new website.

Upcoming Server Move

GasMask

Wanderer
Re: Upcoming Server Move

Hmm well im running off someone elses router in the neighborhood temperarely.
when i get mine turned back on, it will have road runner high speed cable.
 

Mark

Knight
Re: Upcoming Server Move

GasMask;1681196 said:
Hmm well im running off someone elses router in the neighborhood temperarely.
when i get mine turned back on, it will have road runner high speed cable.

The wireless link you are currently using would explain the fluctuation I saw when pinging your connection.

Your neighbor has Road Runner, so the latency will probably be the same when you get your own access (just more stable).
 

Endless Darc

Wanderer
Re: Upcoming Server Move

I have Road Runner Cable, But I don't run a wireless router, and the line my internet is on is straight from the pole, its not split for a tv like most peoples are. When its split it loses signal.

Long story short-
I get the best signal possible and the losest ping Ive had so far was 27.
 
Re: Upcoming Server Move

got road runner too, but ya i got cable tv and shit so eh. plus i split it between two comps sothat doesnt help either i suppose. still bullshit someone in Iowa has better ping than me! :/
 
Re: Upcoming Server Move

That's not hurting my ping.. What hurts my ping is that cox routes me to New York before pairing with road runner. :(
 

drakrum-hybrid

Sorceror
Re: Upcoming Server Move

Code:
[FONT=Tahoma]C:\Documents and Settings\Brandon>tracert 67.192.185.136 ([B]Current[/B])[/FONT]
[FONT=Tahoma]Tracing route to 67.192.185.136 over a maximum of 30 hops[/FONT]
[FONT=Tahoma]  1    <1 ms    <1 ms    <1 ms  launchmodem [192.168.1.254]
  2    15 ms    15 ms    15 ms  68.152.229.54
  3    15 ms    15 ms    15 ms  68.216.237.249
  4    20 ms    20 ms    26 ms  ixc01mgm-ge-0-2-2.bellsouth.net [205.152.170.30][/FONT]
[FONT=Tahoma]  5    19 ms    20 ms    20 ms  axr00aep-so-2-0-0.bellsouth.net [65.83.236.38]
  6    20 ms    20 ms    19 ms  axr01aep-ge-5-0-0.bellsouth.net [65.83.238.35]
  7    20 ms    19 ms    20 ms  pxr00asm-3-0-0.bellsouth.net [65.83.236.6]
  8    20 ms    21 ms    19 ms  ge-4-2-1.mpr2.atl6.us.above.net [64.125.12.221][/FONT]
[FONT=Tahoma]  9    21 ms    20 ms    20 ms  xe-0-0-0.mpr3.atl6.us.above.net [64.125.31.41]
 10    35 ms    35 ms    35 ms  ge-2-1-0.mpr4.iah1.us.above.net [64.125.31.50]
 11    40 ms    40 ms    41 ms  so-1-1-0.mpr2.dfw2.us.above.net [64.125.26.133][/FONT]
[FONT=Tahoma] 12    52 ms    73 ms    63 ms  xe-1-1-0.er2.dfw2.us.above.net [64.125.26.214]
 13    39 ms    39 ms    39 ms  xe-0-0-0.er1.dfw2.us.above.net [64.125.26.205]
 14    49 ms    54 ms    49 ms  209.133.126.42
 15    60 ms    59 ms    60 ms  vlan905.core5.dfw1.rackspace.com [67.192.56.229][/FONT]
[FONT=Tahoma] 16    60 ms    60 ms    61 ms  67.192.56.35
 17    48 ms    48 ms    48 ms  67.192.185.136[/FONT]
[FONT=Tahoma]Trace complete.[/FONT]

Code:
[FONT=Tahoma]C:\Documents and Settings\Brandon>tracert 209.173.139.110 ([B]OH)[/B][/FONT]
[FONT=Tahoma]Tracing route to 209.173.139.110 over a maximum of 30 hops[/FONT]
[FONT=Tahoma]  1    <1 ms    <1 ms    <1 ms  launchmodem [192.168.1.254]
  2    15 ms    15 ms    15 ms  68.152.229.54
  3    15 ms    15 ms    15 ms  68.216.237.249
  4    50 ms    33 ms    32 ms  ixc01mgm-ge-0-2-2.bellsouth.net [205.152.170.30][/FONT]
[FONT=Tahoma]  5    19 ms    20 ms    20 ms  axr00aep-so-2-0-0.bellsouth.net [65.83.236.38]
  6    31 ms    32 ms    32 ms  pxr00ash-so-0-1-0.bellsouth.net [65.83.236.74]
  7    32 ms    31 ms    31 ms  peer-01-ge-3-1-0-14.asbn.twtelecom.net [66.192.2
52.236]
  8    48 ms    48 ms    49 ms  207-250-147-226.static.twtelecom.net [207.250.14
7.226]
  9    49 ms    48 ms    48 ms  207-250-147-226.static.twtelecom.net [207.250.14
7.226]
 10    48 ms    48 ms    49 ms  209.173.128.70
 11    50 ms    49 ms    49 ms  209.173.128.142
 12    50 ms    48 ms    49 ms  209.173.139.110[/FONT]
[FONT=Tahoma]Trace complete.[/FONT]

Nice. 5 less hops to the future host and less 'jitter'. Much more consistent.
 

MarcusO

Sorceror
Re: Upcoming Server Move

Mark;1680825 said:
Those on the east coast, central United States, Canada, and Europe should see a reduction in latency, no packet loss (compared to transient losses over some of the congested Texas links), less jitter (latency variation), and lower hop counts. Users on the west coast can generally expect their latency to increase 20-30ms but should still see a significant overall improvement given the reduction in packet loss and jitter (which affect gameplay much more than latency).

I'm in Northern Virginia on Cox Cable Crap and I was just pinging 45 ms to the Texa$$ IP. The new IP in the Buckeye State puts me at 39 ms...a 13% improvement. Woot! Sucks for Left coast folks though.

If there's another fellow NoVa person out there on Verizon FIOS, can you please post your ping times?
 

Sprint-

Wanderer
Re: Upcoming Server Move

MarcusO;1681479 said:
I'm in Northern Virginia on Cox Cable Crap and I was just pinging 45 ms to the Texa$$ IP. The new IP in the Buckeye State puts me at 39 ms...a 13% improvement. Woot! Sucks for Left coast folks though.

If there's another fellow NoVa person out there on Verizon FIOS, can you please post your ping times?

lol@ left coast
NEW SERVER:

C:\Documents and Settings\Compaq_Administrator>ping 209.173.139.110

Pinging 209.173.139.110 with 32 bytes of data:

Reply from 209.173.139.110: bytes=32 time=48ms TTL=118
Reply from 209.173.139.110: bytes=32 time=49ms TTL=118
Reply from 209.173.139.110: bytes=32 time=48ms TTL=118
Reply from 209.173.139.110: bytes=32 time=48ms TTL=118

Ping statistics for 209.173.139.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 49ms, Average = 48ms

OLD SERVER:

C:\Documents and Settings\Compaq_Administrator>ping 67.192.185.136

Pinging 67.192.185.136 with 32 bytes of data:

Reply from 67.192.185.136: bytes=32 time=27ms TTL=117
Reply from 67.192.185.136: bytes=32 time=28ms TTL=117
Reply from 67.192.185.136: bytes=32 time=27ms TTL=117
Reply from 67.192.185.136: bytes=32 time=27ms TTL=117

Ping statistics for 67.192.185.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms

also; I always ping 80-100 on current server (according to razor), does that mean I'll ping like 120+ on new one? :(
 

ecurb12849

Sorceror
Re: Upcoming Server Move

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Reltub>ping 67.192.185.136

Pinging 67.192.185.136 with 32 bytes of data:

Reply from 67.192.185.136: bytes=32 time=80ms TTL=108
Reply from 67.192.185.136: bytes=32 time=82ms TTL=108
Reply from 67.192.185.136: bytes=32 time=81ms TTL=108
Reply from 67.192.185.136: bytes=32 time=80ms TTL=108

Ping statistics for 67.192.185.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 82ms, Average = 80ms

C:\Documents and Settings\Reltub>ping 209.173.139.110

Pinging 209.173.139.110 with 32 bytes of data:

Reply from 209.173.139.110: bytes=32 time=89ms TTL=109
Reply from 209.173.139.110: bytes=32 time=89ms TTL=109
Reply from 209.173.139.110: bytes=32 time=88ms TTL=109
Reply from 209.173.139.110: bytes=32 time=88ms TTL=109

Ping statistics for 209.173.139.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 89ms, Average = 88ms

C:\Documents and Settings\Reltub>
 
Top