US Telco Support > Frontier Communications > [FiOS] Unstable connection during evering hours. FIOS. WA area.

[FiOS] Unstable connection during evering hours. FIOS. WA area.

Re: [FiOS] Unstable connection during evering hours. FIOS. WA ar

Glad to hear that someone noticed it too.
I can post traceroutes too check which backbones they are using.

But I still think that it is just heavy overloaded network.

reply to blz
Fios backbones are in Ft Wayne, Ind.

Im only 40miles away from ft.wayne so if I can get a good IP address from a fios customer I can do tracert since I got a fiber connection from ohio to indiana.

reply to Chawk12

C:\Users\wesmills>tracert 209.144.21.58
 
Tracing route to phoenix.tmb.ORG [209.144.21.58]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.7.1
  2    18 ms    18 ms    18 ms  static-50-46-144-1.evrt.wa.frontiernet.net [50.46.144.1]
  3    18 ms    18 ms    18 ms  G14-0-7-117.STTLWA-LCR-01.ncnetwork.net [184.19.242.24]
  4    27 ms    18 ms    18 ms  50.34.2.1
  5    20 ms    19 ms    19 ms  ae3---0.cor02.sttl.wa.frontiernet.net [74.40.1.101]
  6    19 ms    19 ms    19 ms  ae1---0.cbr01.sttl.wa.frontiernet.net [74.40.5.126]
  7    19 ms    19 ms    19 ms  xe-10-1-0.edge1.Seattle3.Level3.net [4.59.232.5]
 

reply to blz
ya I hit level3 and frontier net also:

1 3 ms 3 ms 4 ms 192.168.5.1
2 4 ms 3 ms 4 ms 192.168.0.1
3 29 ms 7 ms 4 ms 206-51-163-1.nktelco.net [206.51.163.1]
4 11 ms 9 ms 8 ms 172.20.0.1
5 62 ms 25 ms 30 ms 10.0.32.245
6 7 ms 7 ms 6 ms 10.0.32.241
7 26 ms 18 ms 18 ms gig7-46-2015.clmboh1-p-rtr01.columbus.rr.com [70
.60.140.161]
8 19 ms 23 ms 18 ms tge4-0-0.dytnoh1-pe-rtr01.mwrtn.rr.com [65.189.1
00.37]
9 21 ms 41 ms 22 ms tge3-0-0.dytnoh1-p-rtr01.mwrtn.rr.com [65.189.10
0.89]
10 41 ms 21 ms 20 ms tge4-0-0.mtgmoh1-pe-rtr01.mwrtn.rr.com [65.189.1
00.33]
11 26 ms 19 ms 19 ms tge8-0-0.mtgmoh1-p-rtr01.mwrtn.rr.com [65.189.10
0.174]
12 90 ms 32 ms 54 ms ae8.tr00.clmkohpe.mwrtn.rr.com [65.189.100.58]
13 33 ms 31 ms 30 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
14 34 ms 40 ms 36 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
15 48 ms 50 ms 50 ms xe-10-0-0.edge2.Chicago2.Level3.net [4.59.28.101
]
16 53 ms 51 ms 47 ms vl-3504-ve-118.ebr1.Chicago2.Level3.net [4.69.15
8.14]
17 79 ms 75 ms 77 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
18 96 ms 102 ms 91 ms ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
19 104 ms 91 ms 127 ms ae-2-52.edge1.Seattle3.Level3.net [4.69.147.170]

20 98 ms 96 ms 98 ms CITIZENS-CO.edge1.Seattle3.Level3.net [4.59.232.
6]
21 101 ms 100 ms 98 ms ae2---0.cor02.sttl.wa.frontiernet.net [74.40.5.1
25]
22 110 ms 113 ms 108 ms ae0---0.car01.evrt.wa.frontiernet.net [74.40.1.1
02]
23 102 ms 101 ms 103 ms 50.34.2.2
24 123 ms 111 ms 107 ms static-50-46-144-1.evrt.wa.frontiernet.net [50.4
6.144.1]

This is exactly my first hop which you pinged.
I do not have lags right now but still ping does not look like stable one:

