AX50 - Weird response time

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

AX50 - Weird response time

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
AX50 - Weird response time
AX50 - Weird response time
2020-12-18 05:54:41
Model: Archer AX50  
Hardware Version: V1
Firmware Version: 1.0.9 Build 20200708 rel.55037(5553)

Hi TP Link, 

 

I've just got my new AX50 but i've been having this spike in response time in 5GHZ band.

Take note, the test is just the ping test from my laptop to my router. Is this normal?? This happens from time to time. 

 

 

12/18/2020 1:33:13 PM - Pinging 192.168.0.1 with 32 bytes of data:
12/18/2020 1:33:13 PM - Reply from 192.168.0.1: bytes=32 time=27ms TTL=64
12/18/2020 1:33:14 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:15 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:16 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:17 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:18 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:19 PM - Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
12/18/2020 1:33:20 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:21 PM - Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
12/18/2020 1:33:22 PM - Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
12/18/2020 1:33:23 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:24 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:25 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:26 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:27 PM - Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
12/18/2020 1:33:28 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:29 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:30 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:31 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:32 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:33 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:34 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:35 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:36 PM - Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
12/18/2020 1:33:37 PM - Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
12/18/2020 1:33:38 PM - Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
12/18/2020 1:33:39 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:40 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:41 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:42 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:43 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:44 PM - Reply from 192.168.0.1: bytes=32 time=205ms TTL=64
12/18/2020 1:33:45 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:46 PM - Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
12/18/2020 1:33:47 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:48 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:49 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:50 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:51 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:52 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:53 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:54 PM - Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
12/18/2020 1:33:55 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:33:56 PM - Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
12/18/2020 1:33:57 PM - Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
12/18/2020 1:33:58 PM - Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
12/18/2020 1:33:59 PM - Reply from 192.168.0.1: bytes=32 time=70ms TTL=64
12/18/2020 1:34:00 PM - Reply from 192.168.0.1: bytes=32 time=100ms TTL=64
12/18/2020 1:34:01 PM - Reply from 192.168.0.1: bytes=32 time=104ms TTL=64
12/18/2020 1:34:02 PM - Reply from 192.168.0.1: bytes=32 time=93ms TTL=64
12/18/2020 1:34:03 PM - Reply from 192.168.0.1: bytes=32 time=30ms TTL=64
12/18/2020 1:34:04 PM - Reply from 192.168.0.1: bytes=32 time=39ms TTL=64
12/18/2020 1:34:05 PM - Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
12/18/2020 1:34:06 PM - Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
12/18/2020 1:34:07 PM - Reply from 192.168.0.1: bytes=32 time=114ms TTL=64
12/18/2020 1:34:08 PM - Reply from 192.168.0.1: bytes=32 time=12ms TTL=64

 

Thank you!

Kevin

  0      
  0      
#1
Options
1 Reply
Re:AX50 - Weird response time
2020-12-18 22:14:30 - last edited 2020-12-18 22:14:42

@AX50-user 

 

Looks like you are getting some spikes. If you have other computers try constant ping tests to make sure it is coming from the router. You could also connect only one device and slowly add more to see is the delay is from a computer hogging the bandwidth.

  0  
  0  
#2
Options

Information

Helpful: 0

Views: 414

Replies: 1

Related Articles