Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Colt44 on February 15, 2012, 10:32:34 PM
-
Skuzzy...
Need some help brother.... I lost cable for about three weeks. They Dug everybodys yard up on the block and its back working... but now I think Im getting packet loss somewhere down the line...I think Im getting 100 % loss at hop 13. Anything you can help with?
Target Name: www.hitechcreations.com
IP: 70.85.193.18
Date/Time: 2/15/2012 11:08:00 PM to 2/15/2012 11:26:16 PM
1 0 ms N/A 0 ms 0 ms 0 ms 0 ms 0 ms N/A 0 ms 0 ms [10.0.1.1]
2 19 ms N/A 26 ms 25 ms 33 ms 27 ms 32 ms N/A 31 ms 21 ms [174.57.130.1]
3 7 ms N/A 7 ms 8 ms 9 ms 7 ms 8 ms N/A 8 ms 10 ms te-9-4-ur01.mayslanding.nj.panjde.comcast.net [68.86.155.5]
4 8 ms N/A 10 ms 8 ms 9 ms 8 ms 8 ms N/A 8 ms 9 ms te-8-3-ar01.absecon.nj.panjde.comcast.net [68.86.210.46]
5 N/A N/A N/A N/A N/A N/A N/A N/A N/A 11 ms xe-2-1-1-0-ar03.audubon.nj.panjde.comcast.net [68.85.63.197]
6 N/A N/A N/A N/A N/A N/A N/A N/A N/A 16 ms pos-3-7-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.149]
7 N/A N/A 17 ms N/A N/A 14 ms 15 ms N/A N/A 14 ms pos-1-2-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.86.74]
8 15 ms N/A 64 ms N/A 14 ms N/A 14 ms N/A N/A 15 ms ae15.bbr02.eq01.wdc02.network layer.com [75.149.228.94]
9 15 ms N/A 14 ms 14 ms 14 ms 14 ms N/A N/A N/A 15 ms ae7.bbr02.tl01.nyc01.networkl ayer.com [173.192.18.177]
10 N/A N/A 28 ms 27 ms 27 ms N/A 29 ms N/A N/A 34 ms ae0.bbr01.tl01.atl01.networkl ayer.com [173.192.18.153]
11 N/A N/A N/A N/A 55 ms N/A 56 ms N/A 56 ms 57 ms ae20.bbr01.eq01.dal03.network layer.com [173.192.18.136]
12 49 ms N/A N/A 48 ms N/A 47 ms 48 ms N/A N/A 49 ms po32.dsr02.dllstx3.networklay er.com [173.192.18.231]
13 * N/A * * * * * N/A * * [-]
14 N/A N/A 48 ms 48 ms 49 ms N/A 48 ms N/A 51 ms 49 ms po2.car03.dllstx5.networklaye r.com [70.87.254.22]
15 48 ms N/A 56 ms 56 ms 49 ms 49 ms 56 ms N/A 56 ms 57 ms 12.c1.5546.static.theplanet.c om [70.85.193.18]
Ping statistics for www.hitechcreations.com
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Round Trip Times: Minimum = 48ms, Maximum = 57ms, Average = 53ms
-
Looks like there are issues from the very beginning. You need to contact Comcast about it and show them your trace.
-
That is the right IP address to ping, Correct? Someone said to ping the following IP for a better idea. More importantly...what does a good plot look like?
Target Name: N/A
IP: 206.16.60.41
Date/Time: 2/16/2012 8:34:01 AM to 2/16/2012 8:35:31 AM
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [10.0.1.1]
2 25 ms 23 ms 23 ms 23 ms 31 ms 22 ms 23 ms 22 ms 32 ms 23 ms [174.57.130.1]
3 11 ms 9 ms 26 ms 11 ms 9 ms 10 ms 9 ms 10 ms 8 ms 12 ms te-9-4-ur01.mayslanding.nj.panjde.comcast.net [68.86.155.5]
4 9 ms 9 ms 8 ms 8 ms 9 ms 8 ms 8 ms 7 ms 8 ms 9 ms te-8-4-ar01.absecon.nj.panjde.comcast.net [68.85.159.130]
5 N/A 13 ms N/A N/A N/A N/A N/A N/A N/A 88 ms xe-15-0-0-0-ar03.plainfield.nj.panjde.comcast.net [68.85.62.242]
6 N/A N/A N/A N/A N/A 14 ms N/A N/A N/A 17 ms pos-3-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.173]
7 15 ms N/A 17 ms N/A 15 ms 16 ms 16 ms N/A 16 ms 16 ms pos-0-4-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.146]
8 15 ms N/A N/A N/A 16 ms N/A N/A N/A 15 ms 17 ms [192.205.37.41]
9 N/A N/A N/A N/A N/A 55 ms N/A N/A N/A 55 ms cr2.wswdc.ip.att.net [12.122.134.186]
10 54 ms 54 ms N/A 56 ms 56 ms 55 ms N/A 54 ms 55 ms 53 ms cr2.wswdc.ip.att.net [12.122.3.38]
11 N/A N/A N/A N/A N/A N/A 56 ms 56 ms 56 ms 57 ms cr1.attga.ip.att.net [12.122.1.173]
12 N/A N/A 117 ms 52 ms 52 ms 51 ms 50 ms 50 ms 181 ms 51 ms ggr1.dlstx.ip.att.net [12.122.138.1]
13 N/A 52 ms N/A 52 ms N/A 54 ms N/A N/A N/A 52 ms [12.122.251.66]
14 N/A N/A N/A N/A N/A N/A N/A N/A N/A 54 ms [12.122.251.66]
15 53 ms 50 ms 51 ms 51 ms 52 ms 52 ms 52 ms 51 ms 51 ms 51 ms [206.16.60.41]
Ping statistics for 206.16.60.41
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 50ms, Maximum = 53ms, Average = 51ms
-
That IP is just fine to use. And that latest trace still shows a ton of issues in the Comcast network.
-
<snip>More importantly...what does a good plot look like?
<snip>
Those N/As are not good and neither are the ***s. Once you get somthing like that in a trace, the rest of the numbers don't matter too much.
Nice low, or more importantly, consistant numbers are good.
-
I get >1ms on all my hops until I hit some AT&T lines, then it's 50-150ms. *Grumble* Stupid companies and their crap infrastructure. AT&T from LA to Texas is crap.