@Cramezul 

This is what i don't really understand either - my C6 Archer worked perfectly well for a year before I started to experience some problems,and even then it took a while to become so much of a problem that I had to do some serious investiagtion.  I wonder if the problem wasn'tintroduced with the January F/W upgrade, but it feels more hardware than software given the problem got worse over time before becoming untenable.

I must admit that my solution has been to purchase a 2.4Ghz WAP and turn off the 2.4Ghz band on the router itself (had to do this as my printer doesn't operate on the 5GHz band, otherwise I would have just made do with the 5GHz band).

In a perverse way I am pleased to hear that it is not just me experiencing the problem as I had begun to distrust myself.

I have been a bit disappointed wit hthe TP-Link support on the matter as they are in denial.

The same situation here. Is this normal behaviour - 2G, Archer C6 EU?

C:\Users\famgr>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 5ms, Average = 2ms

C:\Users\famgr>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3070ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 3070ms, Average = 769ms

C:\Users\?

I have the Archer c6 version (US) and (EU) however the version (EU) presents many problems, with each firmware update presents a new bug, in the version Archer C6(EU)_V2_200110 the wi-fi network 2.4Ghz presents instability and falls, plus the 5Ghz network works correctly, now in the Version Archer C6(EU)_V2_200402 the 2.4ghz network has become more unstable, but the 5Ghz network is in trouble giving packet loss , the (US) version so far has not experienced problems in the latest firmware version.

same problem here with lastest firmware. Hope TPlink fix it soon. 

@StuartP 

I also have the same problem here.

5G works fine but 2.4G keeps crashing out of the blue. The 2.4G SSID is still being announced but no device can connect to it after the drop

HW Version: Archer C6 v2.0

FW Version: 1.1.5 Build 20191112 rel.36515(5553)

Does wired connection or 5GHz work properly when the 2.4GHz stopped working?

@Template Yes, and I'm not the only one reporting this problem, so it seems to be a general problem with TP-Link firmware

@PedroYan Hi friend, the TP-Link Archer C6 v2 (EN) in version 1.2.1 presents this problem, already in version 1.3.0 the network 2.4ghz and normalized, plus the 5ghz network presents packet loss problems, the TP-Link Archer C6 v2 (US) in version 1.1.15 works perfectly well, the problem and that the hardware version of the two models are different, and would not have how to use a firmware (US) on an equipment (EN) , I think the version (EN) has limitations by different hardware and does not support working correctly as the summer (US) or may be firmware problem even, the way and waits for the company to solve the problem with a firmware more unstable.

@Lucasm TP link please solve this problem. 2.4 ghz connection having issue and disconnecting the devices connected to it. And in mobile devices it says internet access denied. All Users archer series having the same problems and you guys did nothing to solve it. Solve it in your next firmware update pls. Im using the latest firmware still facing this stupid issue. 1.3.0 Build 20200402 rel.52000

i regretting buying this product from tplink. Better go to asus

@DWR65 

It's not hardware related, I started this post and since installing openwrt firmware on it the issue dissapears and the operation is trouble free.