2012-01-05 01:41:45: Reply from 50.46.144.1: time=7ms
2012-01-05 01:41:46: Reply from 50.46.144.1: time=7ms
2012-01-05 01:41:47: Reply from 50.46.144.1: time=8ms
2012-01-05 01:41:48: Reply from 50.46.144.1: time=15ms
2012-01-05 01:41:49: Reply from 50.46.144.1: time=10ms
2012-01-05 01:41:50: Reply from 50.46.144.1: time=9ms
2012-01-05 01:41:51: Reply from 50.46.144.1: time=13ms
2012-01-05 01:41:52: Reply from 50.46.144.1: time=17ms
2012-01-05 01:41:53: Reply from 50.46.144.1: time=41ms
2012-01-05 01:41:54: Reply from 50.46.144.1: time=17ms
2012-01-05 01:41:55: Reply from 50.46.144.1: time=29ms
2012-01-05 01:41:56: Reply from 50.46.144.1: time=8ms
2012-01-05 01:41:57: Reply from 50.46.144.1: time=8ms
2012-01-05 01:41:58: Reply from 50.46.144.1: time=9ms
2012-01-05 01:41:59: Reply from 50.46.144.1: time=11ms
2012-01-05 01:42:00: Reply from 50.46.144.1: time=7ms
2012-01-05 01:42:01: Reply from 50.46.144.1: time=15ms
2012-01-05 01:42:02: Reply from 50.46.144.1: time=21ms
2012-01-05 01:42:03: Reply from 50.46.144.1: time=32ms
2012-01-05 01:42:04: Reply from 50.46.144.1: time=8ms

reply to treichhart
Yeah, I'm in Bothell and have noticed the same thing over the last month. Netflix streaming has come to a halt and not even usable between 8-11pm. Seems to clear up after that. Speed tests are only showing around 1-4mbps for a wired connection. I normally get 9mbps. Seeing extremely high latency when tracert'ing to Netflix and other sites:

C:\Users\Matt>tracert moviecontrol.netflix.com

Tracing route to nccp-moviecontrol-frontend-1712188921.us-east-1.elb.amazonaws.com [204.236.229.171]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms myrouter.home [192.168.2.1]
2 2 ms 2 ms 2 ms static-50-46-224-1.evrt.wa.frontiernet.net [50.46.224.1]
3 91 ms 88 ms 96 ms 50.34.2.153
4 160 ms 161 ms 158 ms ae3---0.cor01.sttl.wa.frontiernet.net [74.40.1.153]
5 159 ms 157 ms 173 ms ae0---0.cor02.sttl.wa.frontiernet.net [74.40.3.138]
6 155 ms 162 ms 160 ms xe--11-0-0---0.cor01.mond.mn.frontiernet.net [74.40.5.45]
7 153 ms 152 ms 159 ms ae0---0.cor01.lkvl.mn.frontiernet.net [74.40.5.53]
8 161 ms 151 ms 148 ms ae4---0.cor01.chcg.il.frontiernet.net [74.40.5.50]
9 155 ms 158 ms 158 ms ae0---0.cor02.chcg.il.frontiernet.net [74.40.3.242]
10 157 ms 150 ms 156 ms ae1---0.cor01.asbn.va.frontiernet.net [74.40.2.194]
11 154 ms 160 ms 174 ms ae1---0.cbr01.asbn.va.frontiernet.net [74.40.2.174]
12 158 ms 205 ms 159 ms equinix02-iad2.amazon.com [206.223.115.35]

reply to blz
I had problems last night for the first time in months. Latency was about 80ms above normal, and my bandwidth on speed tests was about a third or less than what it normally/should be. Hopefully this is just a short lived problem and is going to be resolved. Before last night though, I got my full bandwidth and excellent latency no matter what the time of day. I'm north of Bothell near Mill Creek.

The problem is persistent for the last few months, so I hope everyone who has it will contact technical support.

I contacted support last night and the tech I spoke to said they have been getting calls on this issue throughout Oregon and Washington for about a month and that they are well aware of the problem. He stated that they have no ETR but told me to keep calling back every couple of nights for an update.

reply to sharkdanger
im in bothell and I'm experiencing the same thing.
Evening hours are very unstable.

I called the techs 3 times in the last 6 months. another field tech is coming out on sat. for the 3rd time.

I'm about to drop frontier. ever since verizon handover to frontier it has gone down hill.

Also I noticed that routing inside level3 to NY is crazy:

