• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Is anyone else using a cable modem getting the worst pings EVER?

N8Magic

Lifer
Check out this tracert to www.yahoo.com:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\booyah>tracert www.yahoo.com

Tracing route to www.yahoo.akadns.net [64.58.76.229]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms regina.gnomeless.net [192.168.0.1]
2 2549 ms 2625 ms 2593 ms tlgw8.ktchnr.phub.net.cable.rogers.com [24.xxx.xxx.xx]
3 2265 ms 2492 ms 2687 ms 10.1.64.1
4 2365 ms 2550 ms 2566 ms gw01.ktgc.phub.net.cable.rogers.com [66.185.81.105]
5 2598 ms 2189 ms 2210 ms gw01.cambr.phub.net.cable.rogers.com [66.185.81.101]
6 2452 ms 2646 ms 2520 ms gw01.brntfd.phub.net.cable.rogers.com [66.185.81.97]
7 2619 ms 2559 ms 2613 ms gw02.wlfdle.phub.net.cable.rogers.com [66.185.81.65]
8 2641 ms 2587 ms 2707 ms gw01.wlfdle.phub.net.cable.rogers.com [66.185.80.137]
9 1994 ms 1857 ms 2331 ms if-13-0.core3.NewYork.teleglobe.net [64.86.206.133]
10 * * * Request timed out.
11 2716 ms 2659 ms 2423 ms if-7-0.core1.Chicago3.Teleglobe.net [207.45.220.45]
12 2028 ms 2064 ms 1579 ms ix-2-0.core1.Chicago3.Teleglobe.net [207.45.222.222]
13 1762 ms 1685 ms 1869 ms agr3-loopback.Chicago.cw.net [208.172.2.103]
14 1752 ms 1874 ms 1870 ms 208.175.10.9
15 1966 ms 1986 ms 1951 ms 208.175.10.82
16 1904 ms 1583 ms 1540 ms 216.34.183.97
17 1475 ms 1486 ms 1410 ms bbr01-p8-0.whkn01.exodus.net [216.32.132.54]
18 1087 ms 1055 ms 1050 ms bbr02-g5-0.whkn01.exodus.net [216.35.65.84]
19 1019 ms 1169 ms 1211 ms bbr01-p1-0.nycm01.exodus.net [206.79.9.117]
20 1089 ms 1233 ms 790 ms bbr01-p0-0.stng01.exodus.net [206.79.9.102]
21 1056 ms 1179 ms 1086 ms dcr04-g6-0.stng01.exodus.net [216.33.99.84]
22 1072 ms 1079 ms 976 ms csr22-ve241.stng01.exodus.net [216.33.98.19]
23 891 ms 826 ms 1068 ms 216.35.210.126
24 866 ms 917 ms 1036 ms w8.dcx.yahoo.com [64.58.76.229]

Trace complete.

I'm on Roger's Cable internet, incase anyone is wondering... do you think I should call them up and be like WTF?
 
I have severe packloss and high pings to my gateway a couple weeks back. After a few tech support calls I got to somebody high enough who was able to remotely reset my modem (more than just a power cycle). It took like 2 hours to sort itself out but since then I've been dandy. It could be your modem or maybe rogers...
 
N8, I'm also timing out on that hop through the Teleglobe network - but only to a couple of sites. What I've been told is there's a screw-up in there that's affecting us, but it's not like Rogers can do anything about it.
rolleye.gif
I'm going to power cycle my cable modem right now and see if somehow after that it takes an alternate route to the site...

Oh - but I still have great pings unlike you. 😀
 
Those are not normal pings in any way - and Skoorb - they probably bounced your port or realized they had F'd up your provisioning in some way (I work at an ISP)
 
Ahhh, the power cycle of the modem did it. Pings are back to normal.

Thanks for your help guys! 😀
<----- n00b 😱
 
I believe teh worst ping ever was reported by a man in brazil. It was like 2 hours. Your 2 seconds is NOTHING!
 


<< I believe teh worst ping ever was reported by a man in brazil. It was like 2 hours. Your 2 seconds is NOTHING! >>



What, did a man named Juan have to go out and yell PINNNNGGGG!!! across a field? I don't think 2 hours is a ping, but a circuit problem 😀
 
Back
Top