Weird Server Connection Problem

[Pwnion]

So for some reason my pings been messed for the last week and I can't figure out why. I heard that a bunch of people had connection/ping issues about a week ago, but people said that all got fixed.... Well mine didn't, and I know watchyaback has teh same problem.

I used to get a ping of 8-15, and i still do, most of the time. Heres the weird part, when i have the server window open and I refresh the server it'll give me 10-15 ping but then every 3 seconds it spikes to 90-150, then goes back down. So its like somethings spiking my ping every 3-4 seconds. In game this translates to everyone moving weird every 3-4 seconds which makes the game a lot harder to play.

If anyone has any ideas what could be doing this plz tell me, cause i can't figure out if its the server or my connection or what. All other servers still ping fine for me, its just darkly thats spiking.

 

[Propaganda]

Likely not the server

Could be a bad router at home
Could be your hops to the server
Make sure you don't have HLSW or any other query tool running
Make sure you don't have torrent clients open
Check for spyware

Do a start/run/cmd and ping the server ip, also do a trace route and report the results here

 

[Pwnion]

Here's the trace

C:\Documents and Settings\Hardy>tracert 76.74.139.4

Tracing route to 76.74.139.4 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 5 ms 10.241.116.1
3 9 ms 7 ms 6 ms 69.63.242.17
4 7 ms 6 ms 6 ms gw01.hnsn.phub.net.cable.rogers.com [66.185.80.1
7]
5 6 ms 5 ms 6 ms so-4-2-0.gw02.wlfdle.phub.net.cable.rogers.com [
66.185.81.213]
6 6 ms 7 ms 6 ms pos-4-0.igw01.front.phub.net.cable.rogers.com [6
4.71.240.53]
7 8 ms 7 ms 7 ms 216.187.64.65
8 10 ms 10 ms 10 ms tor-fe3-6a.ne.peer1.net [65.39.198.234]
9 9 ms 7 ms 8 ms 76.74.139.4

Trace complete.

 

[Pwnion]

I did all these within 5 seconds of eachother and look at the variation! It's like it gets stuck over 100 during one of them, 2 of them are normal(around 10 ms) and the one thats 30-40s i dunno wtfs up with that.

C:\Documents and Settings\Hardy>ping -t 76.74.139.4

Pinging 76.74.139.4 with 32 bytes of data:

Reply from 76.74.139.4: bytes=32 time=11ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=17ms TTL=118
Reply from 76.74.139.4: bytes=32 time=10ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=10ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=10ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=7ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=7ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=10ms TTL=118
Reply from 76.74.139.4: bytes=32 time=10ms TTL=118
Reply from 76.74.139.4: bytes=32 time=11ms TTL=118
Reply from 76.74.139.4: bytes=32 time=12ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=7ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118

Ping statistics for 76.74.139.4:
Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 17ms, Average = 9ms
Control-C
^C
C:\Documents and Settings\Hardy> ping -t 76.74.139.4

Pinging 76.74.139.4 with 32 bytes of data:

