US Telco Support > Frontier Communications > [FiOS] Very high pings in pacific NW

[FiOS] Very high pings in pacific NW

stupid editor at this site is useless. sigh.

reply to Customer
Post your traceroute.

Mine looks like this:

Tracing route to frontier.com [66.133.172.205]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 6 ms 7 ms 6 ms static-50-53-160-1.bvtn.or.frontiernet.net [50.53.160.1]
3 8 ms 6 ms 7 ms 50.38.7.209
4 9 ms 7 ms 7 ms ae2---0.cor02.bvtn.or.frontiernet.net [74.40.1.181]
5 7 ms 9 ms 6 ms ae0---0.cor01.bvtn.or.frontiernet.net [74.40.1.185]
6 14 ms 12 ms 12 ms ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.221]
7 12 ms 11 ms 47 ms ae0---0.cor02.sttl.wa.frontiernet.net [74.40.3.138]
8 49 ms 51 ms 50 ms xe--11-0-0---0.cor01.mond.mn.frontiernet.net [74.40.5.45]
9 51 ms 52 ms 53 ms ae0---0.cor01.lkvl.mn.frontiernet.net [74.40.5.53]
10 62 ms 77 ms 62 ms ae4---0.cor01.chcg.il.frontiernet.net [74.40.5.50]
11 106 ms 74 ms 74 ms ae1---0.cor02.roch.ny.ny.frontiernet.net [74.40.5.21]
12 73 ms 74 ms 74 ms ge--0-0-0---0.car02.roch.ny.frontiernet.net [74.40.5.78]
13 74 ms 75 ms 74 ms 74.45.102.10
14 76 ms 78 ms 76 ms frontiertv.info [66.133.172.205]

(Why run a ping test to Corvallis? What does that have to do with reaching frontier.com?)
--
♬ Dragon of good fortune struggles with the trickster Fox ♬

reply to Customer

Tracing route to frontier.com [66.133.172.205]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 192.168.1.1
3 94 ms 109 ms 116 ms static-50-53-32-1.bvtn.or.frontiernet.net [50.53.32.1]
4 145 ms 144 ms 146 ms 50.38.7.93
5 217 ms 212 ms 212 ms ae2---0.cor02.bvtn.or.frontiernet.net [74.40.1.181]
6 224 ms 221 ms 219 ms ae0---0.cor01.bvtn.or.frontiernet.net [74.40.1.185]
7 220 ms 223 ms 227 ms ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.221]
8 221 ms 224 ms 222 ms ae0---0.cor02.sttl.wa.frontiernet.net [74.40.3.138]
9 261 ms 259 ms 254 ms xe--11-0-0---0.cor01.mond.mn.frontiernet.net [74.40.5.45]
10 258 ms 261 ms 259 ms ae0---0.cor01.lkvl.mn.frontiernet.net [74.40.5.53]
11 271 ms 279 ms 259 ms ae4---0.cor01.chcg.il.frontiernet.net [74.40.5.50]
12 285 ms 284 ms 292 ms ae1---0.cor02.roch.ny.ny.frontiernet.net [74.40.5.21]
13 283 ms 287 ms 286 ms ge--0-0-0---0.car02.roch.ny.frontiernet.net [74.40.5.78]
14 285 ms 289 ms 279 ms 74.45.102.10
15 281 ms 276 ms 282 ms frontiertv.info [66.133.172.205]

Trace complete.

Definitely a problem here:

reply to Customer
Called Frontier and found that a hard power-cycle resolves the issue temporarily. Unfortunately, it crops up again after a few hours; how is this possible? Is it a problem on my end?

Maybe your ONT is going bad. In any case, this is an issue for Frontier support to resolve with you.
--
♬ Dragon of good fortune struggles with the trickster Fox ♬

reply to Customer
I've noticed this issue every few months or so. A reboot solves it. Not sure what the root cause is. If you find out, post it

When I had similar issues with the router locking up frequently, I swapped out my router for a Linksys E4200 router, cloned the MAC address and didn't have to worry about it again (I fortunately have Ethernet drop-off). The Actiontec routers that Verizon used to offer prior to the take over were terrible. I don't know what they're handing out these days, but you can get a MOCCA compatable third party router if you're on Coax now too (Motorola has a few, for example) and have something where the software will get at least a couple of updates during its lifespan.