dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
7744
share rss forum feed


Fatman

@frontiernet.net
reply to FU_Frontier

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

I'm in the same boat. Already called and jumped through all of the hoops the tech asked me too. He said he was passing it to someone who handles more backend stuff as my setup seemed fine. Never heard back and still jumps in ping and low bandwidth in the evenings only. Same experience for 3 coworkers that live on the west side of Portland. I'm ready to move to COmcast shortly if this isn't fixed quickly.


SLK

@frontiernet.net
I still keep experiencing huge increases in latency in Beaverton OR every night between 7:00 PM and midnight (local time). This has been going on for nearly 6 weeks now and everyone I speak with at tech support at frontier is completely oblivious to the problem. Some people at tech support will take a moment to look into it and come to find there is an issue in the area. Others will say they spoke with people and they were told of no issues in the area. One guy I spoke with seemed pretty competent and told me that the issue was because of IP routing in my area. He said that IP's were being routed much further away than they needed to be resulting in a loss in down/up speeds as well as large increases in latency. This is getting very annoying as I only really need to use the internet during these peak hours but have been unable to for what will be approaching 2 months. Very frustrating to deal with a company that doesn't care about it's customers.


Ben J
Triple Play Architect
Premium
join:2011-09-16
Fort Wayne, IN
kudos:9
Fatman/SLK,

Post traceroutes or PM me your WAN IP.


SLK

@frontiernet.net
Tracing route to host.colocrossing.com [66.225.232.20]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 6 ms 6 ms static-50-53-0-1.bvtn.or.frontiernet.net [50.53.
0.1]
3 90 ms 84 ms 76 ms 50.38.7.77
4 159 ms 174 ms 184 ms ae2---0.cor01.ptld.or.frontiernet.net [74.40.1.1
61]
5 145 ms 104 ms 99 ms ae1---0.cor01.plal.ca.frontiernet.net [74.40.2.1
58]
6 151 ms 159 ms 159 ms so--0-0-0---0.br01.plal.ca.frontiernet.net [74.4
0.3.150]
7 165 ms 156 ms 157 ms paix.99.xe-0-1-0.cr1.pao1.us.nlayer.net [198.32.
176.13]
8 96 ms 102 ms 96 ms ae1-50g.cr1.sjc1.us.nlayer.net [69.22.143.165]
9 151 ms 146 ms 137 ms xe-5-1-0.cr2.ord1.us.nlayer.net [69.22.142.6]
10 154 ms 146 ms 144 ms ae3-40g.cr1.ord1.us.nlayer.net [69.31.111.153]
11 167 ms 154 ms 157 ms po6.ar1.ord1.us.scnet.net [69.31.111.58]
12 157 ms 164 ms 164 ms 61.po1.ar1.ord6.us.scnet.net [75.102.3.226]
13 149 ms 146 ms 149 ms as36352.po4.ar1.ord6.us.scnet.net [204.93.192.18
6]
14 151 ms 139 ms 147 ms host.colocrossing.com [205.234.152.250]
15 157 ms 161 ms 157 ms host.colocrossing.com [66.225.232.20]

This was taken before the worst latency times (latency was still increasing). At the highest latency the ms reaches 200ms/times out.

Let me know if you need any other information or if this isn't enough.

Thanks!


SLK

@frontiernet.net
Here is another tracert that I just took that it outside the 7:00PM-midnight time frame of increased latency. For this tracert it only shows the latency doubling but when I run tracert to places on the east coast they can reach 4 or 5 times the typical latency.

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

C:\Users\Set>tracert 66.225.232.20