Reply from 76.74.139.4: bytes=32 time=138ms TTL=118
Reply from 76.74.139.4: bytes=32 time=137ms TTL=118
Reply from 76.74.139.4: bytes=32 time=139ms TTL=118
Reply from 76.74.139.4: bytes=32 time=137ms TTL=118
Reply from 76.74.139.4: bytes=32 time=131ms TTL=118
Reply from 76.74.139.4: bytes=32 time=134ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=128ms TTL=118
Reply from 76.74.139.4: bytes=32 time=130ms TTL=118
Reply from 76.74.139.4: bytes=32 time=138ms TTL=118
Reply from 76.74.139.4: bytes=32 time=128ms TTL=118
Reply from 76.74.139.4: bytes=32 time=131ms TTL=118
Reply from 76.74.139.4: bytes=32 time=125ms TTL=118
Reply from 76.74.139.4: bytes=32 time=128ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=135ms TTL=118
Reply from 76.74.139.4: bytes=32 time=136ms TTL=118
Reply from 76.74.139.4: bytes=32 time=129ms TTL=118
Reply from 76.74.139.4: bytes=32 time=134ms TTL=118
Reply from 76.74.139.4: bytes=32 time=131ms TTL=118
Reply from 76.74.139.4: bytes=32 time=140ms TTL=118
Reply from 76.74.139.4: bytes=32 time=130ms TTL=118
Reply from 76.74.139.4: bytes=32 time=16ms TTL=118
Reply from 76.74.139.4: bytes=32 time=147ms TTL=118
Reply from 76.74.139.4: bytes=32 time=131ms TTL=118
Reply from 76.74.139.4: bytes=32 time=135ms TTL=118
Reply from 76.74.139.4: bytes=32 time=136ms TTL=118
Reply from 76.74.139.4: bytes=32 time=140ms TTL=118
Reply from 76.74.139.4: bytes=32 time=139ms TTL=118
Reply from 76.74.139.4: bytes=32 time=136ms TTL=118
Reply from 76.74.139.4: bytes=32 time=10ms TTL=118
Reply from 76.74.139.4: bytes=32 time=137ms TTL=118
Reply from 76.74.139.4: bytes=32 time=130ms TTL=118
Reply from 76.74.139.4: bytes=32 time=136ms TTL=118

Ping statistics for 76.74.139.4:
Packets: Sent = 34, Received = 34, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 147ms, Average = 119ms
Control-C
^C
C:\Documents and Settings\Hardy>ping -t 76.74.139.4

Pinging 76.74.139.4 with 32 bytes of data:

Reply from 76.74.139.4: bytes=32 time=10ms TTL=118
Reply from 76.74.139.4: bytes=32 time=29ms TTL=118
Reply from 76.74.139.4: bytes=32 time=26ms TTL=118
Reply from 76.74.139.4: bytes=32 time=22ms TTL=118
Reply from 76.74.139.4: bytes=32 time=26ms TTL=118
Reply from 76.74.139.4: bytes=32 time=30ms TTL=118
Reply from 76.74.139.4: bytes=32 time=31ms TTL=118
Reply from 76.74.139.4: bytes=32 time=32ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=22ms TTL=118
Reply from 76.74.139.4: bytes=32 time=31ms TTL=118
Reply from 76.74.139.4: bytes=32 time=35ms TTL=118
Reply from 76.74.139.4: bytes=32 time=35ms TTL=118
Reply from 76.74.139.4: bytes=32 time=27ms TTL=118
Reply from 76.74.139.4: bytes=32 time=38ms TTL=118
Reply from 76.74.139.4: bytes=32 time=30ms TTL=118
Reply from 76.74.139.4: bytes=32 time=12ms TTL=118
Reply from 76.74.139.4: bytes=32 time=36ms TTL=118
Reply from 76.74.139.4: bytes=32 time=30ms TTL=118
Reply from 76.74.139.4: bytes=32 time=34ms TTL=118
Reply from 76.74.139.4: bytes=32 time=36ms TTL=118
Reply from 76.74.139.4: bytes=32 time=35ms TTL=118
Reply from 76.74.139.4: bytes=32 time=40ms TTL=118
Reply from 76.74.139.4: bytes=32 time=37ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=37ms TTL=118
Reply from 76.74.139.4: bytes=32 time=42ms TTL=118
Reply from 76.74.139.4: bytes=32 time=42ms TTL=118
Reply from 76.74.139.4: bytes=32 time=34ms TTL=118
Reply from 76.74.139.4: bytes=32 time=42ms TTL=118
Reply from 76.74.139.4: bytes=32 time=41ms TTL=118
Reply from 76.74.139.4: bytes=32 time=35ms TTL=118
Reply from 76.74.139.4: bytes=32 time=11ms TTL=118
Reply from 76.74.139.4: bytes=32 time=34ms TTL=118
Reply from 76.74.139.4: bytes=32 time=42ms TTL=118
Reply from 76.74.139.4: bytes=32 time=40ms TTL=118
Reply from 76.74.139.4: bytes=32 time=35ms TTL=118
Reply from 76.74.139.4: bytes=32 time=47ms TTL=118
Reply from 76.74.139.4: bytes=32 time=45ms TTL=118
Reply from 76.74.139.4: bytes=32 time=39ms TTL=118

