dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
56560
share rss forum feed

Action2

join:2010-06-29
Newman, IL
kudos:1
Reviews:
·Frontier Communi..
reply to firefighter15

Re: [Internet] For anyone seeing speed issues...

FireFighter, I emailed my area rep. and he said it would be fixed in about a month "give or take a few weeks." This is coming after the whole "It should be fixed by next month..." in January.

Looking over my speed test averages, I am starting to drift closer to my WISP average 1.04Mbit/s which isn't very impressive when comparing a land line DSL connection to a wireless link with thick trees in the way.


patrickp
Patrick

join:2002-05-03
Bloomington, IL
Reviews:
·Frontier Communi..

I'm located in central IL or Bloomington, IL to be exact and my 7.1/768 service was great for years until shortly after Frontier took over and now now during peak usage times like mid-afternoon until after midnight I'm lucky to get 1mg down when for years or since 7.1 became available I was getting 6.4 mg down and 720k up 24hrs a day.

There is congestion over the backbone between central IL and Chicago and affects all residential and business customers around here that I've heard from.
--
Patrick


StrandedBrit

join:2011-03-01
Ovid, MI
reply to Smith6612

I'm on 3m/768k service in Ovid, Michigan.

Have had the speed issues for several weeks now. Here's a quick download speed chart based on time of day:- 7am 2.8mb, 10am 2mb, 12pm 1.5mb, 3pm 1mb, 6pm 0.5mb, 10pm 0.4mb. Funnily enough my upload speed is always the same at 0.6mb.

Feel like I've been getting the runaround by CS too. I've called multiple times, troubleshooted my equipment etc. One tech finally told me that they were upgrading equipment and that there was no ETA on when it would be complete and to talk to Billing to get some type of credit.

I've also emailed various people at the organization, to which I have one reply saying we are looking into it.

So, my real question here is I have 2 other DSL options for my area. Netzero and Eathlink. Are these companies running their service thru the same hardware as Frontier? Would I just be getting the same slow service from them? I heard someone say that basically these lower level companies just rent lines from the likes of Frontier/Verizon.

Any input would be great.



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24

It's possible the resellers in your area are running off their own networks from the Frontier COs, but there would still be issues if Frontier's core network or the DSLAMs/remotes are still oversold.


StrandedBrit

join:2011-03-01
Ovid, MI
reply to Smith6612

Update: After finally getting to a boss in Michigan I was contacted by a manager in my area. Basically said that the Chigaco area upgrade was live but they were still having issues in Ovid and surrounding area which was being worked on and that the eta was end of next week, so by 3/13 I guess.

Wierd thing was when I got home and did a speedtest, it said my location was in Kansas somwhere. Speeds fluctuate depending on where the test server is located by generally checked out between 2-3mbps so that's much better, although latency seems to have crept up (used to have



Ohio

@verizon.net

Been having problems here in south central Ohio as well. This has been ongoing since the first of November. I'm on a 3mbps down 764kb up but usually only get around .30 down during the day. I was told back in January that this issue would be resolved 3/1/2011. As of today I am still pretty much unable to watch clips or download small content. I'm beginning to get fed up with this as we are closing in on 6 months since these "upgrades" began and yet I see little difference in my connection quality. Hope it gets fixed soon as I don't want to switch ISP's but I'm beginning to see I may have no choice.



Powell_OH

@verizon.net

Central Ohio here. Been having issues for a about a month. Just did a speed test, got 105kb/sec. I'm on the 3mb plan.

I too get the same response, "We're working on it." Unfortunately I think my only other choice is RR. I left them 2 years ago due to horrible drops. Every 30 min or so the connection would drop. Gave them 3 tech visits and 2 months to fix.

Now I'm going through this crap with Frontier. ISP's suck.


COjosh

join:2011-02-21
kudos:1
reply to StrandedBrit

NetZero and Earthlink are DIAL-UP PROVIDERS!

You would be getting even slower service from them.



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24

Earthlink I know does resell Cable and DSL service, however.



mr mac

@50.36.66.x
reply to Smith6612

southwest mich is have the same problems. I know 6 others in the area having the same problems. I was told to call the billing dept and ask for a credit and was told all they could do was drop my plan to a lower speed. If I need slower internet I wouldn't be a unhappy customer calling them. They couldn't tell me how long it was going to be like this in my area. I'm just go to keep calling every few day and maybe someone will have a answer


Toecutter

join:2011-02-21
Kewaskum, WI

