Packet Loss Issue.

jhouse0386 · Jan 22, 2014

So to start over the past week I have been getting random packet loss. I never fully drop connection but the packet loss causes massive lag in any gaming or VOIP I am doing and only started recently.

My last 5 tests recently on pingtest.net

.
C:\Users\jHouse>tracert www.yahoo.com

Tracing route to www.yahoo.com [98.139.183.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 8 ms 7 ms 14 ms 10.112.192.1
3 8 ms 7 ms 8 ms static-206-53-95-138.cpe.metrocast.net [206.53.9
5.138]
4 7 ms 7 ms 7 ms static-206-53-95-3.cpe.metrocast.net [206.53.95.
3]
5 25 ms 23 ms 24 ms ten10-4.ur1.rochester.nh.metrocast.net [65.175.1
42.201]
6 17 ms 17 ms 17 ms TBD-65-175-128-2.metrocast.net [65.175.128.2]
7 18 ms 18 ms * te0-7-0-5.ccr22.bos01.atlas.cogentco.com [38.122
.126.73]
8 23 ms 23 ms 23 ms be2097.mpd22.jfk02.atlas.cogentco.com [154.54.30
.117]
9 29 ms 31 ms 30 ms be2151.mpd22.dca01.atlas.cogentco.com [154.54.40
.73]
10 29 ms 31 ms 30 ms be2112.ccr41.iad02.atlas.cogentco.com [154.54.5.
233]
11 32 ms 30 ms 31 ms te2-7.ccr01.iad01.atlas.cogentco.com [154.54.31.
226]
12 30 ms 30 ms 31 ms yahoo.iad01.atlas.cogentco.com [154.54.13.166]
13 30 ms 32 ms 31 ms ae-6.pat2.dce.yahoo.com [216.115.102.176]
14 57 ms 77 ms 71 ms ae-4.pat2.che.yahoo.com [216.115.101.145]
15 52 ms 55 ms 60 ms ae-0.pat2.bfy.yahoo.com [216.115.97.204]
16 68 ms 49 ms 61 ms ae-4.pat1.bfz.yahoo.com [216.115.97.211]
17 55 ms 52 ms 53 ms po16.bas1-3-yst.bf1.yahoo.com [98.139.130.5]
18 60 ms 66 ms 68 ms xe-9-0-0.clr1-a-gdc.bf1.yahoo.com [98.139.232.10
1]
19 59 ms 79 ms 56 ms po-15.bas2-7-prd.bf1.yahoo.com [98.139.129.243]

20 63 ms 63 ms * po-15.bas2-7-prd.bf1.yahoo.com [98.139.129.243]

21 63 ms 73 ms 62 ms ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]

Trace complete.

C:\Users\jHouse>tracert www.yahoo.com

Tracing route to www.yahoo.com [98.139.183.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 7 ms 7 ms 7 ms 10.112.192.1
3 14 ms 25 ms 11 ms static-206-53-95-138.cpe.metrocast.net [206.53.9
5.138]
4 7 ms 7 ms 7 ms static-206-53-95-3.cpe.metrocast.net [206.53.95.
3]
5 25 ms 24 ms 23 ms ten10-4.ur1.rochester.nh.metrocast.net [65.175.1
42.201]
6 24 ms 24 ms 24 ms TBD-65-175-128-2.metrocast.net [65.175.128.2]
7 17 ms 17 ms 18 ms te0-7-0-5.ccr22.bos01.atlas.cogentco.com [38.122
.126.73]
8 23 ms 23 ms 24 ms be2096.ccr22.jfk02.atlas.cogentco.com [154.54.30
.41]
9 30 ms 29 ms 29 ms be2149.ccr22.dca01.atlas.cogentco.com [154.54.31
.125]
10 30 ms 30 ms 31 ms be2112.ccr41.iad02.atlas.cogentco.com [154.54.5.
233]
11 116 ms 223 ms 203 ms te2-1.ccr02.iad01.atlas.cogentco.com [154.54.31.
234]
12 30 ms 31 ms 78 ms yahoo.iad01.atlas.cogentco.com [154.54.12.102]
13 30 ms 30 ms 29 ms ae-6.pat2.dce.yahoo.com [216.115.102.176]
14 58 ms 35 ms 60 ms ae-0.pat2.nyc.yahoo.com [216.115.100.93]
15 61 ms 56 ms 52 ms ae-5.pat1.bfz.yahoo.com [216.115.96.65]
16 72 ms 46 ms 55 ms ae-4.pat1.bfz.yahoo.com [216.115.97.211]
17 73 ms 55 ms 56 ms po16.bas1-3-yst.bf1.yahoo.com [98.139.130.5]
18 56 ms 58 ms 53 ms UNKNOWN-98-139-128-X.yahoo.com [98.139.128.77]
19 67 ms 67 ms 56 ms po-15.bas2-7-prd.bf1.yahoo.com [98.139.129.243]

20 64 ms 53 ms 71 ms po-15.bas2-7-prd.bf1.yahoo.com [98.139.129.243]

21 56 ms 45 ms 62 ms ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]

