|
broncbob
Anon
2015-Mar-15 9:24 pm
[FiOS] Bad ping during peak, speed test is fineAnyone have slow downs in the beaverton, OR area?
I get perfect 100-ish ping every night during peak periods, never spikes or anything, it's just high. Come Saturday morning it's back down to 10-15ms. Gaming sucks, but the speeds are just fine, still get 25/25MB.
Tracing route to 192-69-96-54.valve.net [192.69.96.54] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 5 ms 4 ms 4 ms static-50-53-0-1.bvtn.or.frontiernet.net [50.53. 0.1] 3 4 ms 4 ms 4 ms 50-39-211-17.bvtn.or.frontiernet.net [50.39.211. 17] 4 77 ms 76 ms 76 ms ae2---0.cor01.bvtn.or.frontiernet.net [74.40.1.2 17] 5 76 ms 86 ms 79 ms ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.2 21] 6 90 ms 74 ms 76 ms ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.1 22] 7 69 ms 69 ms 69 ms six.zayo.com [206.81.80.19] 8 64 ms 61 ms 58 ms ae11.mpr2.sea1.us.zip.zayo.com [64.125.31.94] 9 58 ms 58 ms 56 ms 128.177.117.130.IPYX-094067-002-ZYO.zip.zayo.com [128.177.117.130] 10 * * * Request timed out. |
|
|
BVTNFIOS
Anon
2015-Mar-15 10:24 pm
Agreed, here is where it all starts going downhill a little. These are like this every night from say 6pm on. This is on a 25/25 plan as well. You can see where it all starts going down hill also.
4 57 ms 4 ms 4 ms ae8---0.car01.bvtn.or.frontiernet.net [74.40.70. 29] 5 153 ms 134 ms 132 ms ae2---0.cor01.bvtn.or.frontiernet.net [74.40.1.2 17] 6 156 ms 144 ms 139 ms ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.2 21] 7 149 ms 152 ms 154 ms ae0---0.cor02.sttl.wa.frontiernet.net [74.40.3.1 38] 8 128 ms 134 ms 134 ms xe--11-0-0---0.cor01.mond.mn.frontiernet.net [74 .40.5.45] 9 142 ms 139 ms 164 ms ae0---0.cor01.lkvl.mn.frontiernet.net [74.40.5.5 3] 10 126 ms 127 ms 124 ms ae4---0.cor01.chcg.il.frontiernet.net [74.40.5.5 0] 11 140 ms 139 ms 134 ms ae1---0.car01.ftwy.in.frontiernet.net [74.40.2.2 06] 12 140 ms 144 ms 142 ms 50.121.72.133 13 141 ms 147 ms 144 ms 50.121.72.196 14 138 ms 137 ms 137 ms 50.121.72.226 15 * * * Request timed out. 16 * * * Request timed out. 17 128 ms 129 ms 129 ms ftr.com [50.121.73.21] |
|
|
broncbob
Anon
2015-Mar-15 10:39 pm
yeah, mines slowly going up... gets to about 120 at the peak and is rock solid. still 25/25 on speedtest |
|
|
to broncbob
Same here... it goes up to around 100ms. |
|
Motorola MG8725 Asus RT-N66
|
to broncbob
This is weird, when I do tracerts from CT, I get my normal latency and such to anything else. However, once I do a tracert to your second hop (50.53.0.1) everything all of a sudden is 100+ ms, even the same routers.
Tracing route to comcast.net [69.252.80.75] over a maximum of 30 hops:
1 1 ms 2 ms 3 ms dsldevice.frontier.com [192.168.1.254] 2 26 ms 23 ms 23 ms ------------- 3 * * * Request timed out. 4 25 ms 26 ms 23 ms ------------- 5 24 ms 23 ms 25 ms ae4---0.car02.wlfr.ct.frontiernet.net [74.40.71. 101] 6 33 ms 33 ms 33 ms ae11---0.cor01.asbn.va.frontiernet.net [74.40.5. 217] 7 34 ms 33 ms 33 ms ae0--0.cbr02.asbn.va.frontiernet.net [74.40.5.19 4] 8 * 33 ms 33 ms lag-5.ear1.Washington39.Level3.net [4.15.136.1]
9 35 ms 34 ms 35 ms ae-104-3508.edge2.Washington12.Level3.net [4.69. 159.157] 10 33 ms 33 ms 35 ms ae-104-3508.edge2.Washington12.Level3.net [4.69. 159.157] 11 36 ms 35 ms 35 ms be-200-cr01.ashburn.va.ibone.comcast.net [23.30. 207.93] 12 38 ms 37 ms 37 ms et-1-1-0-0-ar03.newcastle.de.panjde.comcast.net [68.86.94.250] 13 37 ms 37 ms 38 ms ae100-ur11-d.newcastlerdc.de.panjde.comcast.net [68.85.158.90] 14 39 ms 37 ms 38 ms te-5-3-ur01-d.newcastlerdc.de.panjde.comcast.net [68.85.159.118] 15 37 ms 37 ms 37 ms urlrw01.cable.comcast.com [69.252.80.75]
Trace complete.
Tracing route to static-50-53-0-1.bvtn.or.frontiernet.net [50.53.0.1] over a maximum of 30 hops:
1 2 ms 1 ms 2 ms dsldevice.frontier.com [192.168.1.254] 2 23 ms 23 ms 23 ms ----------- 3 * * * Request timed out. 4 25 ms 23 ms 23 ms ------------ 5 23 ms 23 ms 23 ms ae4---0.car02.wlfr.ct.frontiernet.net [74.40.71. 101] 6 102 ms 102 ms 101 ms ae11---0.cor01.asbn.va.frontiernet.net [74.40.5. 217] 7 102 ms 101 ms 118 ms ae0---0.cor02.asbn.va.frontiernet.net [74.40.2.1 82] 8 102 ms 102 ms 104 ms ae1---0.cor02.chcg.il.frontiernet.net [74.40.2.1 93] 9 105 ms 102 ms 102 ms ae0---0.cor02.enwd.co.frontiernet.net [74.40.5.1 54] 10 101 ms 102 ms 102 ms ae6---0.cor01.sttl.wa.frontiernet.net [74.40.2.5 7] 11 103 ms 102 ms 102 ms ae1---0.cor02.bvtn.or.frontiernet.net [74.40.1.2 22] 12 103 ms 101 ms 101 ms 74.40.1.218 13 102 ms 102 ms 101 ms static-50-53-0-1.bvtn.or.frontiernet.net [50.53. 0.1]
Trace complete.
My Ashburn hop is 100ms for some reason when doing a tracert to that area while it's around 30ms when doing it to anything else. Also, for some reason, it's showing only a difference of 1ms to get to Oregon, so I don't know how accurate this is. I find it a little odd. |
|
|
|
broncbob
Anon
2015-Mar-16 11:10 pm
Yeah. The fact it's so stable is strange. Anyone know how to approach this? |
|
broncbob |
broncbob
Anon
2015-Mar-17 11:22 pm
multiple zombies are owning my ass. |
|
NormanSI gave her time to steal my mind away MVM join:2001-02-14 San Jose, CA TP-Link TD-8616 Asus RT-AC66U B1 Netgear FR114P
|
to Darknessfall
said by Darknessfall:My Ashburn hop is 100ms for some reason when doing a tracert to that area while it's around 30ms when doing it to anything else. Also, for some reason, it's showing only a difference of 1ms to get to Oregon, so I don't know how accurate this is. I find it a little odd. MPLS, maybe? Going to Beaverton, Oregon from San José, California looks normal: Tracing route to static-50-53-0-1.bvtn.or.frontiernet.net [50.53.0.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms koyomi.aosake.net [192.168.102.1]
2 20 ms 20 ms 19 ms 173-228-7-1.dsl.static.fusionbroadband.com [173.228.7.1]
3 20 ms 23 ms 20 ms gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
4 35 ms 32 ms 32 ms ae2.cr2.lsatca11.sonic.net [50.0.79.178]
5 20 ms 20 ms 20 ms 50.ae4.gw.pao1.sonic.net [142.254.58.158]
6 20 ms 20 ms 20 ms ae2.0.gw.equinix-sj.sonic.net [50.0.2.14]
7 21 ms 20 ms 20 ms sonicnet-customer.xo.com [216.156.84.101]
8 26 ms 26 ms 21 ms 207.88.13.228.ptr.us.xo.net [207.88.13.228]
9 21 ms 22 ms 21 ms 207.88.13.225.ptr.us.xo.net [207.88.13.225]
10 21 ms 22 ms 20 ms 206.111.12.146.ptr.us.xo.net [206.111.12.146]
11 21 ms 48 ms 21 ms ae2--0.cor01.plal.ca.frontiernet.net [74.40.3.149]
12 38 ms 39 ms 38 ms 74.40.1.226
13 72 ms 40 ms 39 ms ae0---0.car01.tgrd.or.frontiernet.net [74.40.1.182]
14 55 ms 40 ms 39 ms ae1---0.fdr01.aloh.or.frontiernet.net [74.40.70.74]
15 40 ms 40 ms 40 ms static-50-53-0-1.bvtn.or.frontiernet.net [50.53.0.1]
Trace complete.
But going to Connecticut I jump to 102 ms (East Coast RTT) while still in California, then only 1 ms cross country: Tracing route to ae4---0.car02.wlfr.ct.frontiernet.net [74.40.71.101]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms koyomi.aosake.net [192.168.102.1]
2 19 ms 20 ms 19 ms 173-228-7-1.dsl.static.fusionbroadband.com [173.228.7.1]
3 21 ms 20 ms 20 ms gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
4 32 ms 32 ms 32 ms ae2.cr2.lsatca11.sonic.net [50.0.79.178]
5 22 ms 20 ms 20 ms 50.ae4.gw.pao1.sonic.net [142.254.58.158]
6 20 ms 22 ms 20 ms ae2.0.gw.equinix-sj.sonic.net [50.0.2.14]
7 21 ms 20 ms 20 ms sonicnet-customer.xo.com [216.156.84.101]
8 21 ms 21 ms 21 ms 207.88.13.228.ptr.us.xo.net [207.88.13.228]
9 21 ms 24 ms 23 ms 207.88.13.225.ptr.us.xo.net [207.88.13.225]
10 21 ms 21 ms 39 ms 206.111.12.146.ptr.us.xo.net [206.111.12.146]
11 103 ms 103 ms 102 ms ae2---0.cor02.plal.ca.frontiernet.net [74.40.3.169]
12 103 ms 110 ms 104 ms ae4---0.cor02.plal.ca.frontiernet.net [74.40.1.62]
13 105 ms 93 ms 101 ms ae1---0.cor02.asbn.va.frontiernet.net [74.40.2.198]
14 103 ms 103 ms 102 ms ae4---0.car02.wlfr.ct.frontiernet.net [74.40.71.101]
Trace complete.
|
|
|
broncbob
Anon
2015-Mar-19 11:32 pm
Tracing route to ae4---0.car02.wlfr.ct.frontiernet.net [74.40.71.101] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 5 ms 4 ms 4 ms static-50-53-0-1.bvtn.or.frontiernet.net [50.53. 0.1] 3 5 ms 4 ms 4 ms xe--0-1-1---0.fdr01.aloh.or.frontiernet.net [50. 39.211.21] 4 4 ms 4 ms 4 ms ae11---0.car01.bvtn.or.frontiernet.net [74.40.70 .41] 5 178 ms 174 ms 174 ms ae2---0.cor01.bvtn.or.frontiernet.net [74.40.1.2 17] 6 168 ms 169 ms 174 ms ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.2 21] 7 193 ms 174 ms 186 ms ae3---0.cor02.enwd.co.frontiernet.net [74.40.2.5 8] 8 176 ms 173 ms 177 ms ae9---0.cor02.chcg.il.frontiernet.net [74.40.5.1 53] 9 177 ms 174 ms 209 ms ae1---0.cor01.asbn.va.frontiernet.net [74.40.2.1 94] 10 167 ms 166 ms 164 ms ae10---0.cor01.asbn.va.frontiernet.net [74.40.5. 129] 11 175 ms 174 ms 171 ms ae4---0.car02.wlfr.ct.frontiernet.net [74.40.71. 101]
Trace complete.
Beaverton, OR. This is where I live. Why is this hop so crazy. |
|
broncbob |
broncbob
Anon
2015-Mar-20 10:37 pm
Dear All,
Zombies continue to eat my face. Kind Regards, sad & bloody, Bob |
|
|
to broncbob
I feel for ya Bob. I get crap ping most nights as well and it has been that way for a good time now. |
|
DweeB0 |
to broncbob
Tonight is one of those nights. Crap ping. They'll never fix it. |
|
|
I may not be of the area, but you guys/gals have no idea what crap ping is....LoL
Tracing route to google.com [173.194.219.139] over a maximum of 30 hops:
1 477 ms 431 ms 477 ms 74-33-176-1.br1.civl.wi.frontiernet.net [74.33.176.1] 2 426 ms 499 ms 459 ms 184.9.115.17 3 413 ms 451 ms 476 ms ae3---0.car01.waus.wi.frontiernet.net [74.40.70.237] 4 310 ms 385 ms 492 ms ae12---0.cor02.chcg.il.frontiernet.net [74.40.4.29] 5 * * * Request timed out. 6 409 ms 314 ms 293 ms 72.14.212.143 7 470 ms 553 ms 501 ms 209.85.143.152 8 512 ms 498 ms 533 ms 209.85.243.163 9 294 ms 321 ms 319 ms 72.14.239.90 10 528 ms 518 ms 370 ms 209.85.143.193 11 * * * Request timed out. 12 434 ms 425 ms 417 ms 173.194.219.139
Trace complete. |
|
Motorola MG8725 Asus RT-N66
|
said by atigerman:I may not be of the area, but you guys/gals have no idea what crap ping is....LoL I sure don't traceroute to google.com (216.58.219.238), 30 hops max, 38 byte packets 1 -----------(-----------) 21.219 ms 20.907 ms 22.035 ms 2 * * * 3 -------------- (-------------) 21.673 ms 25.797 ms 21.233 ms 4 ae5---0.car02.wlfr.ct.frontiernet.net (74.40.71.105) 20.798 ms 20.898 ms 20.908 ms 5 ae1---0.car01.wlfr.ct.frontiernet.net (74.40.4.129) 24.707 ms 26.916 ms 24.815 ms 6 ae6---0.cor01.nycm.ny.frontiernet.net (74.40.5.209) 24.055 ms 24.864 ms 24.641 ms 7 ae0---0.cbr01.nycm.ny.frontiernet.net (74.40.4.82) 25.337 ms 24.467 ms 24.581 ms 8 74.40.26.214 (74.40.26.214) 24.258 ms 27.224 ms 24.758 ms 9 209.85.245.116 (209.85.245.116) 25.057 ms 24.548 ms 24.414 ms 10 64.233.174.117 (64.233.174.117) 25.246 ms 25.000 ms 25.072 ms 11 lga25s41-in-f14.1e100.net (216.58.219.238) 24.951 ms 24.773 ms 25.416 ms |
|
Smith6612 MVM join:2008-02-01 North Tonawanda, NY |
It would be so nice to see Interleaving turned off with that kind of route. Too bad that never happens on VDSL. |
|
Juniper SRX220 Cisco Meraki MR16
|
to NormanS
said by NormanS:But going to Connecticut I jump to 102 ms (East Coast RTT) while still in California, then only 1 ms cross country: Tracing route to ae4---0.car02.wlfr.ct.frontiernet.net [74.40.71.101] over a maximum of 30 hops:
1 I think the latency spike when you hit hops with Frontier Reverse DNS is due to Frontier de-prioritizing ICMP on their routers |
|
|
broncbob
Anon
2015-Mar-26 12:20 am
I always thought my FIOS connection was dedicated to me and I would never run into the neighborhood logging on at 7pm to watch their Netflix. Why I left comcast.
I just find it strange, that after 2 years of no problems, every night is a problem all of a sudden. Someone flipped a switch somewhere, this was not gradual. |
|
HankSearching for a new Frontier Premium Member join:2002-05-21 Burlington, WV |
Hank
Premium Member
2015-Mar-26 5:49 am
It could be that Frontier is making some network changes and it is temporary. Have you talked to Frontier about the issue? |
|
|
1 recommendation |
to broncbob
So my back and forth between Frontier reps has finally yielded an admission, but unfortunately we can expect this issue for the foreseeable future: Hello Brian,
Thank you for contacting Frontier FiOS Technical Support. I apologize for the latency issues you are having, and as a fellow gamer myself I understand and appreciate how frustrating that can be. This is an known issues in the Beaverton area (ae2---0.cor01.bvtn.or.frontiernet.net ), which unfortunately right now we are experience a surplus of users in this area which is causing some slow down. We have plans in place to upgrade the servers and the system to alleviate this issue. As of right now we do not have an ETA but upgrade and bettering our infrastructure is our number one goal right now.
Regards,
Donald I really don't want to have to switch back to Comcast, but I may have to upon my upcoming move this summer. |
|
Advil6 join:2002-01-25 Beaverton, OR
1 recommendation |
Advil6
Member
2015-Mar-26 11:40 pm
I am right there with you broncbob. My attached traceroute is what it looks like every night now after 6:30pm. This is when it's STABLE. The random spikes of 800ms and loss has just about made gaming impossible lately. (last few months and getting worse it seems like weekly)
This is really more or less unusable for gaming now, which is why I have it. And no, I don't want to ever return to Comcast, but I'm going to have no choice at this rate which is even more upsetting. No ETA for the upgrades to fix it? We NEED an ETA or we are going to get forced to make decisions about keeping the service based on the assumption that it won't get fixed any time soon. They don't want to lose the revenue, and I don't want to stop supporting the local fiber internet provider. So maybe they could talk to us a little? Maybe give some options? Maybe we could pay extra on a bill to do the upgrades and they can credit it back later over time? Work with us!
Frontier, if you guys ever read this, you need to please move this up to emergency status. Our service is collapsing every evening. This has been going on for months!
This is fiber internet for crying out loud, these numbers are horrible:
Tracing route to mwomercs.com [192.99.109.192] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1] 2 1 ms 1 ms 1 ms 10.40.0.23 3 2 ms 1 ms 1 ms xe--5-1-0---0.fdr01.aloh.or.frontiernet.net [50.38.7.85] 4 1 ms 1 ms 1 ms ae11---0.car01.bvtn.or.frontiernet.net [74.40.70.41] 5 98 ms 95 ms 114 ms ae2---0.cor01.bvtn.or.frontiernet.net [74.40.1.217] 6 97 ms 99 ms 97 ms ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.221] 7 98 ms 93 ms 101 ms ae0---0.cbr01.sttl.wa.frontiernet.net [74.40.5.122] 8 92 ms 93 ms 92 ms ix-0-0-3-0.tcore1.00S-Seattle.as6453.net [207.45.206.29] 9 170 ms 116 ms 109 ms if-1-0-0-3.core1.00S-Seattle.as6453.net [64.86.123.6] 10 161 ms 165 ms 169 ms if-1-0-3-0.tcore2.CT8-Chicago.as6453.net [64.86.124.10] 11 171 ms 171 ms 173 ms if-22-2.tcore1.CT8-Chicago.as6453.net [64.86.79.2] 12 * 168 ms * if-12-6.tcore2.NYY-New-York.as6453.net [216.6.99.45] 13 171 ms 172 ms 157 ms if-11-2.tcore1.NYY-New-York.as6453.net [216.6.99.2] 14 172 ms 171 ms 173 ms if-3-2.thar1.NJY-Newark.as6453.net [66.198.70.21] 15 * * * Request timed out. 16 172 ms 166 ms 166 ms 192.99.146.86 17 173 ms 173 ms 173 ms 198.27.73.233 18 173 ms 171 ms 172 ms mwomercs.com [192.99.109.192]
Trace complete. |
|
darciliciousCyber Librarian Premium Member join:2001-01-02 Forest Grove, OR ·Ziply Fiber
|
to broncbob
Everyone on FiOS who is experiencing this issue needs to contact Frontier management, be polite but firm, don't make threats that you're not going to act upon. Mention that you're paying for a premium residential service and would like to see this addressed as soon as possible, etc. » frontier.com/helpCenter/ ··· r-memberI recommend emailing them no more than once a week but do email them regularly. |
|
Advil6 join:2002-01-25 Beaverton, OR
1 recommendation |
Advil6
Member
2015-Mar-27 5:52 pm
Thank you so much for the links. Sent a polite email explaining just how bad the connection has gotten every evening to the GM and received a personal reply almost immediately.
She said they are aware of it. It is a capacity/congestion issue of a northbound route. They expect mid April now for things to be done and claim they are trying to work quickly to resolve it.
I know, they've been saying that for a while. But as darcilicious just said, PLEASE send a polite email using the link. This has obviously reached the point where something has to be done for the service to be acceptable and they need to be told by those affected. |
|
|
broncbob
Anon
2015-Mar-29 11:07 pm
Thanks for the links.
Although I'm sorry to see others in OR having the same issue, I'm now happy it's not just me and some masses to get behind this. I just e-mailed the GM as well, politely, asking if they are aware and an ETA. 8pm sunday and my tracert to google is in the 300's already. Ouch. |
|
Kai @frontiernet.net |
Kai
Anon
2015-Apr-4 1:39 am
I have noticed the same issues as everyone else but even during peak times no matter where in California or any west region state besides Washington i get great pings but anything in Washington I get 100+ ms no matter what I try and do.
I spoke with a couple of reps this evening and they told me that there is an issue with the server in Beaverton and multiple customers have called to make them aware of this situation and the techs are currently working on it. |
|
zmarty join:2015-02-25 Kirkland, WA |
to broncbob
I have Frontier FiOS and I live in Kirkland, WA. I have set up ICMP (ping) monitoring from my local machine using Zabbix. I monitor the ping times to a bunch of websites. I am attaching just two examples. The green line shows ping times and the red line shows ping timeouts. The Yahoo Japan graph shows the past month of data. The spikes happen like clockwork in the evenings. The Lehigh (Pennsylvania) graph is just for the last 7 days, so you can see the spikes better. Again, they are in the evenings. |
|
|
broncbob
Anon
2015-Apr-15 8:01 pm
getting worse for me now... 400-600 pings from 100-200 |
|
broncbob |
broncbob
Anon
2015-Apr-23 11:21 pm
perfect now |
|
|
Looking better here as well, looks like no direct to Google peering in Seattle now, but it seems the congestion is better (8:44PM PDT) from Portland to 4.2.2.2 and 8.8.8.8
#traceroute 4.2.2.2 Type escape sequence to abort. Tracing the route to b.resolvers.Level3.net (4.2.2.2) VRF info: (vrf in name/id, vrf out name/id) 1 static-50-43-16-1.bvtn.or.frontiernet.net (50.43.16.1) 0 msec 4 msec 4 msec 2 xe--5-1-1---0.fdr01.grhm.or.frontiernet.net (50.45.229.5) 4 msec 0 msec 0 msec 3 ae10---0.car01.bvtn.or.frontiernet.net (74.40.70.37) 4 msec 4 msec 4 msec 4 ae2---0.cor01.bvtn.or.frontiernet.net (74.40.1.217) 32 msec 12 msec 32 msec 5 ae4---0.cor01.sttl.wa.frontiernet.net (74.40.1.221) 20 msec 8 msec 8 msec 6 ae0---0.cbr01.sttl.wa.frontiernet.net (74.40.5.122) 8 msec 68 msec 8 msec 7 xe-5-0-0.edge1.Seattle3.Level3.net (4.59.232.5) 24 msec 20 msec 24 msec 8 ae-1-60.edge1.SanJose1.Level3.net (4.69.152.14) 20 msec 20 msec ae-3-80.edge1.SanJose1.Level3.net (4.69.152.142) 20 msec 9 * ae-4-90.edge1.SanJose1.Level3.net (4.69.152.206) 20 msec 20 msec 10 b.resolvers.Level3.net (4.2.2.2) 36 msec 40 msec 36 msec #traceroute 8.8.8.8 Type escape sequence to abort. Tracing the route to google-public-dns-a.google.com (8.8.8.8) VRF info: (vrf in name/id, vrf out name/id) 1 static-50-43-16-1.bvtn.or.frontiernet.net (50.43.16.1) 4 msec 4 msec 4 msec 2 xe--5-1-1---0.fdr01.grhm.or.frontiernet.net (50.45.229.5) 0 msec 0 msec 0 msec 3 ae10---0.car01.bvtn.or.frontiernet.net (74.40.70.37) 4 msec 4 msec 4 msec 4 ae2---0.cor01.bvtn.or.frontiernet.net (74.40.1.217) 8 msec 8 msec 8 msec 5 ae4---0.cor01.sttl.wa.frontiernet.net (74.40.1.221) 8 msec 8 msec 8 msec 6 ae0---0.cbr01.sttl.wa.frontiernet.net (74.40.5.122) 8 msec 8 msec 8 msec 7 74.40.26.177 32 msec 24 msec 24 msec 8 209.85.247.15 20 msec 72.14.233.249 24 msec 72.14.239.148 20 msec 9 * google-public-dns-a.google.com (8.8.8.8) 20 msec 24 msec |
|
zmarty join:2015-02-25 Kirkland, WA |
zmarty
Member
2015-Apr-24 1:08 am
I have looked at all my ping monitoring graphs and nothing changed. I also have a graph which measures number of traceroute network hops to Google & Co., and again nothing changed. In the evenings the throughput to destinations outside Washington State is still atrocious. |
|
HankSearching for a new Frontier Premium Member join:2002-05-21 Burlington, WV |
Hank
Premium Member
2015-Apr-24 3:05 pm
Take a look at the post by MDrules in this thread and you will have your answer. » [FiOS] Daily routing congestion |
|