- Location
- Never Far From Nowhere
I'm not familiar with Quantum or Comcast these days (I kicked them to the curb three years ago). With Google, their app is only telling you what it sees on its modem. I suppose if you have a Google Mesh network, then it may tell you more, but if you've got Google fiber and the only Google networking device you have is that modem, all its going to report back on is the status of that device. So its path is: Modem>Test ServerI get this with my Quantum fiber connection. Their app will tell me I've got blazing speed but when I go to Ookla or whatever it's always lower. Comcast did this too. I've always assumed that the app is telling me the speed from the Quantum server (or switch or whatever it's called in that world) to my device, but the Ookla test is telling me the speed between the outside world and my device, THROUGH the Quantum server. Now I'm telco, not an internet or networking guy, but I've always assumed that that's telling me that the bottleneck is on the other side, between the provider's server and the outside world. Do I have that wrong?
Ookla, or SpeedTest, or whatever, is going to be testing from the device its being called up on to the destination server. So it goes PC>Router>Modem>Test Server. In this case, you've added two steps and two points for potential latency. Make sense?
Yeah, you're pretty much always going to get a slower connection over WiFi (depending on what kind), so that seems normal to me.I know nothing. My PC, wired to my modem, just got 945mbps down and 945mbps up with Ookla. My phone, over WiFi, just got 724mbps down and 405mbps up with Ookla. Google fiber and their modem/wifi.
- DAA