Trace complete.

C:\Users\jHouse>tracert www.yahoo.com

Tracing route to www.yahoo.com [98.139.183.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 7 ms 7 ms 7 ms 10.112.192.1
3 7 ms 8 ms 7 ms static-206-53-95-138.cpe.metrocast.net [206.53.9
5.138]
4 7 ms 7 ms 7 ms static-206-53-95-3.cpe.metrocast.net [206.53.95.
3]
5 14 ms 14 ms 23 ms ten10-4.ur1.rochester.nh.metrocast.net [65.175.1
42.201]
6 25 ms 25 ms 23 ms TBD-65-175-128-2.metrocast.net [65.175.128.2]
7 18 ms 17 ms 16 ms te0-7-0-5.ccr22.bos01.atlas.cogentco.com [38.122
.126.73]
8 26 ms 23 ms 24 ms be2096.ccr22.jfk02.atlas.cogentco.com [154.54.30
.41]
9 30 ms 29 ms 29 ms be2151.mpd22.dca01.atlas.cogentco.com [154.54.40
.73]
10 32 ms 32 ms 31 ms be2112.ccr41.iad02.atlas.cogentco.com [154.54.5.
233]
11 133 ms 30 ms 31 ms te1-2.ccr02.iad01.atlas.cogentco.com [154.54.31.
194]
12 32 ms 31 ms 34 ms yahoo.iad01.atlas.cogentco.com [154.54.12.102]
13 34 ms 31 ms 29 ms ae-6.pat2.dce.yahoo.com [216.115.102.176]
14 42 ms 37 ms 36 ms ae-0.pat2.nyc.yahoo.com [216.115.100.93]
15 54 ms 105 ms 63 ms ae-3.pat1.bfy.yahoo.com [216.115.96.117]
16 48 ms 77 ms 57 ms ae-3.msr2.bf1.yahoo.com [216.115.100.31]
17 52 ms 56 ms 55 ms ae-4.msr1.bf1.yahoo.com [216.115.100.25]
18 55 ms 52 ms 53 ms unknown-98-139-128-x.yahoo.com [98.139.128.77]
19 67 ms 58 ms 68 ms unknown-98-139-128-x.yahoo.com [98.139.128.77]
20 47 ms 71 ms 71 ms po-15.bas2-7-prd.bf1.yahoo.com [98.139.129.243]

21 68 ms 51 ms 59 ms ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]

Trace complete.

C:\Users\jHouse>tracert www.yahoo.com

