Full description not available
S**R
reliably unreliable
Been messing with this for days and no matter what I see consistent network fail:Pinging 172.16.0.73 with 32 bytes of data:Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=7ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=7ms TTL=64Reply from 172.16.0.73: bytes=32 time=3ms TTL=64Reply from 172.16.0.73: bytes=32 time=406ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=15ms TTL=64Reply from 172.16.0.73: bytes=32 time=5ms TTL=64Reply from 172.16.0.73: bytes=32 time=24ms TTL=64Reply from 172.16.0.73: bytes=32 time=6ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=21ms TTL=64Reply from 172.16.0.73: bytes=32 time=20ms TTL=64Reply from 172.16.0.73: bytes=32 time=11ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=3ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=3ms TTL=64Reply from 172.16.0.73: bytes=32 time=17ms TTL=64Reply from 172.16.0.73: bytes=32 time=19ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=13ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=2ms TTL=64Reply from 172.16.0.73: bytes=32 time=10ms TTL=64Reply from 172.16.0.73: bytes=32 time=5ms TTL=64Reply from 172.16.0.73: bytes=32 time=9ms TTL=64Reply from 172.16.0.73: bytes=32 time=9ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=9ms TTL=64Reply from 172.16.0.73: bytes=32 time=12ms TTL=64Reply from 172.16.0.73: bytes=32 time=44ms TTL=64Reply from 172.16.0.73: bytes=32 time=5ms TTL=64Reply from 172.16.0.73: bytes=32 time=7ms TTL=64Request timed out.Request timed out.Request timed out.Request timed out.Request timed out.Reply from 172.16.0.73: bytes=32 time=18ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=35ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=2ms TTL=64Reply from 172.16.0.73: bytes=32 time=150ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=2ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=1103ms TTL=64Reply from 172.16.0.73: bytes=32 time=2468ms TTL=64Reply from 172.16.0.73: bytes=32 time=3ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Request timed out.Request timed out.Reply from 172.16.0.73: bytes=32 time=2ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=10ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=3ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=3ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=9ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=7ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Request timed out.Request timed out.Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=13ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=2ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=9ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=3ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=9ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=1ms TTL=64Reply from 172.16.0.73: bytes=32 time=2ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=9ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time<1ms TTL=64Reply from 172.16.0.73: bytes=32 time=3ms TTL=64Request timed out.Reply from 172.16.0.73: bytes=32 time=10ms TTL=64
D**N
Worked well for 15 months then just quit working.
The media could not be loaded. This device started working GREAT from the moment I set it up. I purchased this device in Sept 2019 and honestly had NO issues what so ever. However, 15 months later I can't make the same statement. The item is reasonably priced, so I can't be too upset, but when you have security devices dependent upon this device to work, THAT is a problem. Prior to the device failing, I would have without a doubt given it 5 stars. Maybe even 4 after it stopped working, had it given any hint that it was failing. To just all of a sudden NOT work hurts, especially when you start to depend on it, as you build out your smart home. So, I guess if I can't pay for a replacement, I'll honestly just purchase another one because the thing did work flawlessly, before dying. The only thing I'll do differently next time, is buy an extended warranty.
P**E
One sorry piece of hardware.
The configuration page is loaded with broken English and typos. They spell "connectsetting" as 1 word. They try to show "help" worded "Password must be does not include ; and , ". (Even when you haven't typed and semicolons or commas.) Its text has childish "smiley faces" emojis. Step #1 says to type an IP address in your browser. (That's even BEFORE you have connected to anything.) The paper manual says it will help you connect to "your handy". (What's a "handy?) The manufacturer recommends the use of easily hackable WPS. Changing settings requires a long/slow reboot of the device EACH TIME. Even when it connects, you don't get Internet access. Needless to say, we are going to try to get our money back.
S**.
Meh, no great improvement and slower speeds noticed
Seems to actually slow or throttle WiFi signal. When I plugged in an Ethernet Cat6 cable and connect to Xbox One X, the NAT type varies during gameplay from open to moderate and the connection speeds vary quite frequently. Connection is actually a bit better just on the original routers WiFi so I’m not sure it’s actually improving or helping signal at all. Tried to download update from cudytech website and get routed to an Asian website requiring a login and password so seems fairly pointless.
R**S
It woks well... but the installation instructions...
The product does what is supposed to. However the Installation guide is very inaccurate and poor. I had to google for the installation. The IP / web address will not be enable via wifi (at least with a Comcast router). I had to connect the provided wan cable from the extender (AC750) to the laptop directly to be able to access the IP / Web address. Only then I was able to configure the extender. Also the configuration steps in the guide are inaccurate as well. You will have to access the advanced tab and enter your wifi information separated for the 2.4 and the 5Ghz. I hope this helps.
F**S
Horrible! Save yourself a headache, don't buy this.
First off, the setup instructions are not up to date. The website which are you directed to in order to set up the device is no longer active, and I had to independently search for an alternative setup method. The wifi extender worked properly once, and only for a short period of a couple hours. After that, it constantly disconnects and has to be unplugged and restarted for it to function properly, but still only temporary. The device is pure garbage and regret buying it. I do not recommend this wifi extender for anyone.
F**G
good
I have my router on first floor, and my house is whole bricks made structure that I can not connect the wifi well most of the time in second floor or back yard. I have this wifi amplifier for a few weeks and it is easy to connect with wifi router. I can receive signal on second floor and in the yard. The signal appears even stronger on the first floor than before. The instruction may seems a little complicated, but follow the steps and you will get it installed correctly. Just press the WPS button for both wifi router and repeater, then plug and place the repeater somewhere needs to extend wifi signal, everything done.
Trustpilot
1 month ago
1 week ago