3 edits
reply to Smith6612

Tracing route to www.l.google.com [74.125.225.20]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 1 ms 1 ms 1 ms dslrouter [192.168.1.1]
3 29 ms 29 ms 29 ms 10.34.54.1
4 179 ms 184 ms 184 ms so-1-2-2-0.CHI01-CORE-RTR3.verizon-gni.net [108.
57.128.8]
5 153 ms 141 ms 149 ms as0-0.chi01-bb-rtr1.verizon-gni.net [130.81.20.5
6]
6 246 ms 287 ms 245 ms 0.so-7-2-0.xl3.chi13.alter.net [152.63.64.169]
7 193 ms 159 ms 192 ms tengige0-4-2-0.gw2.chi13.alter.net [152.63.67.10
2]
8 213 ms 209 ms 196 ms google-gw.customer.alter.net [65.195.243.218]
9 269 ms 238 ms 300 ms 209.85.254.122
10 36 ms 31 ms 31 ms 64.233.174.173
11 189 ms 189 ms 194 ms 74.125.225.20

Trace complete.

---------------------------------------------------------------

Pinging 108.57.128.8 with 64 bytes of data:

Reply from 108.57.128.8: bytes=64 time=186ms TTL=62
Reply from 108.57.128.8: bytes=64 time=185ms TTL=62
Reply from 108.57.128.8: bytes=64 time=214ms TTL=62
Reply from 108.57.128.8: bytes=64 time=280ms TTL=62

Ping statistics for 108.57.128.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 280ms, Average = 216ms

---------------------------------------------------------------

Pinging 108.57.128.8 with 32 bytes of data:

Reply from 108.57.128.8: bytes=32 time=206ms TTL=62
Reply from 108.57.128.8: bytes=32 time=172ms TTL=62
Reply from 108.57.128.8: bytes=32 time=166ms TTL=62
Reply from 108.57.128.8: bytes=32 time=187ms TTL=62
Reply from 108.57.128.8: bytes=32 time=186ms TTL=62
Reply from 108.57.128.8: bytes=32 time=184ms TTL=62
Reply from 108.57.128.8: bytes=32 time=186ms TTL=62
Reply from 108.57.128.8: bytes=32 time=188ms TTL=62
Reply from 108.57.128.8: bytes=32 time=187ms TTL=62
Reply from 108.57.128.8: bytes=32 time=287ms TTL=62
Reply from 108.57.128.8: bytes=32 time=166ms TTL=62
Reply from 108.57.128.8: bytes=32 time=186ms TTL=62
Reply from 108.57.128.8: bytes=32 time=185ms TTL=62
Reply from 108.57.128.8: bytes=32 time=184ms TTL=62
Reply from 108.57.128.8: bytes=32 time=280ms TTL=62
Reply from 108.57.128.8: bytes=32 time=366ms TTL=62
Reply from 108.57.128.8: bytes=32 time=205ms TTL=62
Reply from 108.57.128.8: bytes=32 time=218ms TTL=62
Reply from 108.57.128.8: bytes=32 time=261ms TTL=62
Reply from 108.57.128.8: bytes=32 time=400ms TTL=62
Reply from 108.57.128.8: bytes=32 time=277ms TTL=62
Reply from 108.57.128.8: bytes=32 time=288ms TTL=62

--------------------------------------------------------------

I am a former Verizon customer in SE Wisconsin. I had no problems with my DSL when it was being run by Verizon. I guess Frontier took over in about July, and things were fine up until late December. Since then I have been experiencing high latency issues. I finally got tired of not being able to watch anything on Netflix in the evening so I finally contacted Frontier tech support.

The woman the I spoke with was quite friendly, and gave me a very straightforward answer as to what is going on. I told her that I was experiencing high latency issues at 108.57.128.8. She then ran the usual battery of line tests, had me run a speed test (2714 kbps up / 695 kbps down), and all of the test indicated that there was nothing wrong on my end, or with the line. She then admitted that Frontier is routing something like five states worth of traffic through just a few servers in Chicago. She said that they are adding more capacity, but it probably won't be done until mid-May. Unfortunately, she said that there was nothing that she could do for me, and to please bear with them for another month or two.

I really appreciate her candor, but I have about had it with Frontier due to their congestion, and I don't have a warm fuzzy that this issue is going to be fixed by mid-May. Unfortunately, the only other player in my area is Charter, who I previously fired for dropping my connection about twice a day. Given the alternative, I guess I could wait until mid-May and see how things progress before I pull the plug.


