Home Network Community > Deco > Ping Spiking
< Deco

Ping Spiking

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Ping Spiking

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Ping Spiking
Ping Spiking
2020-06-03 23:22:56
Model: Deco M4  
Hardware Version: V2
Firmware Version: 1.1.0

Can someone help me pinpoint why my ping keeps randomly spiking and dropping, as far as i can tell there is only 2 devices in use. My PC and a amazon firestick. Speedtest shows 50/75. This is a wireless connection pinging the deco m4.

 

Pinging 192.168.68.1 with 500 bytes of data:
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=1ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=1ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=5ms TTL=64
Reply from 192.168.68.1: bytes=500 time=5ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=6ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=12ms TTL=64
Reply from 192.168.68.1: bytes=500 time=7ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=8ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=20ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=69ms TTL=64
Reply from 192.168.68.1: bytes=500 time=7ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=1ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=18ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=1ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=1ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=199ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=2ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=5ms TTL=64
Reply from 192.168.68.1: bytes=500 time=105ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=105ms TTL=64
Reply from 192.168.68.1: bytes=500 time=4ms TTL=64
Reply from 192.168.68.1: bytes=500 time=52ms TTL=64
Reply from 192.168.68.1: bytes=500 time=56ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64
Reply from 192.168.68.1: bytes=500 time=3ms TTL=64

Ping statistics for 192.168.68.1:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 199ms, Average = 9ms

  1      
 
  1      
 
#1
Options
5 Reply
Re:Ping Spiking
2020-06-04 15:26:47

@yoshi9540 

 

Are you seeing any issues as a result of this? If so, what have you tried so far?

  0  
  0  
#2
Options
Re:Ping Spiking
2020-06-04 15:29:48

@Tony 

I spoke with live tech support yesterday, they had me clean the QoS on the deco app and it seems to be running much better now. Still having some spikes here and there but it is manageable now. 

  0  
  0  
#3
Options
Re:Ping Spiking
2021-05-10 20:40:54

@yoshi9540 Did you find a solution to this?

  0  
  0  
#4
Options
Re:Ping Spiking
2021-05-10 20:43:09
It was mentioned above. Support had me ear QoS. I will probably be swapping mesh routers though
  0  
  0  
#5
Options
Re:Ping Spiking
2021-05-10 20:49:55

@yoshi9540 Yeah, I am very dissappointed in my deco X20. My old netgear router used to give a constant 1ms ping in the same location, the deco doesnt go under 5, and spikes quite irraticly. I do not even have any QoS set up, it is still as it came out of the box.

  0  
  0  
#6
Options

Information

Helpful: 1

Views: 730

Replies: 5

Related Articles
Allow ping from WAN port?
11067 1
Archer T3U AC1300 Plus Spiking Connection
296 0
Enable ICMP (ECHO) PING on WAN
20846 2
Unable to Ping from a Downlink ROuter
965 0
DNS Unresponsive to Browsers, ping only partially responsive
278 0
Regular ping spikes
250 0
About Us
Press
Copyright © TP-Link USA Corporation. All rights reserved.