High ping, lot of packet loss, loss of DNS entries
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Has there any fixes known for the problem?
It has been previously reported here: https://community.tp-link.com/en/home/forum/topic/198550
The problems varies randomly. I have multiple devices connected, all wireless.
The network location is fully clean from any other Wi-Fi RF emissions (2 km to nearest buildings), so it is sole Wi-Fi in the area.
All devices experience serious high ping's suddenly. It can be something example:
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1471ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2028ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2390ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3298ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2504ms TTL=64
Reply from 10.0.0.1: bytes=32 time=924ms TTL=64
Reply from 10.0.0.1: bytes=32 time=907ms TTL=64
Reply from 10.0.0.1: bytes=32 time=99ms TTL=64
Reply from 10.0.0.1: bytes=32 time=602ms TTL=64
Reply from 10.0.0.1: bytes=32 time=714ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1714ms TTL=64
Reply from 10.0.0.1: bytes=32 time=672ms TTL=64
Reply from 10.0.0.1: bytes=32 time=39ms TTL=64
Reply from 10.0.0.1: bytes=32 time=112ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=12ms TTL=64
Reply from 10.0.0.1: bytes=32 time=987ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.0.1: bytes=32 time=696ms TTL=64
Reply from 10.0.0.1: bytes=32 time=436ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2090ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1687ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1887ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1411ms TTL=64
Reply from 10.0.0.1: bytes=32 time=615ms TTL=64
Reply from 10.0.0.1: bytes=32 time=721ms TTL=64
Reply from 10.0.0.1: bytes=32 time=544ms TTL=64
Reply from 10.0.0.1: bytes=32 time=778ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1067ms TTL=64
Reply from 10.0.0.1: bytes=32 time=649ms TTL=64
Reply from 10.0.0.1: bytes=32 time=385ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1970ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1977ms TTL=64
Reply from 10.0.0.1: bytes=32 time=250ms TTL=64
Reply from 10.0.0.1: bytes=32 time=931ms TTL=64
Reply from 10.0.0.1: bytes=32 time=223ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1253ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1833ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1048ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1518ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1782ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1139ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1710ms TTL=64
Reply from 10.0.0.1: bytes=32 time=792ms TTL=64
Reply from 10.0.0.1: bytes=32 time=18ms TTL=64
Reply from 10.0.0.1: bytes=32 time=153ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2365ms TTL=64
Reply from 10.0.0.1: bytes=32 time=419ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=20ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=84ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
And then at the best it can be something like this from Windows PC's:
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=6ms TTL=64
Reply from 10.0.0.1: bytes=32 time=19ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=5ms TTL=64
Reply from 10.0.0.1: bytes=32 time=4ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=21ms TTL=64
Reply from 10.0.0.1: bytes=32 time=4ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=5ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
That spike in the latency will cause serious problems in the PC online games, as it will trigger severe packet loss and as well cause massive 300-500 ms peaks that you experience as freezes. Even when it doesn't look bad in the ping on those moments.
The web browsing is almost impossible as so much is dropped or delayed, that synced connections doesn't work.
And as well streaming video to TV from internet is not possible as it just triggers severe frame drops and buffering every few seconds.
This happens with single computer, or multiple computers.
Not tested with wire (as it is anyways impossible).
Re-Connect or reseting NIC etc doesn't help than few seconds.
And then suddenly everything can be just right (except those few ms looking spikes).
And when it goes bad, it is very bad.
Factory reset etc doesn't help.
