Does Verizon Fios throttle updates?

I am seeing this as well. I ran across something about changing DNS settings on my FIOS router - which I did to Google - and speed increased slightly then decreased again. iOS 8 reporting 30-40 hours. I am now just trying to download the iTunes update at 244 MB and I have over 2 hours of remaining time. If I connect to my work computer (a university computer system but not VPN) remotely, I was able to run the update downloads to that computer in minutes.

what the heck ??

HA glad im not the old one (sorry misery loves company)

I tried to update my iPad to IOS8 would not eve try though the iPad. When I tried to do it through I tunes it estimated 135 hours, and the update your talking about has 19hours on it right now and its 139mb.

Their speed test is clocking my connection currently at around 1-9 for download on a 35/35 package absolutely insane, It may have to do with all this net neutrality garbage they are involved in, only thing I can think of, but I just came over from Comcast and have been disappointed between monopalized router and nothing but slow everything as far as speeds go.

Many people here have the same problem with Verizon FiOS.

http://www.dslreports.com/forum/r29544596-FIOS-horrible-Apple-download-speeds.

It is unclear to me whether the problem is caused by Verizon FiOS, or by Apple's new CDN (content distribution network).

One of the fixes that has worked is to change the DNS server that you use. This page has a list of alternative DNS server iPs,

http://pcsupport.about.com/od/tipstricks/a/free-public-dns-servers.htm

I changed the DNS servers in the FiOS Actiontec Router. The sign in info is on the label. Go to Main, My Network, Network Connections, click Edit on Broadband Connection, then Settings. Change DNS Server from Automatic to Use the following ... and enter the IP address from the link above.

I first tried Google, then Level3, then OpenDNS Home. The first two had no effect, but with the third, instead of indicating that the download would take 34 hours, it said 8 minutes which turned out to be accurate. I now have iOS 8 on my iPad. Apparently, it is somewhat random which DNS server will work, and some have reported that while one DNS server worked well for one download, it did not work so well later. This has happened to me. When I try to download the iOS update for my iPhone, I am back to (now) a 62 hour estimated download time. I will probably try some more different DNS servers to see if I can get it done, or else just give up and go somewhere tomorrow where Verizon FiOS is not the Internet provider.

Others in the thread above mentioned using a VPN, but I don' have one.

I don't understand why this problem is not in the news, as there must be many, many people with the same problem.

This did it! Thanks so much for list JDBartram.

I also turned off "Internet Connection Fastpath" in the Broadband settings

and made sure I did this:

OS X: How to reset the DNS cache

Lastly - I had to use the "Public-Root" DNS as the first 3 on the list didn't work for me right off.

My time went from 26+ hours to 11 minutes - finally.

when my iPad and phone are done updating - I'd like to play around with that "fast path" option and the DNS flush utility and see if I can track down what the bottleneck is.

best wishes and thanks again

Hmmm Ill try this when I get home tonight and report back. crossing my fingers

I am pretty sure this is just a Verizon Fios issue and that they should be ashamed!!! It has nothing to do with Apple servers. I updated seven devices in only minutes each at my home using Comcast ranging, in time, from when ios8 was released to several days later. I tried to help my mom update her iphone in her house using Verizon Fios with a 50 up and down connection. (Speed checked right before each attempt to update.) I tried wirelessly using just the phone and wired by connecting to my MacBook Air and using itunes. About 25 attempts over three days produced results that varied from 35-79 hours. I finally gave up and drove the phone home to my house. it took me 1 hour to drive home, update to ios8 over Comcast, install Swype and a few other apps, and drive the phone back to her house.

Option A - As a community of consumers, raise holy **** with Verizon. It really is unacceptable.

Option B - Switch to Comcast!!!

P.S. Comcast could have field day with this from a marketing perspective.

I was having the same issue trying to update my Apple TV and my iPhone for the last couple of days. The download times were showing as 18 hours and over 1 day, respectively. I was not having speed issues with anything else, interestingly.

I contacted Verizon support three times over chat. The last gentlemen I repeatedly told I was going to drop Verizon FiOS if they didn't fix the issue. He kept trying to say it was an Apple issue (e.g. overloaded due to iPhone release, CDN change, yadda yadda). I knew this was BS because at work I was able to download iOS 8 in 5 minutes (yes, I realize this is not an apples-to-apples comparison, but still).

Anyway, after closing a very frustrating chat window I notice a couple of minutes later that my internet service went out. I went downstairs to check the router and noticed it was recycling. It recycled again a couple of minutes later. I realized then that Verizon was doing it remotely. Aha!

Once it finished recycling the second time, I tried downloading the software updates from Apple again. Success! I was able to download both in minutes, not hours or days.

So, did Verizon simply recycle the router and that cleared up the issue or did Verizon do something a little more? I leave it to everyone's own cynicism to answer that question.

It would be very interesting to know exactly what Verizon did when they recycled telliott5's router. I had given up trying different DNS servers and signed up for a VPN ($12 for 50 GB from PrivateTunnel), so I am not aware of exactly when the upgrades started to work over FiOS. My neighbor who also has FiOS was able to upgrade on the evening of September 25 and I was able to upgrade my two Apple TVs on the 26th (which I had not been able to do before) so it was apparently OK at least by the 25th. I wonder if telliott5's call was the straw that broke the camel's back and convinced them there was a problem?

If anyone sees an article describing exactly what the problem was, I would appreciate them posting a link here.