Hello, can i ask for help about the problem with my tp link router? I recently bought a Tp link Archer c80 ac1900 and im experiencing unstable and a huge packet loss on this router, i tried to see if the wan port of the router is faulty by changing the mode to ap mode, so far there are no packet loss. I tried connecting my old router which is the TL wr840n, there is no packet loss and the connection is very stable with the default gateway. What i am experiencing is the unstable connection between my router and the default gateway. PPPoe is our internet 

 

 

here is a ping i conducted through the diagnostics page of the tp link webpage:

 

Pinging 172.16.0.1 with 64 bytes of data:

 

Request timed out (seq=0).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=1).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=2).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=3).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=4).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=5).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=6).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=7).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=8).

 

Request timed out (seq=9).

 

Request timed out (seq=10).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=11).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=12).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=13).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=14).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=15).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=16).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=17).

 

Request timed out (seq=18).

 

Request timed out (seq=19).

 

Request timed out (seq=20).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=21).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=22).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=23).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=24).

 

Request timed out (seq=25).

 

Request timed out (seq=26).

 

Request timed out (seq=27).

 

Request timed out (seq=28).

 

Request timed out (seq=29).

 

Request timed out (seq=30).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=31).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=32).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=33).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=34).

 

Reply from 172.16.0.1: bytes=64 time=16ms TTL=64 (seq=35).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=36).

 

Request timed out (seq=37).

 

Request timed out (seq=38).

 

Request timed out (seq=39).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=40).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=41).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=42).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=43).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=44).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=45).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=46).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=47).

 

Reply from 172.16.0.1: bytes=64 time=16ms TTL=64 (seq=48).

 

Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=49).

 

Ping statistics for 172.16.0.1:

 

Packets: Sent = 50, Received = 35, Lost = 15 (30% loss).

 

Approximate round trip times in milli-seconds:

 

Minimum = 1ms, Maximum = 16ms, Average = 0ms