tmarsh1518

join:2011-03-21
reply to Smith6612

I have noticed widely fluctuating download speeds for the past few months which coincided with the switch from verizion to frontier. I live in north central Indiana and have the 7.1/768 plan. I've seen speeds as low as 170 Kbps some evenings. Last Wednesday evening the service was having problems connecting to some websites and tracert showed an issue at certain hops. Service was out or unreliable for about 18 hours. On Friday I also lost connectivity briefly in the afternoon. I didn't want to go through the hassle of changing ISPs but I've had enough of Frontier. I am having cable broadband installed next weekend.


Festivus

join:2011-04-02
Powell, OH
reply to Toecutter

Same issues with me in central ohio. I connect through somewhere near Chicago though, as you noted many people are. Getting .43Mbps as of a few minutes ago, sometimes as slow as .14. At 5:00AM when I get up for work it's 3Mbps like I'm supposed to be getting of course.

Mid-may? I can't wait that long. But I'm the same boat as you are. I left time warner due to connection drops every 30 min. It would disconnect my work vpn if I was working from home. If that happened too often I would get locked out of my account. So I left them for Verizon. All was fine until a couple of months ago.

This is BS.



StumpFreak

@frontiernet.net
reply to Smith6612

Hey Smith6612, been seeing issues for about 5 months now, thought I'd toss this up here for you to take a look at and see if you have any ideas.

Traceroute
----------
tracert www.google.com

Tracing route to www.google.com [170.215.255.115]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.254.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 230 ms 273 ms * ple01.mdtw.ny.frontiernet.net [170.215.255.115]

6 243 ms 242 ms 227 ms ple01.mdtw.ny.frontiernet.net [170.215.255.115]

Trace complete.

Pingtest
--------
ping 170.215.255.115 -t

Pinging 170.215.255.115 with 32 bytes of data:

Reply from 170.215.255.115: bytes=32 time=348ms TTL=60
Reply from 170.215.255.115: bytes=32 time=219ms TTL=60
Reply from 170.215.255.115: bytes=32 time=348ms TTL=60
Reply from 170.215.255.115: bytes=32 time=354ms TTL=60
Reply from 170.215.255.115: bytes=32 time=333ms TTL=60
Reply from 170.215.255.115: bytes=32 time=361ms TTL=60
Reply from 170.215.255.115: bytes=32 time=282ms TTL=60
Reply from 170.215.255.115: bytes=32 time=352ms TTL=60
Reply from 170.215.255.115: bytes=32 time=344ms TTL=60
Reply from 170.215.255.115: bytes=32 time=359ms TTL=60
Reply from 170.215.255.115: bytes=32 time=330ms TTL=60
Reply from 170.215.255.115: bytes=32 time=305ms TTL=60
Reply from 170.215.255.115: bytes=32 time=284ms TTL=60
Reply from 170.215.255.115: bytes=32 time=288ms TTL=60
Reply from 170.215.255.115: bytes=32 time=311ms TTL=60
Reply from 170.215.255.115: bytes=32 time=254ms TTL=60
Reply from 170.215.255.115: bytes=32 time=291ms TTL=60
Reply from 170.215.255.115: bytes=32 time=156ms TTL=60
Reply from 170.215.255.115: bytes=32 time=280ms TTL=60
Reply from 170.215.255.115: bytes=32 time=246ms TTL=60
Reply from 170.215.255.115: bytes=32 time=345ms TTL=60
Reply from 170.215.255.115: bytes=32 time=292ms TTL=60
Reply from 170.215.255.115: bytes=32 time=301ms TTL=60
Reply from 170.215.255.115: bytes=32 time=194ms TTL=60
Reply from 170.215.255.115: bytes=32 time=231ms TTL=60
Reply from 170.215.255.115: bytes=32 time=287ms TTL=60
Reply from 170.215.255.115: bytes=32 time=348ms TTL=60
Reply from 170.215.255.115: bytes=32 time=259ms TTL=60
Reply from 170.215.255.115: bytes=32 time=271ms TTL=60
Reply from 170.215.255.115: bytes=32 time=138ms TTL=60
Reply from 170.215.255.115: bytes=32 time=244ms TTL=60
Reply from 170.215.255.115: bytes=32 time=370ms TTL=60
Reply from 170.215.255.115: bytes=32 time=291ms TTL=60
Reply from 170.215.255.115: bytes=32 time=386ms TTL=60
Reply from 170.215.255.115: bytes=32 time=373ms TTL=60
Reply from 170.215.255.115: bytes=32 time=264ms TTL=60
Request timed out.
Reply from 170.215.255.115: bytes=32 time=305ms TTL=60
Reply from 170.215.255.115: bytes=32 time=313ms TTL=60
Reply from 170.215.255.115: bytes=32 time=249ms TTL=60
Reply from 170.215.255.115: bytes=32 time=173ms TTL=60
Reply from 170.215.255.115: bytes=32 time=321ms TTL=60
Reply from 170.215.255.115: bytes=32 time=298ms TTL=60
Reply from 170.215.255.115: bytes=32 time=382ms TTL=60
Reply from 170.215.255.115: bytes=32 time=317ms TTL=60
Reply from 170.215.255.115: bytes=32 time=321ms TTL=60
Reply from 170.215.255.115: bytes=32 time=356ms TTL=60
Reply from 170.215.255.115: bytes=32 time=346ms TTL=60
Reply from 170.215.255.115: bytes=32 time=261ms TTL=60
Reply from 170.215.255.115: bytes=32 time=226ms TTL=60
Reply from 170.215.255.115: bytes=32 time=326ms TTL=60
Reply from 170.215.255.115: bytes=32 time=316ms TTL=60
Reply from 170.215.255.115: bytes=32 time=292ms TTL=60
Reply from 170.215.255.115: bytes=32 time=295ms TTL=60
Reply from 170.215.255.115: bytes=32 time=374ms TTL=60
Reply from 170.215.255.115: bytes=32 time=295ms TTL=60
Reply from 170.215.255.115: bytes=32 time=335ms TTL=60
Reply from 170.215.255.115: bytes=32 time=266ms TTL=60
Reply from 170.215.255.115: bytes=32 time=253ms TTL=60
Reply from 170.215.255.115: bytes=32 time=286ms TTL=60
Reply from 170.215.255.115: bytes=32 time=314ms TTL=60
Reply from 170.215.255.115: bytes=32 time=261ms TTL=60
Request timed out.
Reply from 170.215.255.115: bytes=32 time=310ms TTL=60
Reply from 170.215.255.115: bytes=32 time=282ms TTL=60
Reply from 170.215.255.115: bytes=32 time=207ms TTL=60
Reply from 170.215.255.115: bytes=32 time=260ms TTL=60
Reply from 170.215.255.115: bytes=32 time=176ms TTL=60
Reply from 170.215.255.115: bytes=32 time=288ms TTL=60
Reply from 170.215.255.115: bytes=32 time=192ms TTL=60
Reply from 170.215.255.115: bytes=32 time=230ms TTL=60
Reply from 170.215.255.115: bytes=32 time=151ms TTL=60
Reply from 170.215.255.115: bytes=32 time=234ms TTL=60
Reply from 170.215.255.115: bytes=32 time=284ms TTL=60
Reply from 170.215.255.115: bytes=32 time=113ms TTL=60
Reply from 170.215.255.115: bytes=32 time=343ms TTL=60
Reply from 170.215.255.115: bytes=32 time=327ms TTL=60
Reply from 170.215.255.115: bytes=32 time=182ms TTL=60
Reply from 170.215.255.115: bytes=32 time=268ms TTL=60
Reply from 170.215.255.115: bytes=32 time=348ms TTL=60
Reply from 170.215.255.115: bytes=32 time=367ms TTL=60
Reply from 170.215.255.115: bytes=32 time=283ms TTL=60
Reply from 170.215.255.115: bytes=32 time=227ms TTL=60
Reply from 170.215.255.115: bytes=32 time=307ms TTL=60
Reply from 170.215.255.115: bytes=32 time=258ms TTL=60
Reply from 170.215.255.115: bytes=32 time=298ms TTL=60
Reply from 170.215.255.115: bytes=32 time=369ms TTL=60
Request timed out.
Reply from 170.215.255.115: bytes=32 time=289ms TTL=60
Reply from 170.215.255.115: bytes=32 time=376ms TTL=60
Reply from 170.215.255.115: bytes=32 time=318ms TTL=60
Reply from 170.215.255.115: bytes=32 time=351ms TTL=60
Reply from 170.215.255.115: bytes=32 time=395ms TTL=60
Reply from 170.215.255.115: bytes=32 time=333ms TTL=60
Reply from 170.215.255.115: bytes=32 time=415ms TTL=60
Reply from 170.215.255.115: bytes=32 time=346ms TTL=60
Reply from 170.215.255.115: bytes=32 time=235ms TTL=60
Reply from 170.215.255.115: bytes=32 time=354ms TTL=60
Reply from 170.215.255.115: bytes=32 time=295ms TTL=60
Reply from 170.215.255.115: bytes=32 time=391ms TTL=60
Reply from 170.215.255.115: bytes=32 time=385ms TTL=60
Reply from 170.215.255.115: bytes=32 time=365ms TTL=60
Reply from 170.215.255.115: bytes=32 time=297ms TTL=60
Reply from 170.215.255.115: bytes=32 time=366ms TTL=60
Reply from 170.215.255.115: bytes=32 time=387ms TTL=60
Reply from 170.215.255.115: bytes=32 time=245ms TTL=60
Request timed out.
Reply from 170.215.255.115: bytes=32 time=356ms TTL=60
Reply from 170.215.255.115: bytes=32 time=413ms TTL=60
Reply from 170.215.255.115: bytes=32 time=262ms TTL=60
Reply from 170.215.255.115: bytes=32 time=339ms TTL=60
Reply from 170.215.255.115: bytes=32 time=220ms TTL=60
Reply from 170.215.255.115: bytes=32 time=349ms TTL=60
Reply from 170.215.255.115: bytes=32 time=361ms TTL=60
Reply from 170.215.255.115: bytes=32 time=358ms TTL=60
Reply from 170.215.255.115: bytes=32 time=269ms TTL=60
Reply from 170.215.255.115: bytes=32 time=383ms TTL=60
Reply from 170.215.255.115: bytes=32 time=270ms TTL=60
Request timed out.
Reply from 170.215.255.115: bytes=32 time=242ms TTL=60
Reply from 170.215.255.115: bytes=32 time=334ms TTL=60