Tracing route to www.yahoo.com [98.139.183.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 * * 7 ms 10.112.192.1
3 * 8 ms 7 ms static-206-53-95-138.cpe.metrocast.net [206.53.9
5.138]
4 7 ms 7 ms 7 ms static-206-53-95-3.cpe.metrocast.net [206.53.95.
3]
5 14 ms 15 ms 24 ms ten10-4.ur1.rochester.nh.metrocast.net [65.175.1
42.201]
6 22 ms 24 ms 24 ms tbd-65-175-128-2.metrocast.net [65.175.128.2]
7 18 ms 17 ms 18 ms te0-7-0-5.ccr22.bos01.atlas.cogentco.com [38.122
.126.73]
8 23 ms 23 ms 23 ms be2096.ccr22.jfk02.atlas.cogentco.com [154.54.30
.41]
9 30 ms 30 ms 29 ms be2149.ccr22.dca01.atlas.cogentco.com [154.54.31
.125]
10 * 31 ms 31 ms be2112.ccr41.iad02.atlas.cogentco.com [154.54.5.
233]
11 43 ms 29 ms 48 ms te2-1.ccr01.iad01.atlas.cogentco.com [154.54.31.
162]
12 31 ms 31 ms * yahoo.iad01.atlas.cogentco.com [154.54.12.102]
13 * 95 ms 59 ms ae-6.pat2.dce.yahoo.com [216.115.102.176]
14 50 ms 37 ms 37 ms ae-0.pat2.nyc.yahoo.com [216.115.100.93]
15 56 ms 54 ms 216 ms ae-5.pat1.bfz.yahoo.com [216.115.96.65]
16 131 ms 72 ms 147 ms ae-4.pat2.bfz.yahoo.com [216.115.97.207]
17 54 ms 60 ms 56 ms po16.bas1-3-yst.bf1.yahoo.com [98.139.130.5]
18 54 ms 53 ms 55 ms unknown-98-139-128-x.yahoo.com [98.139.128.77]
19 75 ms 59 ms 57 ms po-15.bas2-7-prd.bf1.yahoo.com [98.139.129.243]

20 46 ms 63 ms 51 ms ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]

Trace complete.

C:\Users\jHouse>tracert www.yahoo.com

Tracing route to www.yahoo.com [98.139.183.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 8 ms 7 ms 7 ms 10.112.192.1
3 56 ms 8 ms 9 ms static-206-53-95-138.cpe.metrocast.net [206.53.9
5.138]
4 7 ms 7 ms 7 ms static-206-53-95-3.cpe.metrocast.net [206.53.95.
3]
5 26 ms 23 ms 22 ms ten10-4.ur1.rochester.nh.metrocast.net [65.175.1
42.201]
6 19 ms 23 ms 25 ms tbd-65-175-128-2.metrocast.net [65.175.128.2]
7 18 ms 19 ms 17 ms te0-7-0-5.ccr22.bos01.atlas.cogentco.com [38.122
.126.73]
8 23 ms 23 ms 24 ms be2096.ccr22.jfk02.atlas.cogentco.com [154.54.30
.41]
9 29 ms 30 ms 28 ms be2149.ccr22.dca01.atlas.cogentco.com [154.54.31
.125]
10 31 ms 30 ms 31 ms be2177.ccr41.iad02.atlas.cogentco.com [154.54.41
.205]
11 234 ms 210 ms 67 ms te2-1.ccr02.iad01.atlas.cogentco.com [154.54.31.
234]
12 50 ms 30 ms 31 ms yahoo.iad01.atlas.cogentco.com [154.54.12.102]
13 32 ms 31 ms 31 ms ae-6.pat2.dce.yahoo.com [216.115.102.176]
14 59 ms 35 ms 59 ms ae-4.pat2.che.yahoo.com [216.115.101.145]
15 46 ms 47 ms 45 ms ae-5.pat1.bfz.yahoo.com [216.115.96.65]
16 58 ms 73 ms 46 ms ae-4.msr2.bf1.yahoo.com [216.115.100.73]
17 61 ms 54 ms 84 ms ae-4.msr2.bf1.yahoo.com [216.115.100.73]
18 54 ms 68 ms 68 ms xe-9-0-0.clr1-a-gdc.bf1.yahoo.com [98.139.232.10
1]
19 375 ms 67 ms 58 ms po-15.bas2-7-prd.bf1.yahoo.com [98.139.129.243]

20 * 72 ms 47 ms ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]

Trace complete.

C:\Users\jHouse>

C:\Users\jHouse>tracert www.yahoo.com

