US Cable Support > Comcast HSI > Ping is up from 22 to 46: Sandy issue?

Ping is up from 22 to 46: Sandy issue?

ping to where? 46 still isnt high. traffic on the interwebz= higher ping
--
I'm better than you!

reply to signmeuptoo
Depends on the area you are in. If you're in the area that was hit or very close to it could be so.

They may have had to change routing to keep you online.

No way to know without traceroute of prior ping and new one at this point.

You probably route through the same NY router I do now. It makes all my pings go to 45 or so. Don't say it's low priority pinging, it's not only that ping. A family member a town over routes through another NY router and gets 21.

- CT here too.

If the problem remains after a few days, I'll post a traceroute, I forget the syntax for that command, tracert or something...

Go to Command Prompt(Make sure you run it as admin)

Do:
Tracert Dslreports.com > C:/Tracert.txt

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 --
Join Teams Helix and Discovery. Rest in Peace, Leonard David Smith, my best friend, you are missed badly! Rest in peace, Pop, glad our last years were good. Please pray for Colin, he has ependymoma, a brain cancer, donate to a children's Hospital.

Where did it go :P?

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 --
Join Teams Helix and Discovery. Rest in Peace, Leonard David Smith, my best friend, you are missed badly! Rest in peace, Pop, glad our last years were good. Please pray for Colin, he has ependymoma, a brain cancer, donate to a children's Hospital.

Are you trying to use code blocks or something on it? Just copy/paste it all out.

reply to Darknessfall
What the... It won't post it, is it being blocked? I copied and pasted, but it won't post here.

reply to Darknessfall
that's exactly WHAT I am doing.

reply to signmeuptoo

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 --
Join Teams Helix and Discovery. Rest in Peace, Leonard David Smith, my best friend, you are missed badly! Rest in peace, Pop, glad our last years were good. Please pray for Colin, he has ependymoma, a brain cancer, donate to a children's Hospital.

I'll just post out mine lol. Tell me where yours is different.

Tracing route to Dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 * * * Request timed out.
3 11 ms 7 ms 9 ms te-3-2-ur01.-----.ct.hartford.comcast.net [68.87.159.49]
4 15 ms 22 ms 11 ms be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
5 19 ms 15 ms 15 ms pos-1-5-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.73]
6 53 ms 47 ms 48 ms he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]
7 45 ms 43 ms 44 ms 173.167.58.26
8 45 ms 43 ms 44 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
9 45 ms 45 ms 44 ms vlan804.esd1.oct.nac.net [209.123.10.2]
10 43 ms 43 ms 45 ms www.dslreports.com [209.123.109.175]

Trace complete.

reply to signmeuptoo

Tracert.txt 858 bytes

Not exactly the same router as mine in NY but we both hit 46 ping at those NY routers. Welcome to the pings I had to deal with since getting service :P. Darn you NY routers !

reply to signmeuptoo
For your future reference, you usually need to put traceroute results inside code blocks as illustrated below (you need to to this because any "<" or ">" characters in the traceroute results will be interpreted as code, and will frequently cause problems when the post is viewed):

[code]
traceroute results
[/code]

When I do that for your traceroute results, the posted results look like this:

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms     2 ms  DD-WRT [192.168.1.1] 
  2     *        *        *     Request timed out.
  3    18 ms    14 ms     8 ms  te-7-1-ur02.waterbury.ct.hartford.comcast.net [68.85.143.193] 
  4    17 ms    18 ms    15 ms  be-53-ar01.chartford.ct.hartford.comcast.net [68.85.162.198] 
  5    20 ms    22 ms    19 ms  pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.69] 
  6    52 ms    47 ms    47 ms  he-2-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.201] 
  7    59 ms    49 ms    49 ms  173.167.58.26 
  8    45 ms    43 ms    43 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122] 
  9    44 ms    43 ms    45 ms  vlan804.esd1.oct.nac.net [209.123.10.2] 
 10    43 ms    44 ms    46 ms  www.dslreports.com [209.123.109.175] 
 
Trace complete.
 
 

Oh! Thank you!

I have been experiencing the same increase in ping from a little over 4 months ago. Pings jump up from ~11ms to the mid 40s once it hits 40 ms 47 ms 35 ms cr01.newyork.ny.ibone.comcast.net [68
86.93.33].

reply to signmeuptoo
Latency for you guys in the NE seems to be a little higher than I would like but is still considered acceptable. I'm further away in Detroit and my ping is lower. And my packets go to Chicago first.

traceroute to dslreports.com (209.123.109.175), 64 hops max, 72 byte packets
 1  10.66.122.1 (10.66.122.1)  1.774 ms  1.314 ms  1.009 ms
 2  71.205.80.1 (71.205.80.1)  28.444 ms  28.817 ms  13.684 ms
 3  te-8-3-ur02.birmingham.mi.michigan.comcast.net (68.85.48.41)  11.050 ms  9.232 ms  14.438 ms
 4  te-9-2-ur03.birmingham.mi.michigan.comcast.net (68.87.190.206)  11.132 ms  9.042 ms  10.488 ms
 5  te-0-2-0-4-ar01.pontiac.mi.michigan.comcast.net (68.87.190.210)  20.801 ms  21.339 ms  11.867 ms
 6  he-4-5-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.90.221)  21.402 ms  23.620 ms  24.346 ms
 7  he-4-4-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.88.145)  39.213 ms  44.832 ms  35.741 ms
 8  173.167.58.26 (173.167.58.26)  43.648 ms  35.909 ms  38.750 ms
 9  0.e1-4.tbr1.oct.nac.net (209.123.10.122)  36.059 ms  36.238 ms  35.128 ms
10  vlan804.esd1.oct.nac.net (209.123.10.2)  36.963 ms  37.348 ms  38.403 ms
11  www.dslreports.com (209.123.109.175)  35.919 ms  35.793 ms  37.051 ms