Ping statistics for 170.215.255.115:
Packets: Sent = 121, Received = 116, Lost = 5 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 415ms, Average = 299ms

Notes
-----
The second and fourth lost pings are where the download started and stopped, respectively. Download speeds remained around 25kBps, and I'm on the 3Mbps/384kbps package. I've documented more of my trouble with Frontier here - »bit.ly/hHk41Q - if you'd like to take a look.



Backatcha

@frontiernet.net
reply to Smith6612

These are the results of a trace route to Frontiernet.net. As you can see, the results are pitiful.

1 1 ms 1 ms 1 ms 192.168.254.254

2 14 ms 13 ms 13 ms 170-215-105-1.br1.frt.ga.frontiernet.net [170.215.105.1]

3 77 ms 76 ms 73 ms 74.40.30.25

4 74 ms * 80 ms xe-0-2-0--0.cor02.atln.ga.frontiernet.net [74.40.2.237]

5 * * 76 ms ae0---0.cbr01.atln.ga.frontiernet.net [74.40.2.82]

6 14 ms 15 ms 16 ms te-9-2.car1.Atlanta4.Level3.net [4.53.233.133]

7 14 ms 15 ms 16 ms vlan51.csw1.Atlanta2.Level3.net [4.69.150.62]

8 72 ms 48 ms 63 ms ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]

9 28 ms 27 ms 30 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

10 30 ms 31 ms 29 ms ae-71-71.csw2.Washington1.Level3.net [4.69.134.134]

11 29 ms 29 ms 29 ms ae-24-70.car4.Washington1.Level3.net [4.69.149.70]

12 30 ms 31 ms 30 ms CO-LOCATION.car4.Washington1.Level3.net [4.79.170.254]

13 * * * Request timed out.

14 * * * Request timed out.

15


Festivus

join:2011-04-02
Powell, OH
reply to Smith6612

I've been told that issues might be resolved in north central Ohio. I've been consistently getting anywhere from 2.75Mbps to 3.12Mbps down on the 3Mbps plan the past 3 days.

My speedtest now connects through Columbus, not Chicago.

Here's an excerpt from the email that Frontier sent to me this morning:

"Thanks again for your patience and for reaching out to me regarding your internet speed. As of today I was able to get you migrated to a new pathway and you should see an increase in your connection speed. This is just one step in the process and as other projects are completed you will continue to see an increase in performance. I apologize for the delay and again thank you for giving us the opportunity to upgrade our network."



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Reviews:
·Verizon Online DSL
·Frontier Communi..

1 edit
reply to StumpFreak