Tracing route to www.yahoo.com [98.139.183.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 7 ms 7 ms 7 ms 10.112.192.1
3 8 ms 6 ms 7 ms static-206-53-95-138.cpe.metrocast.net [206.53.9
5.138]
4 10 ms 7 ms 7 ms static-206-53-95-3.cpe.metrocast.net [206.53.95.
3]
5 * 15 ms 24 ms ten10-4.ur1.rochester.nh.metrocast.net [65.175.1
42.201]
6 20 ms 23 ms 24 ms tbd-65-175-128-2.metrocast.net [65.175.128.2]
7 17 ms 17 ms 17 ms te0-7-0-5.ccr22.bos01.atlas.cogentco.com [38.122
.126.73]
8 26 ms 34 ms 31 ms be2097.mpd22.jfk02.atlas.cogentco.com [154.54.30
.117]
9 32 ms 29 ms 29 ms be2149.ccr22.dca01.atlas.cogentco.com [154.54.31
.125]
10 31 ms 31 ms 31 ms be2112.ccr41.iad02.atlas.cogentco.com [154.54.5.
233]
11 166 ms 212 ms 195 ms te1-2.ccr02.iad01.atlas.cogentco.com [154.54.31.
194]
12 30 ms 37 ms 31 ms yahoo.iad01.atlas.cogentco.com [154.54.13.166]
13 31 ms 30 ms 31 ms ae-6.pat2.dce.yahoo.com [216.115.102.176]
14 37 ms 37 ms 51 ms ae-4.pat2.che.yahoo.com [216.115.101.145]
15 56 ms 54 ms 47 ms ae-2.pat2.bfz.yahoo.com [216.115.100.74]
16 65 ms 47 ms 59 ms ae-3.msr2.bf1.yahoo.com [216.115.100.31]
17 52 ms 84 ms 61 ms ae-4.msr1.bf1.yahoo.com [216.115.100.25]
18 111 ms 62 ms 67 ms po16.bas1-3-yst.bf1.yahoo.com [98.139.130.5]
19 57 ms 56 ms 57 ms po-15.bas2-7-prd.bf1.yahoo.com [98.139.129.243]

20 49 ms 65 ms 60 ms ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]

Trace complete.

C:\Users\jHouse>tracert www.yahoo.com

Tracing route to www.yahoo.com [98.139.183.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 11 ms 8 ms 7 ms 10.112.192.1
3 8 ms 8 ms 7 ms static-206-53-95-138.cpe.metrocast.net [206.53.9
5.138]
4 8 ms 7 ms 39 ms static-206-53-95-3.cpe.metrocast.net [206.53.95.
3]
5 14 ms 22 ms 23 ms ten10-4.ur1.rochester.nh.metrocast.net [65.175.1
42.201]
6 16 ms 24 ms 24 ms tbd-65-175-128-2.metrocast.net [65.175.128.2]
7 17 ms 101 ms * te0-7-0-5.ccr22.bos01.atlas.cogentco.com [38.122
.126.73]
8 23 ms 24 ms 24 ms be2097.mpd22.jfk02.atlas.cogentco.com [154.54.30
.117]
9 29 ms 30 ms 31 ms be2151.mpd22.dca01.atlas.cogentco.com [154.54.40
.73]
10 31 ms 31 ms 31 ms be2177.ccr41.iad02.atlas.cogentco.com [154.54.41
.205]
11 31 ms 29 ms 31 ms te2-7.ccr02.iad01.atlas.cogentco.com [154.54.31.
214]
12 32 ms 31 ms 31 ms yahoo.iad01.atlas.cogentco.com [154.54.12.102]
13 71 ms 88 ms 104 ms ae-6.pat2.dce.yahoo.com [216.115.102.176]
14 96 ms 57 ms 36 ms ae-0.pat2.nyc.yahoo.com [216.115.100.93]
15 61 ms 48 ms 60 ms ae-0.pat2.bfy.yahoo.com [216.115.97.204]
16 49 ms 51 ms 50 ms ae-3.msr1.bf1.yahoo.com [216.115.100.29]
17 63 ms 54 ms 54 ms xe-9-0-0.clr1-a-gdc.bf1.yahoo.com [98.139.232.10
1]
18 60 ms 56 ms 78 ms po16.bas1-3-yst.bf1.yahoo.com [98.139.130.5]
19 56 ms 62 ms 68 ms unknown-98-139-128-x.yahoo.com [98.139.128.77]
20 59 ms 65 ms 56 ms ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24]