Ping statistics for 76.74.139.4:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 47ms, Average = 31ms
Control-C
^C
C:\Documents and Settings\Hardy>ping -t 76.74.139.4

Pinging 76.74.139.4 with 32 bytes of data:

Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=17ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=19ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=7ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118
Reply from 76.74.139.4: bytes=32 time=9ms TTL=118
Reply from 76.74.139.4: bytes=32 time=8ms TTL=118

Ping statistics for 76.74.139.4:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 19ms, Average = 9ms
Control-C

 

[Pwnion]

I know its not my router cause like I said, everything but the darkly server is fine. I don't have torrents open when I play, I don't' have spyware(I run a tight ship).

I don't think I have another querying tool running. I'm not sure what you meant by this.

It didn't seem liek it was the hops to the server, but if it is how can I get this fixed???

don't forget, watchyaback had teh exact same problem as me, we also both have rogers and he lives in sauga, I live in brampton, so maybe its rogers, but spinny also has rogers and he did have this problem but his fixed a couple days after it started. So I dunno...

 

[Low Budget]

Weird.

 

[Propaganda]

Yes weird. Call your ISP. You on cable or dsl?

 

[crojon]

same problem occuring lately..went away and now it has returned, im with rogers aswell i Live in sauga too...if its rogers illl freakkkkkkk.

 

[Pwnion]

I bet it is! I'm on rogers cable right now. Prolly switching to Primus soon cause I'm sick of rogers bs cap on data transfer.

Prop! If it is a suspected problem with rogers when I call them what do I say/tell them to do???

 

[Low Budget]

I have rogers 10mpbs and i live in sauga. No problem over here.

 

[47]

u got rogers extreme for $55/month LB ?? i got that i DL at 900+ and upload at like 30 !!! fucking rip off...

i ran this test: http://www.speakeasy.net/speedtest/

7969 down and 927 up


dont use rogers speed test, its rigged !

 

[Propaganda]

[quote1225170532=Pwnion]
I bet it is! I'm on rogers cable right now. Prolly switching to Primus soon cause I'm sick of rogers bs cap on data transfer.

Prop! If it is a suspected problem with rogers when I call them what do I say/tell them to do???
[/quote1225170532]

First tell them they suck cock. Then tell them you have bad latency spikes, they probably won't care, like Shaw cable in Alberta told me when I called them "well thats the way cable is", then call someone else and try them out, maybe try a good dsl package, not blazing dl speed, but constant good connection.

 

[td|35mm]

I'm on rogers ...

Last Result:
Download Speed: 8787 kbps (1098.4 KB/sec transfer rate)
Upload Speed: 933 kbps (116.6 KB/sec transfer rate)

I have days when my download speed is 10000+

 

[TD|night blade]

I had Rogers a couple years ago when Shaw sold out to them, they sucked so bad I had to switch to DSL. It not the speed that was the problem, it was the latency issues & peak time speed that fucking pissed me off. I went from broadband connection to dial-up during peak, was stupid so I switched to a DSL provider, haven't looked back since.

Pwnion, head to www.dslreports.com, go to tools & try the "Line Quality Test" & "Smokeping", might find something.

 

[Pwnion]

Thanks Night Blade, I'm trying those tests now. I know its not a peek usage time issue, this happens all the time and its so annoying.

I might be switching to primus at the end of this month. Rogers is a ripoff anyway, and primus quotes comparable speeds with no usage cap for less than it costs for rogers slower packages.

 

[Pwnion]

Well, the line quality test showed that people in this area have been getting crappy connections, although it said mine was fine right now which doesn't surprise me, cause its only the darkly server that has a bad hop to it i think.