Home Network Community > All Threads > High ping on Archer C2 AC750
< All Threads

High ping on Archer C2 AC750

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

High ping on Archer C2 AC750

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
High ping on Archer C2 AC750
High ping on Archer C2 AC750
2016-02-16 03:14:46
Model :

Hardware Version : Not Clear

Firmware Version :

ISP :

I just bought the Archer C2 V1 and there is what I think is an unusual high latency. Connected directly with Ethernet, it returns a unstable and high ping:

ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=3.16 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.89 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.54 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=3.95 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=3.00 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=2.60 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.957 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=3.97 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=3.60 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.93 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.887 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.625 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=2.93 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1.97 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.68 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=3.94 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.49 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=2.68 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=0.973 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=4.02 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=3.75 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=1.97 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=0.978 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=1.34 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=2.96 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=1.97 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=1.86 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=0.958 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=3.94 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=1.23 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=2.94 ms
^C
--- 192.168.1.1 ping statistics ---
31 packets transmitted, 31 received, 0% packet loss, time 30028ms
rtt min/avg/max/mdev = 0.625/2.316/4.024/1.089 ms

All settings are untouched, and it is updated to the last firmware;
Firmware Version:0.9.1 3.2 v0032.0 Build 151022 Rel.60429n

Cables or computer are not the problem, I´ve tried the same with a WDR3600 and a Technicolor and both return normal pings;

ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.386 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.340 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.332 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.368 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.357 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.360 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.330 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.316 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.366 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.330 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.362 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.368 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=0.355 ms
^C
--- 192.168.1.1 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 11997ms
rtt min/avg/max/mdev = 0.316/0.351/0.386/0.027 ms





When I do the same with a 25m cable, the ping goes up from 5 to 9ms, so I suppose this is a hardware problem. Should I ask for a RMA, or is this a normal performance for a 50€ router? Anyone with the same problem?

Thank you in advance.
  0      
 
  0      
 
#1
Options
10 Reply
Re:High ping on Archer C2 AC750
2016-02-16 23:50:35
Is your C2 v1.0 or v1.1?
  0  
  0  
#2
Options
Re:High ping on Archer C2 AC750
2016-02-17 20:14:16
I didn´t know there are more than one version. In the status configuration page apprears: "Hardware Version:Archer C2 v1 00000000", so I suppose is v1.0.
  0  
  0  
#3
Options
Re:High ping on Archer C2 AC750
2016-02-17 21:00:47
You can find the version below the router physically. Does it say v1.0 or v1.1?
  0  
  0  
#4
Options
Re:High ping on Archer C2 AC750
2016-02-17 21:27:07
Ok yep, v1.1, sorry for the confusion.
  0  
  0  
#5
Options
Re:High ping on Archer C2 AC750
2016-02-18 04:32:21
Anyone with this model can test if this happens in his router?
  0  
  0  
#6
Options
Re:High ping on Archer C2 AC750
2016-02-18 07:41:29
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=3.855 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.124 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=7.582 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=5.265 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=3.811 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=4.852 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=3.925 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=3.787 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=3.542 ms
Request timeout for icmp_seq 9
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=6.788 ms
Request timeout for icmp_seq 11
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=18.197 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=7.540 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=19.262 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=2.097 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=2.486 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=3.551 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=5.808 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=7.194 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=3.656 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=3.161 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=4.178 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=5.537 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=5.434 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=61.339 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=53.259 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=108.453 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=39.403 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=3.473 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=4.772 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=4.706 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=5.432 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=4.107 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=9.548 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=4.719 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=3.589 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=7.134 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=35.983 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=22.109 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=90.021 ms

I have the same thing on the same router.
  0  
  0  
#7
Options
Re:High ping on Archer C2 AC750
2016-02-18 07:52:15
Wow, those are really messy pings. Are you connected directly to the router via Ethernet?
  0  
  0  
#8
Options
Re:High ping on Archer C2 AC750
2016-02-18 15:22:38
Hi, sorry that was 5 Ghz wifi.....

Ping has started…


PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=1.439 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.834 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.556 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.527 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=3.018 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.907 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=1.249 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=1.214 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.723 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=4.505 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=2.324 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=0.839 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=3.321 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=2.218 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=1.145 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=1.771 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=1.293 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=2.373 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=2.106 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=2.604 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=0.867 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=1.154 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=1.204 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=0.883 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=3.936 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=1.309 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=0.682 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=2.173 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=4.427 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=1.828 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=4.392 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=1.545 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=1.141 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=0.503 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=1.318 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=1.499 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=1.739 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=0.654 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=1.411 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=2.472 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=2.070 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=0.646 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=2.754 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=0.738 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=1.353 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=1.336 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=0.566 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=3.665 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=1.640 ms
64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=3.634 ms


--- 192.168.0.1 ping statistics ---
50 packets transmitted, 50 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.503/1.830/4.505/1.077 ms

Here is Ethernet only from a few minutes ago
  0  
  0  
#9
Options
Re:High ping on Archer C2 AC750
2016-02-18 15:23:56
Probably still a bit messy wouldn't you say?
  0  
  0  
#10
Options
Re:High ping on Archer C2 AC750
2016-02-26 19:09:05
Yep, already returned it to amazon, really disappointed with this product.
  0  
  0  
#11
Options

Information

Helpful: 0

Views: 1670

Replies: 10

Related Articles
Archer C2 too high ping
1824 0
Archer c2 Ac750
756 0
High Ping
1234 0
Archer c2 ac750 Broken
1078 0
No connection on Archer C2 (AC750)
585 0
Archer C2 AC750 disconnecting
1089 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.