NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

cda023's avatar
cda023
Tutor
Jan 19, 2022
Solved

MR60/MS60 speedtest not working on latest firmware V1.1.6.122_2.0.58

Speedtest through both the Nighthawk App and Web UI do not work.  the App registers 0.00 and the webUI says "The Speedtest failed to detect the bandwidth, please check your Internet connection or try...
  • tduke's avatar
    tduke
    Feb 14, 2022

    Well, Speedtest randomly started working again on it's own.  The firmware version is the same and no other changes were made, so I guess there must have been something on the service side, though short of an API change, I can't imagine what.  In any case, the issue is resolved.

    FURRYe38 wrote:

    Well if its only the speed test app on the MR thats not working and other systems work, you night avoid using the built in speed test app for now and just client side speed tests for now. Unless you wnat to revert back to something prior. Thats up to you. If the system is working other wise then leave it and wait for NG to fix all this. They need too look into this. Nothing else we can do here. No idea when a fix will be coming so don't ask. Just keep looking at NG download page or here in the forums once in a while to check. I try to post new FW notices when NG releases them.

    tduke wrote:

     

     

    Considering that the issue first appeared on the .116 version, but only since December, how far back do you suggest I go?  Further, as far as I can tell, the issue was not apparent when I first upgraded to the .116 version, but only appeared in the last month or so, can we even be sure it's the result of a firmware change and not the result of some change, like dropping a deprecated API call, that Speedtest made recently that wasn't applied to this firmware?

     



FURRYe38's avatar
FURRYe38
Guru - Experienced User
Jan 27, 2022

Well if its only the speed test app on the MR thats not working and other systems work, you night avoid using the built in speed test app for now and just client side speed tests for now. Unless you wnat to revert back to something prior. Thats up to you. If the system is working other wise then leave it and wait for NG to fix all this. They need too look into this. Nothing else we can do here. No idea when a fix will be coming so don't ask. Just keep looking at NG download page or here in the forums once in a while to check. I try to post new FW notices when NG releases them.

tduke wrote:

 

 

Considering that the issue first appeared on the .116 version, but only since December, how far back do you suggest I go?  Further, as far as I can tell, the issue was not apparent when I first upgraded to the .116 version, but only appeared in the last month or so, can we even be sure it's the result of a firmware change and not the result of some change, like dropping a deprecated API call, that Speedtest made recently that wasn't applied to this firmware?

 

tduke's avatar
tduke
Aspirant
Feb 14, 2022

Well, Speedtest randomly started working again on it's own.  The firmware version is the same and no other changes were made, so I guess there must have been something on the service side, though short of an API change, I can't imagine what.  In any case, the issue is resolved.

FURRYe38 wrote:

Well if its only the speed test app on the MR thats not working and other systems work, you night avoid using the built in speed test app for now and just client side speed tests for now. Unless you wnat to revert back to something prior. Thats up to you. If the system is working other wise then leave it and wait for NG to fix all this. They need too look into this. Nothing else we can do here. No idea when a fix will be coming so don't ask. Just keep looking at NG download page or here in the forums once in a while to check. I try to post new FW notices when NG releases them.

tduke wrote:

 

 

Considering that the issue first appeared on the .116 version, but only since December, how far back do you suggest I go?  Further, as far as I can tell, the issue was not apparent when I first upgraded to the .116 version, but only appeared in the last month or so, can we even be sure it's the result of a firmware change and not the result of some change, like dropping a deprecated API call, that Speedtest made recently that wasn't applied to this firmware?