Your trace route suggests a Firewall at play messing it up, though the latency is obviously bad. It's the same issue everyone else seems to be getting with Frontier's DSL service. I'm downloading the podcast right now from the blog post you linked above. I'll interested to hear it . Anyhow, Frontier will need to bring in more bandwidth into your area, obviously. If you can get a hold of a local tech for your area, bring them up on the issue.

In case you haven't come across any of my previous threads here regarding the slow-downs that used to occur in my area, I'll tell you what I did to go about getting the issue solved. First time a slow-down took place, I gave Frontier a call during prime time. They checked out my modem, which I knew wasn't at fault, as well as my DSL Statistics, which were as expected, fine. Rep didn't even question the line or the modem. He then asked me to run a Speedtest from their Speed testing site. Came back with half of my normal speed the first try, and then 240kbps the next result for the download. The tech put in a ticket for me regarding slow speeds, which resulted in a tech from the local CO (Who I have become buddies with) to come out and double check things. Of course, the speeds were fine, but he told me that there were tons of tickets open regarding slow speeds (couple hundred at least) for my area alone. He gave me his cell phone number, and two weeks later, speeds returned to normal during the night time hours.

We had another slow-down during the Fall months in my area again. This time, I simply gave my contact at the local CO a call and asked him what was going on. He told me that they had installed some new Load Balancing equipment that was supposed to help increase telephone calling capacity and reliability in the area. I guess indirectly, it also included the Internet service with it as I noticed shortly after Frontier put the upgrades in, my speeds once again, began to dip towards the evening hours. Line Quality Tests tended to show the problem was in Rochester some nights, whereas other nights it would show up in the typical hops where the CO is. Asked my contact two weeks later if he's heard of anything regarding slow-downs, and he mentioned that they were having some trouble with their load balancing system. Fast forward a few weeks later, no more slow-downs. Haven't seen a slow-down since the fall.

@Backatcha: Your issue isn't from the issues people are seeing with the Chicago network directly, but it does look to be a local bandwidth issue. They simply need to bring in more bandwidth to your Central Office.

@Festivus: Feel free to keep us updated on anything being developed. Glad to hear your speed has been returning.


bd4

join:2005-05-27
reply to Smith6612

Need some help, at night around 8-10 pm eastern time getting horrible packet loss and high latency.

C:\Users\Brian>tracert dslreports.com

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 ping -n 10 www.google.com

Pinging www.l.google.com [74.125.225.51] with 32 bytes of data:
Reply from 74.125.225.51: bytes=32 time=32ms TTL=57
Request timed out.
Reply from 74.125.225.51: bytes=32 time=41ms TTL=57
Reply from 74.125.225.51: bytes=32 time=68ms TTL=57
Request timed out.
Reply from 74.125.225.51: bytes=32 time=62ms TTL=57
Reply from 74.125.225.51: bytes=32 time=66ms TTL=57
Request timed out.
Reply from 74.125.225.51: bytes=32 time=57ms TTL=57
Reply from 74.125.225.51: bytes=32 time=56ms TTL=57

Ping statistics for 74.125.225.51:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 68ms, Average = 54ms

C:\Users\Brian>ping 184.17.64.1 -t

Pinging 184.17.64.1 with 32 bytes of data:
Reply from 184.17.64.1: bytes=32 time=48ms TTL=127
Reply from 184.17.64.1: bytes=32 time=56ms TTL=127
Reply from 184.17.64.1: bytes=32 time=37ms TTL=127
Request timed out.
Request timed out.
Reply from 184.17.64.1: bytes=32 time=61ms TTL=127
Reply from 184.17.64.1: bytes=32 time=43ms TTL=127
Reply from 184.17.64.1: bytes=32 time=59ms TTL=127
Reply from 184.17.64.1: bytes=32 time=53ms TTL=127
Reply from 184.17.64.1: bytes=32 time=60ms TTL=127
Reply from 184.17.64.1: bytes=32 time=23ms TTL=127
Reply from 184.17.64.1: bytes=32 time=54ms TTL=127
Reply from 184.17.64.1: bytes=32 time=59ms TTL=127
Reply from 184.17.64.1: bytes=32 time=46ms TTL=127
Request timed out.


delta772lr

join:2011-10-21
Sturgis, MI

Same here, in southwest lower Michigan on the MI/IN border. This has been going on for the better part of 2 weeks now and is the second time this year it has happened. Paying for 7.1 mb down but we are lucky to see .40~.50. I've been on the phone with Frontier twice and finally got a tech from the local office today to admit they had screwed something up during a changeover from Verizon to Frontier and that 'hundreds' of other people were having the same problem.

