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.
Damn the lag to hell!
- Thread starter Ryan
- Start date
Heavy Smoker
Knight
Re: Damn the lag to hell!
Must be a problem with your connection, I have NO lag. Thanks so much. :>
Must be a problem with your connection, I have NO lag. Thanks so much. :>
Re: Damn the lag to hell!
The only "lag" I have experianced since it came back up is from them doing world saves and gm commands to test it. The rest of the time its perfect. As far as ping my ping is awesome as always.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>ping login.uogamers.com
Pinging login.uogamers.com [75.126.37.240] with 32 bytes of data:
Reply from 75.126.37.240: bytes=32 time=18ms TTL=119
Reply from 75.126.37.240: bytes=32 time=17ms TTL=119
Reply from 75.126.37.240: bytes=32 time=17ms TTL=119
Reply from 75.126.37.240: bytes=32 time=19ms TTL=119
Ping statistics for 75.126.37.240:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 19ms, Average = 17ms
C:\>
Yes, thats right, I have a amazing unfair advantage.
The only "lag" I have experianced since it came back up is from them doing world saves and gm commands to test it. The rest of the time its perfect. As far as ping my ping is awesome as always.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>ping login.uogamers.com
Pinging login.uogamers.com [75.126.37.240] with 32 bytes of data:
Reply from 75.126.37.240: bytes=32 time=18ms TTL=119
Reply from 75.126.37.240: bytes=32 time=17ms TTL=119
Reply from 75.126.37.240: bytes=32 time=17ms TTL=119
Reply from 75.126.37.240: bytes=32 time=19ms TTL=119
Ping statistics for 75.126.37.240:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 19ms, Average = 17ms
C:\>
Yes, thats right, I have a amazing unfair advantage.
Re: Damn the lag to hell!
My results from a tracert: login.uogamers.com. Note the bottleneck. Generally the first
few hops is your own ISP. Any hops after that is a neutral router.
So if you're getting a bottleneck similar to the results below, it's definately not your
ISP that's causing the issue.
Tracing route to login.uogamers.com [75.126.37.240]
over a maximum of 30 hops:
1 6 ms 7 ms 6 ms 10.14.48.1
2 6 ms 7 ms 8 ms 68.10.14.45
3 7 ms 6 ms 7 ms 172.22.48.54
4 7 ms 8 ms 8 ms 172.22.48.26
5 7 ms 8 ms 8 ms 172.22.48.102
6 8 ms 7 ms 8 ms nrfkdsrj02-ge702.rd.hr.cox.net [68.10.14.13]
7 14 ms 14 ms 14 ms ashbbbrj01-ae0.0.r2.as.cox.net [68.1.0.220]
8 15 ms 13 ms 14 ms cpr2-pos-3-0.virginiaequinix.savvis.net [204.70.193.165]
9 14 ms 14 ms 15 ms ber1-tenge-2-1.virginiaequinix.savvis.net [204.70.193.6]
10 16 ms 15 ms 15 ms hr1-tengig8-1.sterling2dc3.savvis.net [204.70.197.81]
11 * * * Request timed out.
12 53 ms 53 ms 53 ms cr1-loopback.dan.savvis.net [208.172.130.70]
13 50 ms 51 ms 51 ms pr2-ge-4-0-0.DallasEquinix.savvis.net [204.70.200.169]
14 55 ms 47 ms 45 ms te7-3.cer02.dal01.dallas-border.com [208.175.175.10]
15 47 ms 46 ms 47 ms po52.fcr01.dal01.dallas-datacenter.com [66.228.118.158]
16 47 ms 46 ms 46 ms login.uogamers.com [75.126.37.240]
Trace complete.
Hop #11 is the culprit!
<sarcasm>
I guess Ted Stevens had a point?
Damn kids and their youtube!
</sarcasm>
:-D
My results from a tracert: login.uogamers.com. Note the bottleneck. Generally the first
few hops is your own ISP. Any hops after that is a neutral router.
So if you're getting a bottleneck similar to the results below, it's definately not your
ISP that's causing the issue.
Tracing route to login.uogamers.com [75.126.37.240]
over a maximum of 30 hops:
1 6 ms 7 ms 6 ms 10.14.48.1
2 6 ms 7 ms 8 ms 68.10.14.45
3 7 ms 6 ms 7 ms 172.22.48.54
4 7 ms 8 ms 8 ms 172.22.48.26
5 7 ms 8 ms 8 ms 172.22.48.102
6 8 ms 7 ms 8 ms nrfkdsrj02-ge702.rd.hr.cox.net [68.10.14.13]
7 14 ms 14 ms 14 ms ashbbbrj01-ae0.0.r2.as.cox.net [68.1.0.220]
8 15 ms 13 ms 14 ms cpr2-pos-3-0.virginiaequinix.savvis.net [204.70.193.165]
9 14 ms 14 ms 15 ms ber1-tenge-2-1.virginiaequinix.savvis.net [204.70.193.6]
10 16 ms 15 ms 15 ms hr1-tengig8-1.sterling2dc3.savvis.net [204.70.197.81]
11 * * * Request timed out.
12 53 ms 53 ms 53 ms cr1-loopback.dan.savvis.net [208.172.130.70]
13 50 ms 51 ms 51 ms pr2-ge-4-0-0.DallasEquinix.savvis.net [204.70.200.169]
14 55 ms 47 ms 45 ms te7-3.cer02.dal01.dallas-border.com [208.175.175.10]
15 47 ms 46 ms 47 ms po52.fcr01.dal01.dallas-datacenter.com [66.228.118.158]
16 47 ms 46 ms 46 ms login.uogamers.com [75.126.37.240]
Trace complete.
Hop #11 is the culprit!
<sarcasm>
I guess Ted Stevens had a point?
Damn kids and their youtube!
</sarcasm>
:-D
Re: Damn the lag to hell!
I am sorry but your incorrect. Some servers and routers are setup to not reply to pings. So this is normal. In your example 1 is you and 2 - 7 are your isp COX and 8 -13 are the isp Savvis . 14 -16 are the isp the server is hosted by SoftLayer Technologies Inc which includes the server itself.
Had you got a response like
8 130 ms 120 ms 125 ms cpr2-pos-3-0.virginiaequinix.savvis.net [204.70.193.165]
that would be a sign of a problem.
Here is mine
C:\>tracert login.uogamers.com
Tracing route to login.uogamers.com [75.126.37.240]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 192.168.0.1
3 8 ms 8 ms 8 ms ppp-70-128-127-254.dsl.tulsok.swbell.net [70.128
.127.254]
4 137 ms 12 ms 18 ms dist2-vlan50.tul2ok.sbcglobal.net [69.152.80.67]
5 8 ms 7 ms 8 ms bb1-g5-0-0.tul2ok.sbcglobal.net [69.152.80.242]
6 18 ms 18 ms 17 ms 151.164.95.188
7 18 ms 76 ms 18 ms 151.164.251.162
8 18 ms 19 ms 18 ms te7-2.cer02.dal01.dallas-border.com [64.215.81.2
]
9 20 ms 18 ms 17 ms po52.fcr01.dal01.dallas-datacenter.com [66.228.1
18.158]
10 18 ms 17 ms 18 ms login.uogamers.com [75.126.37.240]
Trace complete.
1 and 2 are my local network.
3-7 are my isp AT&T (formarly SBC)
8-10 are SoftLayer Technologies Inc
So basicly Softlayer has more than one isp that they get bandwidth from (very common). For sure Savvis and AT&T. My ping is amazing because I live in Oklahoma and the server is just south of me in Dallas. I was in Dallas last week due to the power outage here. It's about a 5 hour drive. So I am really close to the server and I am on the same network as the isp that they get the bandwidth from. The further away you are the more servers you have to go threw to get to your destination and that slows you down.
C:\>ping login.uogamers.com
Pinging login.uogamers.com [75.126.37.240] with 32 bytes of data:
Reply from 75.126.37.240: bytes=32 time=19ms TTL=119
Reply from 75.126.37.240: bytes=32 time=18ms TTL=119
Reply from 75.126.37.240: bytes=32 time=20ms TTL=119
Reply from 75.126.37.240: bytes=32 time=18ms TTL=119
Ping statistics for 75.126.37.240:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 20ms, Average = 18ms
C:\>
Rhaedryn;1610524 said:
I am sorry but your incorrect. Some servers and routers are setup to not reply to pings. So this is normal. In your example 1 is you and 2 - 7 are your isp COX and 8 -13 are the isp Savvis . 14 -16 are the isp the server is hosted by SoftLayer Technologies Inc which includes the server itself.
Had you got a response like
8 130 ms 120 ms 125 ms cpr2-pos-3-0.virginiaequinix.savvis.net [204.70.193.165]
that would be a sign of a problem.
Here is mine
C:\>tracert login.uogamers.com
Tracing route to login.uogamers.com [75.126.37.240]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 192.168.0.1
3 8 ms 8 ms 8 ms ppp-70-128-127-254.dsl.tulsok.swbell.net [70.128
.127.254]
4 137 ms 12 ms 18 ms dist2-vlan50.tul2ok.sbcglobal.net [69.152.80.67]
5 8 ms 7 ms 8 ms bb1-g5-0-0.tul2ok.sbcglobal.net [69.152.80.242]
6 18 ms 18 ms 17 ms 151.164.95.188
7 18 ms 76 ms 18 ms 151.164.251.162
8 18 ms 19 ms 18 ms te7-2.cer02.dal01.dallas-border.com [64.215.81.2
]
9 20 ms 18 ms 17 ms po52.fcr01.dal01.dallas-datacenter.com [66.228.1
18.158]
10 18 ms 17 ms 18 ms login.uogamers.com [75.126.37.240]
Trace complete.
1 and 2 are my local network.
3-7 are my isp AT&T (formarly SBC)
8-10 are SoftLayer Technologies Inc
So basicly Softlayer has more than one isp that they get bandwidth from (very common). For sure Savvis and AT&T. My ping is amazing because I live in Oklahoma and the server is just south of me in Dallas. I was in Dallas last week due to the power outage here. It's about a 5 hour drive. So I am really close to the server and I am on the same network as the isp that they get the bandwidth from. The further away you are the more servers you have to go threw to get to your destination and that slows you down.
C:\>ping login.uogamers.com
Pinging login.uogamers.com [75.126.37.240] with 32 bytes of data:
Reply from 75.126.37.240: bytes=32 time=19ms TTL=119
Reply from 75.126.37.240: bytes=32 time=18ms TTL=119
Reply from 75.126.37.240: bytes=32 time=20ms TTL=119
Reply from 75.126.37.240: bytes=32 time=18ms TTL=119
Ping statistics for 75.126.37.240:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 20ms, Average = 18ms
C:\>
Triple h-Lot.Tld.Rbk
Sorceror
Re: Damn the lag to hell!
i likey!!!
i likey!!!