Ping alternates from 90 and 500 every 7-8 minutes

cjbranden

Honorable
Dec 11, 2013
6
0
10,510
Hi there,
been having this trouble for some time now. I have Frontier internet service providing 1.75-2.25Mbps download speeds and have contacted them 6 times with little progress. The problem: my "good" ping-90, download-2.25Mbps, upload 0.25Mps runs for 7-8 minutes then I get ping-500, download 0.9Mbps, upload 0.1Mbps for 7-8 minutes. This happens like clockwork on both of my laptops. The modem's lights do not change during these times. I have full-scanned both computer with 2 different anti-virus/spyware programs with no threats detected. The Frontier technician came by yesterday and said my lines were good and he replaced the modem. This actually seemed to eradicate the fluctuating for about 6-7hours, but it then return. Before the modem change, this problem happens at the same time intervals but my ping-2000, download-0.3Mbps, upload-0.08. I, nor my ISP, seems to know what to do. All this data was gathered on an ethernet connection (I tried two different cords as well if that provides any additional helpful info).
 

cjbranden

Honorable
Dec 11, 2013
6
0
10,510
I ran a tracert through tracert.com and turned up these results on a "good" cycle.

1: s6.hostlocal.com (207.158.52.56) 0.111ms pmtu 1500
1: 207.158.52.125 (207.158.52.125) 0.514ms
1: 207.158.52.125 (207.158.52.125) 0.465ms
2: vlan127.car1.SanDiego1.Level3.net (4.79.33.229) 0.834ms
3: ae-5-5.ebr1.LosAngeles1.Level3.net (4.69.133.206) 11.084ms asymm 10
4: ae-61-61.csw1.LosAngeles1.Level3.net (4.69.137.2) 10.858ms asymm 10
5: ae-73-73.ebr3.LosAngeles1.Level3.net (4.69.137.37) 11.039ms asymm 10
6: ae-3-3.ebr1.SanJose1.Level3.net (4.69.132.9) 11.087ms asymm 10
7: ae-61-61.csw1.SanJose1.Level3.net (4.69.153.2) 10.994ms asymm 9
8: ae-12-70.car2.SanJose2.Level3.net (4.69.152.76) 11.194ms
9: CITIZENS-CO.car2.SanJose2.Level3.net (4.59.4.82) 10.973ms asymm 10
10: ae2---0.cor02.plal.ca.frontiernet.net (74.40.3.169) 86.326ms asymm 15
11: ae1---0.cor01.slkc.ut.frontiernet.net (74.40.5.62) 69.555ms asymm 14
12: ae3---0.cor02.chcg.il.frontiernet.net (74.40.5.57) 69.922ms asymm 13
13: xe--0-2-0---0.car01.waus.wi.frontiernet.net (74.40.4.30) 68.618ms asymm 9
14: ge--0-0-0---0.arr01.rhnl.wi.frontiernet.net (74.42.150.86) 69.645ms asymm 11
15: 74.40.57.86 (74.40.57.86) 67.376ms asymm 11
16:

On a bad cycle:

1: s6.hostlocal.com (207.158.52.56) 0.118ms pmtu 1500
1: 207.158.52.125 (207.158.52.125) 0.561ms
1: 207.158.52.125 (207.158.52.125) 0.488ms
2: vlan127.car1.SanDiego1.Level3.net (4.79.33.229) 1.040ms
3: ae-5-5.ebr1.LosAngeles1.Level3.net (4.69.133.206) 11.083ms asymm 10
4: ae-91-91.csw4.LosAngeles1.Level3.net (4.69.137.14) 10.909ms asymm 10
5: ae-83-83.ebr3.LosAngeles1.Level3.net (4.69.137.41) 10.856ms asymm 10
6: ae-3-3.ebr1.SanJose1.Level3.net (4.69.132.9) 10.894ms asymm 10
7: ae-71-71.csw2.SanJose1.Level3.net (4.69.153.6) 10.846ms asymm 9
8: ae-32-90.car2.SanJose2.Level3.net (4.69.152.204) 11.252ms
9: CITIZENS-CO.car2.SanJose2.Level3.net (4.59.4.82) 10.977ms asymm 10
10: ae2---0.cor02.plal.ca.frontiernet.net (74.40.3.169) 67.321ms asymm 15
11: ae1---0.cor01.slkc.ut.frontiernet.net (74.40.5.62) 67.324ms asymm 14
12: ae3---0.cor02.chcg.il.frontiernet.net (74.40.5.57) 69.917ms asymm 13
13: xe--0-2-0---0.car01.waus.wi.frontiernet.net (74.40.4.30) 68.457ms asymm 9
14: ge--0-0-0---0.arr01.rhnl.wi.frontiernet.net (74.42.150.86) 69.553ms asymm 11
15: 74.40.57.86 (74.40.57.86) 67.657ms asymm 11
16:

