High Ping in TF2

[Hieyeck]

i bet you have use rogers.

long story short, someone shat on a rogers router.

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 9 ms 7 ms 8 ms 10.74.160.1
3 6 ms 38 ms 22 ms gw03.mtnk.phub.net.cable.rogers.com [66.185.90.97]
4 7 ms 8 ms 11 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.83.105]
5 21 ms 7 ms 41 ms so-3-1-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.83.126]
6 85 ms 83 ms 84 ms pos-4-0.igw01.front.phub.net.cable.rogers.com [64.71.240.53]
7 83 ms 85 ms 84 ms gw-spdnetwork.torontointernetxchange.net [198.32.245.81]
8 86 ms 84 ms 90 ms bb1.yyz02.spdnetwork.net [208.68.88.130]
9 * * * Request timed out.

[Boodah]

Hieyeck is it intermittant like his though? Or did you manage to capture that trace while the spike was happening

[archivist101]

I just learned of the "tracert" command for Command Prompt. Mine looks pretty similar Hieyeck.

Yes, I do have rogers... how did you know?

C:\Documents and Settings\Morgan Gill>tracert 67.213.67.72

1 15 ms 29 ms 5 ms 192.168.0.1
2 19 ms 14 ms 17 ms 10.9.160.1
3 * 34 ms * vl-201.gw03.etob.phub.net.cable.rogers.com [66.185.90.129]
4 12 ms 14 ms 20 ms gi-2-0.gw01.etob.phub.net.cable.rogers.com [66.185.93.129]
5 22 ms 24 ms 34 ms so-4-0-0.gw02.bloor.phub.net.cable.rogers.com [64.71.240.166]
6 31 ms 27 ms 27 ms pos-3-0.igw01.front.phub.net.cable.rogers.com [64.71.240.29]
7 119 ms 127 ms 143 ms gw-spdnetwork.torontointernetxchange.net [198.32.245.81]
8 122 ms 105 ms 104 ms bb1.yyz02.spdnetwork.net [208.68.88.130]


Trace complete.

[rk-]

Man, now I'm interested in this tracert thang.. it's like the new cocaine!

[gOOCH]

ya its people with rogers guys, a bunch of people on css experienced it, and i had to deal with it in a cal match last night

[Crayola]

when i do a tracert i time out from hop8 - hop 30

[manofphat]

Hop 8 would have been the server.
You need to tracert until the last hop that you can actually ping.
I'm discarding ping requests on the server right now because of something that happened the other day

[Crayola]

up until my last hop i dont ping anywhere over 10, so i dont think its a rogers issue

[ArchAngel2]

I am on Rogers and I don't have any trouble like you're describing.

Your Rogers connection to the TNR servers should be lightning fast regardless of where you are as they have a direct pipe into the TorEX network in 151 Front St where these servers are housed.

It could be a funky router on Rogers' end. See if you can coordinate with someone else who is having these issues to see if they are happening at the same time. If they are it's likely not your connection/computer. If the occurrences are random then it could be some kind of software running in the background as mentioned above.

Run all the usual virus/spyware scans to make sure it's not something like that and then check other programs you have installed. I found an issue between Nero and my Logitech G15 the other day that was causing the LCD to not work. I couldn't fine a single post about this online and just found it by trial and error. Try the same and you may figure it out.

[gOOCH]

Hop 8 would have been the server.
You need to tracert until the last hop that you can actually ping.
I'm discarding ping requests on the server right now because of something that happened the other day

ok mano



Tracing route to 67.213.67.67 over a maximum of 30 hops

1 6 ms 5 ms 6 ms 10.242.32.1
2 8 ms 8 ms 6 ms vl-201.gw03.wlfdle.phub.net.cable.rogers.com [66.185.90.161]
3 7 ms 7 ms 14 ms te-6-1-0.gw01.wlfdle.phub.net.cable.rogers.com [24.153.5.41]
4 8 ms 8 ms 6 ms so-2-3-0.gw02.bloor.phub.net.cable.rogers.com [64.71.240.106]
5 7 ms 8 ms 7 ms pos-3-0.igw01.front.phub.net.cable.rogers.com [64.71.240.29]
6 9 ms 9 ms 9 ms gw-spdnetwork.torontointernetxchange.net [198.32.245.81]
7 9 ms 10 ms 10 ms bb1.yyz02.spdnetwork.net [208.68.88.130]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.