My only concerns with this is that it shouldn't take two weeks to resolve and this was also the excuse used when we had problems last Spring as well. I work from home and this is becoming a huge issue. We switched from Charter 7 or 8 years ago due to frequent drops and never had ANY issues with Verizon. I don't even remember ever power cycling the modem.



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
reply to bd4

Packet loss typically indicates congestion or a faulty link. Has Frontier attempted to fix both of the above issues by adding more capacity, for example?


stephen62

join:2010-09-02
Chesterton, IN

This sounds a lot like my "down 6 or 7pm-12am" problem in Chesterton, IN which has been going on every day since Oct. 10. I have been told by a local manager that it is "an engineering problem" (no more details than that), that it is being worked on, and that I will be informed regarding any updates. The same manager contacted me over the weekend asking if things had improved. I replied Sunday that things had not. This manager promised to contact the next manager above. Last night I didn't lose service until 7:45pm, which is a slight improvement, but not exactly acceptable.


koritina

join:2007-12-24
Leesburg, OH
reply to Smith6612

Paying for 1.5Meg up

Constant lag between 6-7pm until Midnight every night. Been going this way for quite awhile now... All we've been told is "The district manager is on the same connection, it'll get fixed soon."

Area is SW Ohio.

Morning Ping:
Pinging 10.33.3.3 with 32 bytes of data:
Reply from 10.33.3.3: bytes=32 time=262ms TTL=126
Reply from 10.33.3.3: bytes=32 time=76ms TTL=126
Reply from 10.33.3.3: bytes=32 time=36ms TTL=126
Reply from 10.33.3.3: bytes=32 time=37ms TTL=126
Reply from 10.33.3.3: bytes=32 time=116ms TTL=126
Reply from 10.33.3.3: bytes=32 time=177ms TTL=126
Reply from 10.33.3.3: bytes=32 time=205ms TTL=126
Reply from 10.33.3.3: bytes=32 time=111ms TTL=126
Reply from 10.33.3.3: bytes=32 time=181ms TTL=126
Reply from 10.33.3.3: bytes=32 time=92ms TTL=126
Reply from 10.33.3.3: bytes=32 time=74ms TTL=126
Reply from 10.33.3.3: bytes=32 time=124ms TTL=126
Reply from 10.33.3.3: bytes=32 time=149ms TTL=126
Reply from 10.33.3.3: bytes=32 time=216ms TTL=126
Reply from 10.33.3.3: bytes=32 time=128ms TTL=126
Reply from 10.33.3.3: bytes=32 time=114ms TTL=126
Reply from 10.33.3.3: bytes=32 time=80ms TTL=126
Reply from 10.33.3.3: bytes=32 time=66ms TTL=126
....
Reply from 10.33.3.3: bytes=32 time=443ms TTL=126

Ping statistics for 10.33.3.3:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 443ms, Average = 208ms

Morning Tracert:
Tracing route to yahoo.com [98.139.180.149]
over a maximum of 5 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 56 ms 35 ms 35 ms 10.33.3.3
3 * * * Request timed out.
4 83 ms 99 ms 174 ms 74.40.1.125
5 312 ms 356 ms 415 ms 74.40.1.93

Trace complete.

Evening Ping:
Pinging 10.33.3.3 with 32 bytes of data:
Reply from 10.33.3.3: bytes=32 time=232ms TTL=126
Reply from 10.33.3.3: bytes=32 time=271ms TTL=126
Reply from 10.33.3.3: bytes=32 time=426ms TTL=126
Reply from 10.33.3.3: bytes=32 time=358ms TTL=126
Reply from 10.33.3.3: bytes=32 time=255ms TTL=126
Reply from 10.33.3.3: bytes=32 time=291ms TTL=126
Reply from 10.33.3.3: bytes=32 time=249ms TTL=126
Reply from 10.33.3.3: bytes=32 time=306ms TTL=126
Reply from 10.33.3.3: bytes=32 time=306ms TTL=126
Reply from 10.33.3.3: bytes=32 time=279ms TTL=126
Reply from 10.33.3.3: bytes=32 time=318ms TTL=126
Reply from 10.33.3.3: bytes=32 time=302ms TTL=126
Reply from 10.33.3.3: bytes=32 time=354ms TTL=126
Reply from 10.33.3.3: bytes=32 time=332ms TTL=126
Reply from 10.33.3.3: bytes=32 time=263ms TTL=126
Reply from 10.33.3.3: bytes=32 time=314ms TTL=126
Reply from 10.33.3.3: bytes=32 time=316ms TTL=126
Reply from 10.33.3.3: bytes=32 time=264ms TTL=126
Reply from 10.33.3.3: bytes=32 time=245ms TTL=126
Reply from 10.33.3.3: bytes=32 time=167ms TTL=126
Reply from 10.33.3.3: bytes=32 time=303ms TTL=126
Reply from 10.33.3.3: bytes=32 time=328ms TTL=126
Reply from 10.33.3.3: bytes=32 time=337ms TTL=126
Reply from 10.33.3.3: bytes=32 time=528ms TTL=12
....
Reply from 10.33.3.3: bytes=32 time=78ms TTL=126
Reply from 10.33.3.3: bytes=32 time=148ms TTL=126