Trace complete.

Some Trace routes I have ran recently.

I mean if there is any other information I could provide let me know.

I called my ISP last night they said that my area has had intermittent connection issues the past 2 days they have had techs working on it but my problem has been going on longer then just 2 days.

My modem log from this morning too.

ahnilated · Jan 22, 2014

Your ISP will probably never tell you the 100% truth. Just be happy they know about it and are doing something. A number of them will deny it is even their issue.

jhouse0386 · Jan 22, 2014

ahnilated :

So you think it is on my ISPs side then? Even though I have been having the problem longer then they have admitted having one?

I mean you dont see anything in the trace routes or logs that would indicate its on my side?

ahnilated · Jan 22, 2014

It is probably a router or something on their end that is causing the issue.

Do a constant ping to the location you are trying to get to for 1 hr. See how many dropped packets you get. Then you can slowly work backwards to see where the issue really hits.

jhouse0386 · Jan 22, 2014

ahnilated :

How can I provide more information that is needed? What pings should I be running? What commands.

ahnilated · Jan 22, 2014

You can do:

ping -t XXX.XXX.XXX.XXX (this will ping that address until you stop it.)
ping -n XXXX (this will ping for a number of counts)

you can look this up by typing ping /? in a command prompt window.

jhouse0386 · Jan 22, 2014

ahnilated :

I will run a ping to my isp's website for a while then post the results here.

jhouse0386 · Jan 22, 2014

C:\Users\jHouse>ping -t www.metrocast.com

Pinging mymetrocast.com [69.26.100.36] with 32 bytes of data:
Reply from 69.26.100.36: bytes=32 time=21ms TTL=117
Reply from 69.26.100.36: bytes=32 time=23ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=21ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=26ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=21ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=22ms TTL=117
Reply from 69.26.100.36: bytes=32 time=23ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=22ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=22ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=22ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=21ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=21ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=22ms TTL=117
Reply from 69.26.100.36: bytes=32 time=24ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=26ms TTL=117
Reply from 69.26.100.36: bytes=32 time=23ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=28ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=27ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=21ms TTL=117
Reply from 69.26.100.36: bytes=32 time=29ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=21ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=55ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=21ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=26ms TTL=117
Reply from 69.26.100.36: bytes=32 time=22ms TTL=117
Reply from 69.26.100.36: bytes=32 time=23ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Request timed out.
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=26ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=21ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=28ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=25ms TTL=117
Reply from 69.26.100.36: bytes=32 time=25ms TTL=117
Reply from 69.26.100.36: bytes=32 time=23ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Request timed out.
Reply from 69.26.100.36: bytes=32 time=27ms TTL=117
Request timed out.
Request timed out.
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Request timed out.
Reply from 69.26.100.36: bytes=32 time=32ms TTL=117
Reply from 69.26.100.36: bytes=32 time=205ms TTL=117
Reply from 69.26.100.36: bytes=32 time=26ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Reply from 69.26.100.36: bytes=32 time=20ms TTL=117
Request timed out.
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=978ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=27ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=22ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Request timed out.
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=2773ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=18ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=19ms TTL=117
Reply from 69.26.100.36: bytes=32 time=26ms TTL=117

Ping statistics for 69.26.100.36:
Packets: Sent = 148, Received = 141, Lost = 7 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 2773ms, Average = 48ms
Control-C
^C
C:\Users\jHouse>

This was a small sample size.

ahnilated · Jan 22, 2014

Ok, now that shows you that some of your packets are not making it back to you. What you can now do being you have your trace routes is ping each hop along the way to find out where it is dropping. That information you could pass along to your ISP to let them know where it is failing. It sounded though that they knew there was an issue already.

jhouse0386 · Jan 22, 2014

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\jHouse>ping -t 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=17ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=9ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.2.1:
Packets: Sent = 132, Received = 132, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 17ms, Average = 0ms
Control-C
^C
C:\Users\jHouse>