Tracing route to host.colocrossing.com [66.225.232.20]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 6 ms 7 ms 6 ms static50-53-0-1.bvtn.or.frontiernet.net [50.53.0.1]
3 7 ms 7 ms 9 ms 50.38.7.77
4 28 ms 27 ms 27 ms ae2---0.cor01.ptld.or.frontiernet.net [74.40.1.161]
5 60 ms 32 ms 26 ms ae1---0.cor01.plal.ca.frontiernet.net [74.40.2.158]
6 27 ms 27 ms 27 ms so--0-0-0---0.br01.plal.ca.frontiernet.net [74.40.3.150]
7 27 ms 26 ms 26 ms paix.99.xe0-1-0.cr1.pao1.us.nlayer.net [198.32.176.13]
8 45 ms 26 ms 27 ms ae1-60g.cr1.sfo1.us.nlayer.net [69.22.143.169]
9 48 ms 42 ms 46 ms xe-0-0-3.cr1.slc1.us.nlayer.net [69.22.142.96]
10 70 ms 68 ms 71 ms xe-5-2-0.cr1.ord1.us.nlayer.net [69.22.142.101]
11 73 ms 71 ms 72 ms po6.ar1.ord1.us.scnet.net [69.31.111.58]
12 70 ms 72 ms 71 ms 61.po1.ar1.ord6.us.scnet.net [75.102.3.226]
13 75 ms 74 ms 78 ms as36352.po4.ar1.ord6.us.scnet.net [204.93.192.186]
14 73 ms 71 ms 72 ms host.colocrossing.com [205.234.152.250]
15 73 ms 72 ms 72 ms host.colocrossing.com [66.225.232.20]

Trace complete.


SLK

@frontiernet.net
reply to Ben J
Here is another tracert from today at 10:15 PM pacific. This problem has been known to Frontier Communications for nearly 6 weeks now...this is getting unacceptable. THE ISSUE COMES UP EVERY DAY! Why I continue to pay $150 a month for their so called "service" is beyond me.

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

C:\Users\Set>tracert host.colocrossing.com

Tracing route to host.colocrossing.com [216.246.49.26]
over a maximum of 30 hops:

1


SLK

@frontiernet.net
reply to Ben J
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Set>tracert host.colocrossing.com

Tracing route to host.colocrossing.com [216.246.49.26]
over a maximum of 30 hops:

1

Last one didn't seem to go through.


Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Use the [ code ] [ /code ] tags for Traceroutes. The forums seem to eat them for some reason.


Cyberian75

join:2004-03-16
Beaverton, OR
It's because of the "<" symbol.


Hank
Searching for a new Frontier
Premium
join:2002-05-21
Burlington, WV
kudos:3
reply to SLK
Worked just fine from my location.


Ben J
Triple Play Architect
Premium
join:2011-09-16
Fort Wayne, IN
kudos:9
reply to SLK
SLK,

Your area is in the process of being migrated to new circuits. You should see this resolved in the next couple days.


SLK

@frontiernet.net
Thanks so much for the information Ben. I really don't mind if there is slow issues with my internet, but the fact that they didn't communicate with me at all or that their tech support team doesn't know what is going on is what bugs me.


Ben J
Triple Play Architect
Premium
join:2011-09-16
Fort Wayne, IN
kudos:9
I completely understand your frustration. FYI- I've escalated this internally, they found trouble on two of the new circuits, and it's now being treated as an outage.


Ben J
Triple Play Architect
Premium
join:2011-09-16
Fort Wayne, IN
kudos:9

1 recommendation

reply to SLK
Should be fixed now.


SLK

@frontiernet.net
Thanks so much for helping me out! It seems that it worked great for a few days, and in fact this problem has been solved for my connection to many servers across the country. However the past few days it seems that the problem has again arisen with certain servers located in Texas, Colorado and California (just to name a few). My ping is again stable at times not between 7:00PM and 12midnight Pacific local time. The good thing is, my connection to other servers in places like Illinois, NY, Virgina, Georgia, Seattle seem to be good (again, just to name a few). Not sure if this is the same problem as before.

Thanks so much!


Ben J
Triple Play Architect
Premium
join:2011-09-16
Fort Wayne, IN
kudos:9
Not the same problem as before. Next time it happens, post or PM two traceroutes for me, one to a "bad" site, and one to a "good" site. I'll take a look.

chevelleman

join:2009-05-15
Troutdale, OR
reply to blz
Been getting a very slow connection for the past few days here in Troutdale from about 6PM to midnight.


chevelleman

join:2009-05-15
Troutdale, OR
reply to blz
Here's a Traceroute also.
 Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Home>tracert 66.225.232.20
 