Ping statistics for 10.33.3.3:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 528ms, Average = 262ms

Evening Tracert:
Tracing route to yahoo.com [98.139.180.149]
over a maximum of 5 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 175 ms 246 ms 165 ms 10.33.3.3
3 * * * Request timed out.
4 240 ms 205 ms 242 ms 74.40.1.125
5 285 ms 227 ms 241 ms 74.40.1.93

Trace complete.

Expand your moderator at work

Hyway

join:2007-07-08
Franklinton, NC
reply to Smith6612

Re: [Internet] For anyone seeing speed issues...

I just got off the phone with tech support- they keep saying it's a line attenuation problem- but we all know its a congestion issue-all the service guys that have come out to the house say this-so i am going to keep calling 2-3 times a week-thinking about making a video and sending to my tv station with hopes that someday they will get the congestion fixed--Doubt it will be before i get a new isp.
Download Speed: 227 kbps (28.4 KB/sec transfer rate)
Upload Speed: 265 kbps (33.1 KB/sec transfer rate)
Sunday, November 13, 2011 10:34:36 AM

Download Speed: 501 kbps (62.6 KB/sec transfer rate)
Upload Speed: 275 kbps (34.4 KB/sec transfer rate)
Sunday, November 13, 2011 10:38:00 AM

Download Speed: 723 kbps (90.4 KB/sec transfer rate)
Upload Speed: 311 kbps (38.9 KB/sec transfer rate)
Sunday, November 13, 2011 10:45:43 AM

Download Speed: 328 kbps (41 KB/sec transfer rate)
Upload Speed: 259 kbps (32.4 KB/sec transfer rate)
Sunday, November 13, 2011 10:47:34 AM

Connection Rate (Down/Up): 1790 Kbps / 447 Kbps

Yeah right.



Weaverville

@50.55.86.x

Big problems here in Weaverviile NC. Started to get bad in October
and got worse again this past week. So this is a Frontier-wide congestion problem rather than a local problem?


fwmike

join:2011-11-23
Fort Wayne, IN
reply to Smith6612

I've been experiencing slow FIOS download speeds here in Fort Wayne, IN for the past week. I'm paying for 25/25, and while upload speeds are ok, download speeds are consistently around 1.5 ~ 2.5 Mbps. Time of day does not matter, nor does day of the week. It is consistent on 3 different PCs. I've reset the router, reset the ONT, and have gone to every speedtest site known to mankind.

They are sending a new router out this week, but I do not think that is the issue at all. Unfortunately, I have a MoCA connection, so I am not able to bypass the router to test a direct connection. Frustration does not even begin to explain my feelings at this moment.







weaverville

@50.55.47.x

Having Frontier DSL problems? You've got to let people know; elected reps, media, state regulators, neighbors, FCC, social media etc. Probably not going to get much done posting here.


fwmike

join:2011-11-23
Fort Wayne, IN
reply to fwmike

My slow download speeds were fixed. It was an incorrect cross-connect on their end. It was built to give me 2.5 Mbps instead of 25 Mbps. I can see one person accidentally overlooking this. But I called and talked to 5 different people. How could they all have missed this? Absolutely ridiculous.



Weaverville

@50.55.45.x
reply to weaverville

Day 21 of my DSL disaster here in Weaverville. Yesterday was actually good but today it is back into sort of a start/stop mode



Weaverville

@50.55.45.x

Frontier Communications 2011 Proxy Report: Are these guys worth the
kind of money they are being paid if they can't keep your DSL working

»phx.corporate-ir.net/External.Fi···PTM=&t=1