When connection drops, how about Powerline lights on those adapters?
Upgrade the latest firmware.

I'm getting this problem too.

I have posted a very thorough bug report, still waiting for it to appear in the forum posts though....

Hello.

When the connection drops, the lights don't seem to change. I have the top 3 lights green and the lowest one flashing green (like it always does).

And i though that was the latest firmware.

W

had the same problem for ages, still waiting for a firmware upgrade

I'm having exactly the same problem. I'm using the latest firmware.

I ran an ongoing ping to google.com and the results are as follows:

64 bytes from 64.233.167.103: icmp_seq=0 ttl=44 time=1192.162 ms
64 bytes from 64.233.167.103: icmp_seq=1 ttl=44 time=187.074 ms
64 bytes from 64.233.167.103: icmp_seq=2 ttl=44 time=375.349 ms
64 bytes from 64.233.167.103: icmp_seq=3 ttl=44 time=59.845 ms
64 bytes from 64.233.167.103: icmp_seq=4 ttl=44 time=29.717 ms
64 bytes from 64.233.167.103: icmp_seq=5 ttl=44 time=102.080 ms
64 bytes from 64.233.167.103: icmp_seq=6 ttl=44 time=204.333 ms
64 bytes from 64.233.167.103: icmp_seq=7 ttl=44 time=101.737 ms
.
.
.
64 bytes from 64.233.167.103: icmp_seq=698 ttl=44 time=29.192 ms
64 bytes from 64.233.167.103: icmp_seq=699 ttl=44 time=30.532 ms
64 bytes from 64.233.167.103: icmp_seq=700 ttl=44 time=31.566 ms
Request timeout for icmp_seq 702
Request timeout for icmp_seq 703
Request timeout for icmp_seq 704
Request timeout for icmp_seq 705
Request timeout for icmp_seq 706
Request timeout for icmp_seq 707
Request timeout for icmp_seq 708
Request timeout for icmp_seq 709
Request timeout for icmp_seq 710
Request timeout for icmp_seq 711
Request timeout for icmp_seq 712
Request timeout for icmp_seq 713
Request timeout for icmp_seq 714
Request timeout for icmp_seq 715
64 bytes from 64.233.167.103: icmp_seq=716 ttl=44 time=58.123 ms
64 bytes from 64.233.167.103: icmp_seq=717 ttl=44 time=28.847 ms
64 bytes from 64.233.167.103: icmp_seq=718 ttl=44 time=32.777 ms
.
.
.
64 bytes from 64.233.167.103: icmp_seq=1603 ttl=47 time=28.941 ms
64 bytes from 64.233.167.103: icmp_seq=1604 ttl=47 time=37.622 ms
64 bytes from 64.233.167.103: icmp_seq=1605 ttl=47 time=28.097 ms
Request timeout for icmp_seq 1606
Request timeout for icmp_seq 1607
Request timeout for icmp_seq 1608
Request timeout for icmp_seq 1609
Request timeout for icmp_seq 1610
Request timeout for icmp_seq 1611
Request timeout for icmp_seq 1612
Request timeout for icmp_seq 1613
Request timeout for icmp_seq 1614
Request timeout for icmp_seq 1615
Request timeout for icmp_seq 1616
Request timeout for icmp_seq 1617
Request timeout for icmp_seq 1618
Request timeout for icmp_seq 1619
Request timeout for icmp_seq 1620
Request timeout for icmp_seq 1621
64 bytes from 64.233.167.103: icmp_seq=1622 ttl=47 time=57.876 ms
64 bytes from 64.233.167.103: icmp_seq=1623 ttl=47 time=27.773 ms
64 bytes from 64.233.167.103: icmp_seq=1624 ttl=47 time=28.209 ms
.
.
.
64 bytes from 64.233.167.103: icmp_seq=2504 ttl=47 time=25.767 ms
64 bytes from 64.233.167.103: icmp_seq=2505 ttl=47 time=27.357 ms
64 bytes from 64.233.167.103: icmp_seq=2506 ttl=47 time=28.285 ms
Request timeout for icmp_seq 2507
Request timeout for icmp_seq 2508
Request timeout for icmp_seq 2509
Request timeout for icmp_seq 2510
Request timeout for icmp_seq 2511
Request timeout for icmp_seq 2512
Request timeout for icmp_seq 2513
Request timeout for icmp_seq 2514
Request timeout for icmp_seq 2515
Request timeout for icmp_seq 2516
Request timeout for icmp_seq 2517
Request timeout for icmp_seq 2518
Request timeout for icmp_seq 2519
Request timeout for icmp_seq 2520
Request timeout for icmp_seq 2521
64 bytes from 64.233.167.103: icmp_seq=2522 ttl=47 time=44.622 ms
64 bytes from 64.233.167.103: icmp_seq=2523 ttl=47 time=26.296 ms
64 bytes from 64.233.167.103: icmp_seq=2524 ttl=47 time=31.435 ms

