One more thing... In the days we were on TWC my phone updates always lagged the action in sports by 45 seconds to a minute, since getting Google Fiber my phone updates now happen before the the action happens on the TV.

Odd... One has to wonder how that dealy might now be happening...

I've had mine since Friday. The install went sorta smoothly, but so far I am enjoying having it.

On the first day I had some lag between the remote and the box, and a couple of reboots, but none since then. I really like the "previous" button on this, and how it works ( I was concerned about losing the "last 4" option from DirecTV). The internet is obviously quite a bit faster, though we don't do much other than browse on our phones in our household. Maybe we will do the Netflix thing at some point. I also like how I can stream YouTube from my phone right to the TV. That's a fun little option that'll get used a lot ("Hey, honey, look at this idiot!"). Actually, the phone app is great overall, and also fun to screw with the family when I'm not in the room.

You need to have them come back out with new equipment or it is missing an update.

Most of the people in my neighborhood who had TWC are seeing the same thing, so I don't think it's anything that's broken. But folks who had Uverse and some who had DirecTV are seeing things as better.

Perhaps TWC was just better than I thought...

My DirecTV remote is super laggy. Even turning on the TV takes forever.

Got the googles today. Time to download the entire internet.

I could tell somebody else got on, my hourly download tests went from 940Mbs/940Mbs up/down to 939Mbs/939Mbs up/down, and my work Lync audio/video sucked too! Wait, Lync audio/video always sucks!

:cuss::cuss::cuss::cuss::cuss::cuss:

Do yourself a favor and sign up for Backblaze to get all your shit backed up offsite.

The upload is where you really feel the gig.

Seems like pretty much every day I lose internet connectivity for a minute or so before it gets reestablished. Kind of starting to get annoying.

I started a constant ping to 192.119.17.7 and 192.119.17.70 (the first couple pingable devices that I pulled from a trace to cisco.com [tracert -4 cisco.com]) from a desktop that's hardwired to the network box just to see if I was going nuts. I've missed a few pings.

Meh, it's the Internet.

From my tech words after coming out the 2nd time. You had a shit installer.

google will bend over backwards to fix it. But you have to let them know.

I've contacted their tech support, but perhaps I should call them back out so they can see it for themselves. Bit most folks are saying the remote lag is happening, so I'm not sure it was my installer, none of us had the same installer (that I know of).

no response or a timeout from traceroute is pretty normal from tier 1 ISP's. Most block ICMP echo now with exception for a few routers that do allow it for troubleshooting. traceroute doesn't give the return path so you would need someone to initiate from the remote side as well to get a full picture of the path.





Is that to Google's on-net Ookla server or a random public one?

Try using this for your testing to see what results you get.

http://www.ispgeeks.com/wild/modules...e=CapacityTest

I use the SolarWinds Engineer's toolkit and also Multiping.

GF is aware of the issue, some other peeps in the neighborhood are seeing the same things (loaded Multiping), and GF is working the issue.

It's all good, I just had to convince them that we're not nuts.