I'm not sure if I performed the right action or have the right data to further troubleshoot.
 

dgingeri

Distinguished
What are you trying to ping? It shows the traffic getting routed from San Diego to Los Angeles to San Jose to Salt Lake City, Utah to Chicago to Wisconsin. (I don't know which city they're referring to with the code 'rhnl.') Are you trying to get to something in Wisconsin?
 

cjbranden

Honorable
Dec 11, 2013
6
0
10,510
When I'm testing my ping/download/upload, I'm using FrontierNet's speedtest. I live in northern Wisconsin the test runs through a server in Chicago, IL. tracert.com runs traceroute through a server in San Diego.
 

dgingeri

Distinguished
ok, so you're in wisconsin. It's weird that the tracert shows in opposite order. It's also kind of a weird format. It's easier to just run a "tracert speedtest.frontier.com" from the command line. That gives a little more readable data.
 

cjbranden

Honorable
Dec 11, 2013
6
0
10,510
Sorry, first time running a tracert before. Using the command line:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Corey>tracert chicago.il.speedtest.frontier.com

Tracing route to speedtest01.chcg.il.frontiernet.net [74.40.43.221]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms dslrouter.netgear.com [192.168.254.254]
2 286 ms 245 ms 205 ms 173-86-146-1.dsl1.rhnl.wi.frontiernet.net [173.8
6.146.1]
3 138 ms 124 ms 93 ms 74.40.57.85
4 274 ms * 909 ms ge--7-0-2---0.arr01.waus.wi.frontiernet.net [74.
42.150.85]
5 127 ms 116 ms 81 ms xe--10-1-0---0.cor02.chcg.il.frontiernet.net [74
.40.4.29]
6 * 969 ms * ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
42]
7 67 ms * 359 ms speedtest01.chcg.il.frontiernet.net [74.40.43.22
1]

Trace complete.

C:\Users\CoreThe last run was the bad cycle and there's a goof up in there.
 

cjbranden

Honorable
Dec 11, 2013
6
0
10,510
Sorry didn't realise till now it didn't paste the complete log. He's the results:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Corey>tracert chicago.il.speedtest.frontier.com

Tracing route to speedtest01.chcg.il.frontiernet.net [74.40.43.221]
over a maximum of 30 hops:
-Good-
1 <1 ms 1 ms 1 ms dslrouter.netgear.com [192.168.254.254]
2 200 ms 191 ms 202 ms 173-86-146-1.dsl1.rhnl.wi.frontiernet.net [173.8
6.146.1]
3 215 ms 181 ms 213 ms 74.40.57.85
4 282 ms 296 ms 302 ms ge--7-0-2---0.arr01.waus.wi.frontiernet.net [74.
42.150.85]
5 310 ms 265 ms 171 ms xe--10-1-0---0.cor02.chcg.il.frontiernet.net [74
.40.4.29]
6 309 ms * * ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
42]
7 1372 ms 1188 ms 511 ms speedtest01.chcg.il.frontiernet.net [74.40.43.22
1]

Trace complete.

-And the Bad-

C:\Users\Corey>tracert chicago.il.speedtest.frontier.com

Tracing route to speedtest01.chcg.il.frontiernet.net [74.40.43.221]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dslrouter.netgear.com [192.168.254.254]
2 570 ms * 269 ms 173-86-146-1.dsl1.rhnl.wi.frontiernet.net [173.8
6.146.1]
3 257 ms 253 ms 328 ms 74.40.57.85
4 * * 188 ms ge--7-0-2---0.arr01.waus.wi.frontiernet.net [74.
42.150.85]
5 316 ms 356 ms 408 ms xe--10-1-0---0.cor02.chcg.il.frontiernet.net [74
.40.4.29]
6 458 ms * 128 ms ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
42]
7 66 ms 66 ms 68 ms speedtest01.chcg.il.frontiernet.net [74.40.43.22
1]

Trace complete.

I can see it starts in Rhinelander, WI, then Wausau, WI, then Chicago, IL. It doesn't appear to change where it is pinging between tests.
 

dgingeri

Distinguished
Then the issue isn't in the routing outside your place. It must be in your place. For that, there is only a few parts to test: modem, router, computer. Since you tested with two computers and got the same issue, and you replaced the modem, that leaves only one thing that could be the problem: your Netgear router. Try a power cycle on that and see if behavior changes again like it did when you changed out the modem. If you get the same thing, works fine for a few hours and then the problem comes back, get a new router.