--- www.google.com ping statistics ---
2525 packets transmitted, 2479 packets received, 1.8% packet loss
round-trip min/avg/max/stddev = 25.735/34.405/1192.162/34.157 ms


In other words, approximately every 700 packets, around 14-16 packets get dropped.

I'm not yet sure if it's the wireless connection or the power line aspect that cause the packets to get dropped.

There seems to be a firmware update as of the 4th Jan 2014 (tomorrow oddly)

http://www.tp-link.com/en/support/download/?model=TL-WPA4220KIT&version=V1

And direct to file:
http://www.tp-link.com/resources/software/TL-WPA4220_V1_140401_EU.zip

So i've just updated firmware and reset system. Lets see what happens.

W

uhhh, 14 January 2014 was last year. This is 2015.

And I suspect that "4/1/2014" is an American format date, which would be 1 April 2014.

Duh - of course.

All good so far with the new firmware:

Traceroute has started…

traceroute: Warning: google.com has multiple addresses; using 74.125.230.227
traceroute to google.com (74.125.230.227), 64 hops max, 72 byte packets
1 routerlogin.net (192.168.0.1) 4.440 ms 3.712 ms 3.832 ms
2 XX.XX.XX.XX (XX.XX.XX.XX) 14.007 ms 10.978 ms 10.245 ms
3 popl-core-2b-ae10-1240.network.virginmedia.net (XX.XX.XX.XX) 15.047 ms 12.228 ms 13.059 ms
4 * * *
5 brnt-bb-1a-ae0-0.network.virginmedia.net (XX.XX.XX.XX) 18.770 ms 12.982 ms 22.849 ms
6 tclo-ic-2-ae0-0.network.virginmedia.net (212.250.14.202) 15.957 ms 16.019 ms 14.000 ms
7 72.14.198.97 (72.14.198.97) 24.630 ms 35.779 ms 26.836 ms
8 209.85.255.78 (209.85.255.78) 30.145 ms 21.520 ms 22.871 ms
9 209.85.250.169 (209.85.250.169) 22.479 ms 24.141 ms 25.904 ms
10 lhr08s06-in-f3.1e100.net (74.125.230.227) 19.745 ms 21.680 ms 23.901 ms

I'm getting the same problem here. The wireless was always iffy and tended to drop out and reset itself, so I gave up and wired it. Recently however, I'm starting to get issues with that too. If I leave it alone, it will usually come back in a couple of minutes. Otherwise, unplugging it for a few seconds and then plugging it back in will fix it. Unfortunately this is a pain in the butt when trying to watch Netflix. Any word at all from TP-Link on this? A fix in the works? Even acknowledgement that it's an issue? Maybe a response from someone to let us know they're still alive and haven't been eaten by the walking dead? I thought I'd check to see if there's a new firmware, but that part of the site seems to be down right now. Even this reply page loaded very slowly and painfully.

Did you try to reset them to factory defaults and repair them?
To contact TP-LINK support directly, you can submit a ticket here.
http://ticket.tp-link.com/index.php?/Tickets/Submit