1 1 ms 1 ms 1 ms 192.168.1.1
2 5 ms 6 ms 5 ms static-50-46-144-1.evrt.wa.frontiernet.net [50.46.144.1]
3 12 ms 12 ms 14 ms 50.34.2.181
4 18 ms 17 ms 17 ms ae3---0.cor02.sttl.wa.frontiernet.net [74.40.1.101]
5 119 ms 83 ms 80 ms ae1---0.cbr01.sttl.wa.frontiernet.net [74.40.5.126]
6 41 ms 40 ms 37 ms xe-10-1-0.edge1.Seattle3.Level3.net [4.59.232.5]
7 39 ms 40 ms 50 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]
8 57 ms 52 ms 53 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
9 71 ms 74 ms 76 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
10 148 ms 155 ms 150 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
11 158 ms 152 ms 156 ms ae-2-2.ebr2.NewYork2.Level3.net [4.69.132.66]
12 171 ms 153 ms 157 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
13 124 ms 118 ms 109 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]
14 166 ms 225 ms 242 ms ae-33-80.car3.NewYork1.Level3.net [4.69.155.133]
15 164 ms 167 ms 168 ms PILOSOFT-IN.car3.NewYork1.Level3.net [4.53.88.10]
16 164 ms 163 ms 153 ms 69.172.128.1

1 1 ms 1 ms 1 ms 192.168.1.1
2 5 ms 6 ms 5 ms static-50-46-144-1.evrt.wa.frontiernet.net [50.46.144.1]
3 12 ms 12 ms 14 ms 50.34.2.181
4 18 ms 17 ms 17 ms ae3---0.cor02.sttl.wa.frontiernet.net [74.40.1.101]
5 119 ms 83 ms 80 ms ae1---0.cbr01.sttl.wa.frontiernet.net [74.40.5.126]
6 41 ms 40 ms 37 ms xe-10-1-0.edge1.Seattle3.Level3.net [4.59.232.5]
7 39 ms 40 ms 50 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]
8 57 ms 52 ms 53 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
9 71 ms 74 ms 76 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
10 148 ms 155 ms 150 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
11 158 ms 152 ms 156 ms ae-2-2.ebr2.NewYork2.Level3.net [4.69.132.66]
12 171 ms 153 ms 157 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
13 124 ms 118 ms 109 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]
14 166 ms 225 ms 242 ms ae-33-80.car3.NewYork1.Level3.net [4.69.155.133]
15 164 ms 167 ms 168 ms PILOSOFT-IN.car3.NewYork1.Level3.net [4.53.88.10]
16 164 ms 163 ms 153 ms 69.172.128.1

Strange jump by 80ms in Chicago.

reply to blz
Does this problem occur on the weekend or only during the week?

When I had a similar problem with my DSL service a few months ago things worked fine from 8PM-11PM on the weekend. That's why my suspicions are someone back east is working on the network.

I did not use a computer on last Saturday and Sunday but the problem occur on Monday the 2nd which was non-working day.

Yesterday, Frontier representative called me and said that they have some moving changes in their network during last 4 weeks and this work should be finished on 12th of January.
She said that I can contact billing department and they will add credit to my account.

reply to blz
Throwing my name into the hat. I am also in Bothell and have had slowness with Frontier especially fluctuating upload and download speeds. I normally get a consistent 35/35mbps but now I never hit that and am Lucky to give 10-15 during those hours- try the next morning and problem has magically disappeared. I started noticing on Saturday 01/07/11

reply to blz
Spoke to a FIOS rep last night in West Virginia who initially didn't want to file a ticket/log an outage for the Bothell issue because he hadn't had any other reports. I referred him to the DSLreports thread here and he called me back and said they were treating this as an "outage". I wasn't able to get a ticket number or anything but I hope that means they are actually working on it. However, I'm a bit concerned we keep getting different answers. E.g., network outage, network maintenance, no problems here!

I encourage you all to call in and report this issue.

reply to blz
Latency graph:

»imgur.com/MBcvu

Green line is me (FiOS), Pink, red, and blue are all friends of mine who are all on Comcast. Latency measurements are being taken from a friend's machine at his work on a business class DS3 connection. Pretty reliable unreliability.

I've been e-mailing back and forth with the fiber support center in Everett, I haven't seen any explanation yet. If I find anything out, i'll let everybody here know though.

reply to blz
I'm looking into this for you guys.

reply to blz
We've identified a configuration error on the FIOS systems servicing a subset of markets in the Seattle and Portland areas which was introduced during recent upgrades to the network. The error is artificially limiting the peak downstream capacity in these markets by about 50%. There's an emergency maintenance window scheduled for tonight to implement a fix. We've also fixed the upgrade procedure so this won't happen on the next one, are auditing the other markets to be sure we clean this up fully, and will be working with the FSC to ensure issues like this get better escalation next time around.

Sorry about that guys,
--Ben
(Your friendly resident FIOS/Content Architect)

EDIT: added Portland
--
Transparency Disclosure and Disclaimer: I am a Frontier employee posting in my own personal capacity. The opinions and positions expressed are my own and do not necessarily reflect those of Frontier.