Tracing route to host.colocrossing.com [66.225.232.20]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.ftrdhcpuser.net [192.168.1.1]
  2     7 ms     6 ms     7 ms  static-50-43-16-1.bvtn.or.frontiernet.net [50.43.16.1]
  3    84 ms    86 ms    87 ms  50.38.7.57
  4    99 ms    94 ms    97 ms  ae2---0.cor02.ptld.or.frontiernet.net [74.40.1.165]
  5   135 ms   106 ms   112 ms  ae0---0.cor01.ptld.or.frontiernet.net [74.40.4.109]
  6   118 ms   114 ms   117 ms  ae1---0.cor01.plal.ca.frontiernet.net [74.40.2.158]
  7   104 ms   101 ms   102 ms  so--0-0-0---0.br01.plal.ca.frontiernet.net [74.40.3.150]
  8    91 ms    92 ms    94 ms paix.99.xe0-1-0.cr1.pao1.us.nlayer.net [198.32.176.13]
  9   112 ms   109 ms   109 ms  ae1-60g.cr1.sfo1.us.nlayer.net [69.22.143.169]
 10   130 ms   129 ms   129 ms  xe-0-0-3.cr1.slc1.us.nlayer.net [69.22.142.96]
 11   155 ms   162 ms   152 ms  xe-5-2-0.cr1.ord1.us.nlayer.net [69.22.142.101]
 
 12   150 ms   141 ms   217 ms  po6.ar1.ord1.us.scnet.net [69.31.111.58]
 13   164 ms   159 ms   151 ms  61.po1.ar1.ord6.us.scnet.net [75.102.3.226]
 14   155 ms   152 ms   151 ms  as36352.po4.ar1.ord6.us.scnet.net [204.93.192.186]
 15   160 ms   154 ms   159 ms  host.colocrossing.com [205.234.152.250]
 16   146 ms   149 ms   149 ms  host.colocrossing.com [66.225.232.20]
 
Trace complete.
 


SLK

@frontiernet.net
reply to Ben J
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Set>tracert 206.217.135.162
 
Tracing route to host.colocrossing.com [206.217.135.162]
over a maximum of 30 hops:
 
  1
 
 

This was taken at a little after midnight. My ping to this server was approximately 150. Typically it is approximately half that.

Here is a tracert to an Illinois server hosted by the same company.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Set>tracert 66.225.232.9
 
Tracing route to host.colocrossing.com [66.225.232.9]
over a maximum of 30 hops:
 
  1
 

Again, I appreciate all the help you've been. Without you I probably would have pulled my hair out already because of the latency (luckily I do not connect to Texas servers often).


SLK

@frontiernet.net
Last try with this code...otherwise I'll just PM it to you.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Set>tracert 66.225.232.9
 
Tracing route to host.colocrossing.com [66.225.232.9]
over a maximum of 30 hops:
 
  1
 

The preview looks fine but for some reason it does not show.

SLK

join:2012-01-31
Beaverton, OR
BenJ, I sent you an email with two tracerts. I hope that the information was copied. I honestly have no idea why it isn't copy and pasting properly. I even paste the tracert information to a word document to make sure it copied and then copy it again from the word document to the forum but it always seems to not include the information. Anyway I can email it to you directly if you are comfortable providing me with any email address if you did not get my message.

chevelleman

join:2009-05-15
Troutdale, OR
reply to blz
Now here's the same traceroute after midnight.
 Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\Users\Home>tracert 66.225.232.20
 
Tracing route to host.colocrossing.com [66.225.232.20]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.ftrdhcpuser.net [192.1
68.1.1]
  2     8 ms     7 ms     6 ms  static-50-43-16-1.bvtn.or.frontiernet.net [50.43.16.1]
  3     7 ms     7 ms     7 ms  50.38.7.57
  4    26 ms    26 ms    27 ms  ae2---0.cor02.ptld.or.frontiernet.net [74.40.1.165]
  5    27 ms    77 ms    36 ms  ae0---0.cor01.ptld.or.frontiernet.net [74.40.4.109]
  6    29 ms    55 ms    26 ms  ae1---0.cor01.plal.ca.frontiernet.net [74.40.2.158]
  7    27 ms    29 ms    26 ms  so--0-0-0---0.br01.plal.ca.frontiernet.net [74.40.3.150]
  8    29 ms    27 ms    26 ms  paix.99.xe-0-1-0.cr1.pao1.us.nlayer.net [198.32.176.13]
  9    27 ms    27 ms    41 ms  ae1-60g.cr1.sfo1.us.nlayer.net [69.22.143.169]
 10    41 ms    42 ms    44 ms  xe-0-0-3.cr1.slc1.us.nlayer.net [69.22.142.96]
 11    75 ms    72 ms    71 ms  xe-5-2-0.cr1.ord1.us.nlayer.net [69.22.142.101]
 
 12    71 ms    71 ms    72 ms  po6.ar1.ord1.us.scnet.net [69.31.111.58]
 13    72 ms    71 ms    74 ms  61.po1.ar1.ord6.us.scnet.net [75.102.3.226]
 14    72 ms    74 ms    74 ms  as36352.po4.ar1.ord6.us.scnet.net [204.93.192.186]
 15    73 ms    71 ms    72 ms  host.colocrossing.com [205.234.152.250]
 16    72 ms    71 ms    74 ms  host.colocrossing.com [66.225.232.20]
 
