also, i noticed that it gets extremely bad when you did that last vesper invasion. i was going to check it out, but the hiccups were so frequent that i just logged instead. i dont have this on any of the other servers that i play on either.

Code: Select all
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\Documents and Settings\Administrator>tracert uosecondage.com
Tracing route to uosecondage.com [70.86.184.138]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 19 ms 18 ms 18 ms 76.37.144.1
3 11 ms 7 ms 8 ms gig2-2.milwwimkin-rtr1.wi.rr.com [24.160.225.129
]
4 216 ms 210 ms 270 ms srp12-0.milwwirtco-rtr1.wi.rr.com [24.160.226.97
]
5 30 ms 27 ms 24 ms network-024-160-229-121.wi.rr.com [24.160.229.12
1]
6 25 ms 16 ms 16 ms ae-5-0.cr0.chi30.tbone.rr.com [66.109.6.112]
7 26 ms 22 ms 35 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
8 11 ms 28 ms 11 ms gblx-twc.pr0.chi10.tbone.rr.com [66.109.9.202]
9 44 ms 48 ms 44 ms The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net
[64.208.170.198]
10 115 ms 159 ms 48 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]
11 37 ms 47 ms 54 ms po31.dsr01.dllstx5.theplanet.com [70.85.127.106]
12 97 ms 79 ms 71 ms 1a.fe.5746.static.theplanet.com [70.87.254.26]
13 40 ms 43 ms 39 ms 8a.b8.5646.static.theplanet.com [70.86.184.138]
Trace complete.
H:\Documents and Settings\Administrator>ping uosecondage.com
Pinging uosecondage.com [70.86.184.138] with 32 bytes of data:
Reply from 70.86.184.138: bytes=32 time=38ms TTL=113
Reply from 70.86.184.138: bytes=32 time=54ms TTL=113
Reply from 70.86.184.138: bytes=32 time=55ms TTL=113
Reply from 70.86.184.138: bytes=32 time=54ms TTL=113
Ping statistics for 70.86.184.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 55ms, Average = 50ms
H:\Documents and Settings\Administrator>
kill drizitz wrote: also, i noticed that it gets extremely bad when you did that last vesper invasion. i was going to check it out, but the hiccups were so frequent that i just logged instead. i dont have this on any of the other servers that i play on either.
This is very strange, see this one indicates a router problem, with the packets in only one direction, while other people mention everything freezing.Slade wrote:If it was just my connection with the server, I wouldn't be able to see NPC's walking around while I'm completely frozen. Everything would freeze.
That timeout was to your ISP's gateway, other than that this looks like an excelent tracert.platy wrote:If your not having this problem then why post Ronk..your moving towards annoying..
Derrick any update? Did you notice thru the tracert i emailed you Router Number 2 was completely timed out?
It's getting worse...
Tracing route to uosecondage.com [70.86.184.138]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 10 ms 9 ms ge-1-13-ur01.davie.fl.pompano.comcast.net [68.85
.228.81]
Code: Select all
10 115 ms 159 ms 48 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]
They work like electricity or water. If any spot between you and the server is clogged, slow, damage, down, etc then you'll get slower results. Like with Electricty, if a minor line goes down you won't notice since it'll route a different way...but if a major line or a power plant went down, you'd be screwed while anyone not using that major line would have zero lag.Mazer wrote:From Slade's tracert:
I have little knowledge of how datacenters (or w/e) work but this seems to be the spot where several of us are getting weird values back from periodically (Myself, Slade, Choppa at least). In the e-mail I sent you, it took 9-10 tracerts to get a couple times where that one stood out which seems to be akin to how the lag spikes occur.Code: Select all
10 115 ms 159 ms 48 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]
Try an ingame poll perhaps, asking how many people experience the lag. Not everyone necessarily reports it.
I was referring moreso to the possibility of getting it fixed. Whether or not a few tracerts from us will be enough for whoever owns the troublesome 'network point' to take a serious look at the traffic that's going through there.Ronk wrote:They work like electricity or water. If any spot between you and the server is clogged, slow, damage, down, etc then you'll get slower results. Like with Electricty, if a minor line goes down you won't notice since it'll route a different way...but if a major line or a power plant went down, you'd be screwed while anyone not using that major line would have zero lag.
The problem seems to be that the clogged tube only happens for brief periods and most of the users in the data center wouldn't even notice it. I've currently got a 5 page trouble ticket open with the datacenter and they are stilll trying to find the root of the problem, which hopefully they will find soon, if not we will be moving.Mazer wrote:I was referring moreso to the possibility of getting it fixed. Whether or not a few tracerts from us will be enough for whoever owns the troublesome 'network point' to take a serious look at the traffic that's going through there.
In this specific example with periodic spikes that don't vary much in severity, I don't think it's a 'clogged tube' issue because this would affect all of their services and they'd probably have gotten enough complaints about it in the last month to have worked it out..
We are positive this is a network issue and not a hardware issue based on the proccess monitoring I've done on the server and the tracert's that have been submitted.Thursday November 27th, 2008; 9:29 AM CST wrote: Dear Customer,
We are currently investigating this issue. At this time i am unable to reproduce this issue. The times on the traces i have performed look good and i am not showing any packet loss. I will continue to run these test throughout out the day to see what turns up.
<name edit>
NOC Technician