Forums-->Problems and errors (general)-->
Author | Lag / Connection problems |
I have been getting excessive lag recently (had to increase GB turn time to 60s and still missing a lot of moves).
I have run tracert & ping (resilts below)
- from windows click START>>RUN>> [type command] [press ENTER]
at prompt type:
- ping www.lordswm.com
- tracert www.lordswm.com
_______________________
Tracing route to www.lordswm.com [67.220.205.82]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [xxx.xxx.xxx.xxx]
2 39 ms 39 ms 39 ms lo98.sc-acc-sip-1.as9105.net [212.74.102.14]
3 40 ms 40 ms 40 ms 10.72.4.66
4 42 ms 41 ms 40 ms 10.72.9.217
5 40 ms 41 ms 40 ms xe-7-0-0-118.lon10.ip4.tinet.net [77.67.65.73]
6 111 ms 109 ms 109 ms xe-3-3-0.nyc32.ip4.tinet.net [89.149.187.142]
7 110 ms 109 ms 113 ms Te-3-4.car3.NewYork1.Level3.net [4.68.110.77]
8 118 ms 113 ms 121 ms vlan99.csw4.NewYork1.Level3.net [4.68.16.254]
9 115 ms 111 ms 125 ms ae-94-94.ebr4.NewYork1.Level3.net [4.69.134.125]
10 182 ms 186 ms 190 ms ae-2.ebr4.SanJose1.Level3.net [4.69.135.185]
11 194 ms 188 ms 191 ms ae-84-84.csw3.SanJose1.Level3.net [4.69.134.250]
12 202 ms 189 ms 182 ms ae-83-83.ebr3.SanJose1.Level3.net [4.69.134.233]
13 197 ms 184 ms 211 ms ae-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]
14 236 ms 220 ms 191 ms ae-3-80.edge3.LosAngeles1.Level3.net [4.69.144.137]
15 196 ms 196 ms 204 ms xe2-0.cr01.lax01.mzima.net [4.71.136.2]
16 205 ms * 194 ms xe1-0.cr01.lax02.mzima.net [64.235.224.182]
17 187 ms 190 ms 193 ms ge1.webnx.lax02.mzima.net [64.235.245.66]
18 185 ms 187 ms 188 ms 67-220-192-101.hosted.static.webnx.com [67.220.192.101]
19 187 ms 188 ms 187 ms 67-220-205-82.hosted.static.webnx.com [67.220.205.82]
Trace complete.
_______________________
Pinging www.lordswm.com [67.220.205.82] with 32 bytes of data:
Request timed out.
Reply from 67.220.205.82: bytes=32 time=187ms TTL=53
Reply from 67.220.205.82: bytes=32 time=184ms TTL=53
Reply from 67.220.205.82: bytes=32 time=185ms TTL=53
Ping statistics for 67.220.205.82:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 187ms, Average = 185ms
_______________________
If others can also run these two utilities then maybe it will help admins identify the problems. From the results it looks to be a server bandwidth issue and not a server overload problem. | I was also experiencing problems around this time, although some users were not, if I'd have checked forums I would have been able to copy my ping requests but I closed command prompt long ago unfortunately :( | This was not just for a short period but has been the same for over a week.
I just did another ping a few minutes ago:
Pinging www.lordswm.com [67.220.205.82] with 32 bytes of data:
Reply from 67.220.205.82: bytes=32 time=188ms TTL=53
Reply from 67.220.205.82: bytes=32 time=185ms TTL=53
Reply from 67.220.205.82: bytes=32 time=185ms TTL=53
Reply from 67.220.205.82: bytes=32 time=185ms TTL=53
Ping statistics for 67.220.205.82:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 188ms, Average = 185ms
_________________________________
Still the same slow response. In comparison, most other websites I ping (e.g. www.google.com, etc) average around 41ms | C:\Documents and Settings\Administrator>ping www.lordswm.com -t
Pinging www.lordswm.com [67.220.205.82] with 32 bytes of data:
Reply from 67.220.205.82: bytes=32 time=214ms TTL=50
Reply from 67.220.205.82: bytes=32 time=226ms TTL=50
Reply from 67.220.205.82: bytes=32 time=213ms TTL=50
Reply from 67.220.205.82: bytes=32 time=215ms TTL=50
Reply from 67.220.205.82: bytes=32 time=212ms TTL=50
Reply from 67.220.205.82: bytes=32 time=215ms TTL=50
Reply from 67.220.205.82: bytes=32 time=215ms TTL=50
Reply from 67.220.205.82: bytes=32 time=212ms TTL=50
Reply from 67.220.205.82: bytes=32 time=214ms TTL=50
Reply from 67.220.205.82: bytes=32 time=218ms TTL=50
Reply from 67.220.205.82: bytes=32 time=212ms TTL=50
Reply from 67.220.205.82: bytes=32 time=218ms TTL=50
Reply from 67.220.205.82: bytes=32 time=218ms TTL=50
Ping statistics for 67.220.205.82:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 212ms, Maximum = 226ms, Average = 215ms | Seems fine on my end.
Be glad for your lower pings :). |
Back to topics list
|