#Router throttling how to#

This is absolutely ridiculous that Google can't figure this out, or they have and can't fix via firmware ( and they don't want to replace millions and millions of units). I rebooted the Google Wifi AP this morning and retested my wireless connect from my phone, sitting in the same spot (I went from 42up/35down to 453up/461down). However any device connected wirelessly to the Google Wifi AP, get the drop down to ~90Mbs up/down. The good news is that any device connected through a WIRE going to the Linksys Router gets the expected ~900Mbs up/down.

I can tell you that it is the device itself, no matter whether acting as a ROUTER or Acting as a simple AP, the same thing happens. Thinking this was an issue of the router functionality. I then took one of my mesh Google Wifi devices and reset it and am using it now as an AP (put in Bridge Mode). Based upon all the discussion, I removed the Google Wifi as my ROUTER and replaced it with a Linksys EA9300 that I had been using as a basic AP (Bridge Mode). Its possible to change this, but may also require changing settings in your router if you use one.

#Router throttling how to#

I wanted to post another update - have no idea if it will help or confuse the matter. throttling Find out how to tell and what to do about it. Looks like there are a TON of merged threads that got thrown into it too: I did some more research, and now I'm thinking the below thread shares common issues as myself. Ran them for a week each without any throttling. My other two routers do not have this issue at all. This issue happens only with the Google WiFi router, both wired and wireless, anda network restart consistently fixes it, albeit temporarily. Network analytics, PRTG, WireShark show no anomalies in my network, or any weird traffic or dropped packets. Also worth noting that I'm an IT Senior Systems and Network Admin by trade, with a close eye on my home network. This is absolutely ridiculous that Google can't figure this out, or they have and can't fix via firmware ( and they don't want to replace millions and millions of units).It's worth noting that this just started happening maybe in the last 1-2 months. I can tell you that it is the device itself, no matter whether acting as a ROUTER or Acting as a simple AP, the same thing happens. If you’re familiar with React class lifecycle methods, you can think of useEffect Hook as componentDidMount, componentDidUpdate, and componentWillUnmount combined. I wanted to post another update - have no idea if it will help or confuse the matter.

The only thing these speed tests have in common is the first 4. If there were a non-AT&T router shaping the traffic, you would expect the speeds to vary. Network analytics, PRTG, WireShark show no anomalies in my network, or any weird traffic or dropped packets. Traffic Shaping - meaning some traffic is deliberately throttled by AT&Ts routers to reserve bandwidth for other things.

It's worth noting that this just started happening maybe in the last 1-2 months.