So. I did it to what im guessing is my router. no loss at all a couple minor spikes... is that normal? I noticed 2 out of the 132 pings were 18 and 9 the rest were less than 1.

jhouse0386 · Jan 22, 2014

^C
C:\Users\jHouse>ping -t 10.112.192.1

Pinging 10.112.192.1 with 32 bytes of data:
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=11ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=9ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=9ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Request timed out.
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Request timed out.
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=51ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=12ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=11ms TTL=254
Reply from 10.112.192.1: bytes=32 time=18ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=11ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=48ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=9ms TTL=254
Reply from 10.112.192.1: bytes=32 time=10ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=475ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=18ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Request timed out.
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=9ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Request timed out.
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Request timed out.
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=10ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=9ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=9ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=9ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=34ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=910ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Request timed out.
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=8ms TTL=254
Reply from 10.112.192.1: bytes=32 time=6ms TTL=254
Reply from 10.112.192.1: bytes=32 time=50ms TTL=254
Reply from 10.112.192.1: bytes=32 time=12ms TTL=254
Reply from 10.112.192.1: bytes=32 time=7ms TTL=254

Ping statistics for 10.112.192.1:
Packets: Sent = 159, Received = 153, Lost = 6 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 910ms, Average = 17ms

Pinged the 2nd one and found some issues. What does the 2nd one represent?

what is 10.112.192.1

and why am i dropping packets and having ping spikes while pinging it.

ahnilated · Jan 22, 2014

Well that could be your connection from your modem to your ISP. If you only have one networking device between your computer and the modem it would make me think it was your connection to the ISP. Now that could be the box on the outside of your house (if there is one), or the box on the corner of your lot or anywhere to your ISP.

The reasons you are dropping packets could be a bad card or water in the line to a shield on a fiber optic cable being off... They would have to test for you and fix it.

ex_bubblehead · Jan 22, 2014

Bear in mind that on most routers ICMP is given the lowest possible priority, and that when the router gets busy, the first thing dropped is the useless echo requests.

jhouse0386 · Jan 22, 2014

ahnilated :

If it were the box outside or at the corner of my lot or something in the line. Wouldn't that be noticeable in the power/signal levels?

ahnilated · Jan 22, 2014

That is possible but hard to tell. I would say just talk with your ISP and let them fix it for you. 4% packet loss isn't very bad compared to some I have seen.

Unless you are a line tech you won't really know if the signal is good or bad with the numbers given.

jhouse0386 · Jan 22, 2014

Signal to Noise Ratio 39 dB

Power Level 0 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

Power Level 43 dBmV

jhouse0386 · Jan 22, 2014

at this point im trying to diagnose this myself because they say if they have someone come out and find something on my end because i own all the equipment they are gonna charge me for a service call.

ahnilated · Jan 22, 2014

Well I am not a line tech either to be able to help you that far.

ex_bubblehead · Jan 22, 2014

jhouse0386 :

Absolutely nothing wrong with those numbers.

jhouse0386 · Jan 22, 2014

ex_bubblehead :

I know.

From what I have read and what I have heard over the phone they are good numbers.

So again I am curious to where my problem is.

jhouse0386 · Jan 23, 2014

My ISPs opinion on it is. If its a problem in the first 2 hops then its internal equipment. If I bypass my router and I am still having this problem then they imagine it is the modem. If the modem is suspect they suggested I come get one of their 5 dollar rental modems to swap mine out and try theirs and see if it makes the issue better. If it doesn't they suggest having a service call.

ahnilated · Jan 23, 2014

Or go somewhere and get a replacement modem and try it out and if it works then keep it, if it doesn't take it back.

jhouse0386 · Jan 23, 2014

ahnilated :

Yeah. dont have 80-150 dollars to drop on a new modem right now. Rather pay the 5. if it works ill buy my own modem next payday.

I hope to god it works and it is the modem. I just want to fix the issue and be able to play my games and such.

Packet Loss Issue.

Honorable

Splendid

Honorable

Splendid

Honorable

Splendid

Honorable

Honorable

Splendid

Honorable

Honorable

Splendid

Titan

Honorable

Splendid

Honorable

Honorable

Splendid

Titan

Honorable

Honorable

Splendid

Honorable

Share this page