Trace complete.
 



fiosuser

@frontiernet.net
Same issue last few nights in Gresham...

Here's the daytime tracert/speeds. I'll post new results if it happens again tonight




Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    1 ms    1 ms    1 ms  172.16.1.1
  2     4 ms     4 ms     4 ms  [Snip].bvtn.or.frontiernet.net [Snip]
  3     8 ms     4 ms     7 ms  50.38.7.57
  4    81 ms    82 ms    82 ms  ae2---0.cor02.ptld.or.frontiernet.net [74.40.1.165]
  5    96 ms    82 ms    82 ms  ae1---0.cor01.sttl.wa.frontiernet.net [74.40.2.154]
  6    86 ms    82 ms    82 ms  ae0---0.cor02.sttl.wa.frontiernet.net [74.40.3.138]
  7    81 ms    82 ms    82 ms  xe--11-0-0---0.cor01.mond.mn.frontiernet.net [74.40.5.45]
  8   103 ms    82 ms    82 ms  ae0---0.cor01.lkvl.mn.frontiernet.net [74.40.5.53]
  9    82 ms    82 ms    82 ms  ae4---0.cor01.chcg.il.frontiernet.net [74.40.5.50]
 10    83 ms    82 ms   104 ms  ae0---0.cor02.chcg.il.frontiernet.net [74.40.3.242]
 11    82 ms    82 ms    82 ms  ae1---0.cor01.asbn.va.frontiernet.net [74.40.2.194]
 12    81 ms    82 ms    82 ms  ae1---0.cbr01.asbn.va.frontiernet.net [74.40.2.174]
 13     *        *        *     Request timed out.
 14    89 ms    87 ms    87 ms  e2-18.tbr2.tl9.nac.net [209.123.11.57]
 15    92 ms    89 ms    94 ms  0.e1-4.tbr2.mmu.nac.net [209.123.10.77]
 16    89 ms    89 ms    89 ms  0.e1-1.tbr2.oct.nac.net [209.123.10.21]
 17    88 ms    89 ms    89 ms  vlan808.esd1.oct.nac.net [209.123.10.42]
 18    89 ms    89 ms    89 ms  www.dslreports.com [209.123.109.175]
 
Trace complete.
 

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    1 ms    1 ms    1 ms  172.16.1.1
  2     4 ms     4 ms     4 ms  [snip].bvtn.or.frontiernet.net [snip]
  3     8 ms     4 ms     7 ms  50.38.7.57
  4    81 ms    82 ms    82 ms  ae2---0.cor02.ptld.or.frontiernet.net [74.40.1.165]
  5    96 ms    82 ms    82 ms  ae1---0.cor01.sttl.wa.frontiernet.net [74.40.2.154]
  6    86 ms    82 ms    82 ms  ae0---0.cor02.sttl.wa.frontiernet.net [74.40.3.138]
  7    81 ms    82 ms    82 ms  xe--11-0-0---0.cor01.mond.mn.frontiernet.net [74.40.5.45]
  8   103 ms    82 ms    82 ms  ae0---0.cor01.lkvl.mn.frontiernet.net [74.40.5.53]
  9    82 ms    82 ms    82 ms  ae4---0.cor01.chcg.il.frontiernet.net [74.40.5.50]
 10    83 ms    82 ms   104 ms  ae0---0.cor02.chcg.il.frontiernet.net [74.40.3.242]
 11    82 ms    82 ms    82 ms  ae1---0.cor01.asbn.va.frontiernet.net [74.40.2.194]
 12    81 ms    82 ms    82 ms  ae1---0.cbr01.asbn.va.frontiernet.net [74.40.2.174]
 13     *        *        *     Request timed out.
 14    89 ms    87 ms    87 ms  e2-18.tbr2.tl9.nac.net [209.123.11.57]
 15    92 ms    89 ms    94 ms  0.e1-4.tbr2.mmu.nac.net [209.123.10.77]
 16    89 ms    89 ms    89 ms  0.e1-1.tbr2.oct.nac.net [209.123.10.21]
 17    88 ms    89 ms    89 ms  vlan808.esd1.oct.nac.net [209.123.10.42]
 18    89 ms    89 ms    89 ms  www.dslreports.com [209.123.109.175]
 
Trace complete.
 


fiosuser

@frontiernet.net
Same issues again tonight...







Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    1 ms    1 ms    1 ms  172.16.1.1
  2     4 ms     4 ms     4 ms  [snip].bvtn.or.frontiernet.net [snip]
  3    94 ms    92 ms    94 ms  50.38.7.57
  4   171 ms   182 ms   164 ms  ae2---0.cor02.ptld.or.frontiernet.net [74.40.1.165]
  5   168 ms   169 ms   169 ms  ae1---0.cor01.sttl.wa.frontiernet.net [74.40.2.154]
  6   171 ms   174 ms   169 ms  ae0---0.cor02.sttl.wa.frontiernet.net [74.40.3.138]
  7   168 ms   169 ms   187 ms  xe--11-0-0---0.cor01.mond.mn.frontiernet.net [74.40.5.45]
  8   166 ms   169 ms   169 ms  ae0---0.cor01.lkvl.mn.frontiernet.net [74.40.5.53]
  9   171 ms   172 ms   164 ms  ae4---0.cor01.chcg.il.frontiernet.net [74.40.5.50]
 10   166 ms   167 ms   172 ms  ae0---0.cor02.chcg.il.frontiernet.net [74.40.3.242]
 11   161 ms   169 ms     *     ae1---0.cor01.asbn.va.frontiernet.net [74.40.2.194]
 12   249 ms   172 ms   174 ms  ae1---0.cbr01.asbn.va.frontiernet.net [74.40.2.174]
 13     *        *        *     Request timed out.
 14   172 ms   176 ms   179 ms  e2-18.tbr2.tl9.nac.net [209.123.11.57]
 15   178 ms   174 ms   179 ms  0.e1-4.tbr2.mmu.nac.net [209.123.10.77]
 16   178 ms   179 ms   177 ms  0.e1-1.tbr2.oct.nac.net [209.123.10.21]
 17   179 ms   177 ms   177 ms  vlan808.esd1.oct.nac.net [209.123.10.42]
 18   172 ms   177 ms   179 ms  www.dslreports.com [209.123.109.175]
 
Trace complete.
 

chevelleman

join:2009-05-15
Troutdale, OR
I talked to a Frontier service rep on the phone tonight and he said that the Portland area has some problem that they are working on and it should be fixed in a couple days.


Ben J
Triple Play Architect
Premium
join:2011-09-16
Fort Wayne, IN
kudos:9
Was fixed this morning.

chevelleman

join:2009-05-15
Troutdale, OR
Thanks Ben for taking care of it.


fiosuser

@frontiernet.net
Ben,

Could you provide some insight on what the issue was? I'm curious.

Thanks.


Ben J
Triple Play Architect
Premium
join:2011-09-16
Fort Wayne, IN
kudos:9

1 recommendation

Each FIOS area is served by multiple load balanced circuits. If only a couple circuits in the group go down, the area stays up, but there may no longer be enough bandwidth to serve everybody simultaneously at peak hours (~4pm-12am), and congestion starts to occur. Now, this alone is not very remarkable, circuits go down all the time for a myriad of reasons, we fix them, and unless it's a major outage, customers usually don't even notice. The problem here was actually a flaw in the monitoring/provisioning process where the monitoring systems didn't think that a number of new circuits we recently installed were now "in service", and therefore the NOC wasn't getting alarms when these circuits had trouble.
--
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.

nightjars

join:2010-01-09
Bothell, WA
Ben,

First, I appreciate how helpful you've been regarding the problems that FiOS has had recently with performance. Your honesty and willingness to help is truly appreciated.

I am curious, is there any reason why Frontier does not do more proactive measurement of its network's performance? It seems that this most recent problem, as well as the problem I was having with my FiOS connection last month could have been quickly found if real time metrics were being collected regarding network performance. It seems bizarre that there are no monitoring traps designed to determine if there are such major performance issues occurring..