UAE 1.1.1.1 very poor ping


#1

I am on Etisalat network located in Ajman (50-60km from Dubai) when I ping 1.1.1.1 and 1.0.0.1 I get a poor ping response of 150-250ms while when I ping google dns I get 8-15ms.


#2

Try a traceroute to those servers and post the results here.


#3

Traceroute for 1.1.1.1

traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 72 byte packets
1 www.routerlogin .com (192.168.1.1) 1.473 ms 0.776 ms 1.231 ms
2 86.99.β€”.3 (86.99.β€”.3) 7.796 ms 16.479 ms 6.114 ms
3 10.246.251.61 (10.246.251.61) 7.932 ms 4.786 ms 4.214 ms
4 195.229.4.74 (195.229.4.74) 8.148 ms 12.846 ms 7.885 ms
5 195.229.0.147 (195.229.0.147) 191.268 ms 190.260 ms 192.178 ms
6 206.126.237.30 (206.126.237.30) 197.635 ms 197.600 ms 203.320 ms
7 1dot1dot1dot1 .cloudflare-dns.com (1.1.1.1) 195.706 ms 198.424 ms 211.223 ms

Traceroute to 1.0.0.1

traceroute to 1.0.0.1 (1.0.0.1), 64 hops max, 72 byte packets
1 www.routerlogin .com (192.168.1.1) 1.175 ms 0.816 ms 0.738 ms
2 86.99.β€”-.3 (86.99.β€”-.3) 3.984 ms 5.096 ms 1.465 ms
3 10.246.251.61 (10.246.251.61) 8.090 ms 4.679 ms 4.444 ms
4 195.229.4.72 (195.229.4.72) 12.569 ms 8.373 ms 7.623 ms
5 195.229.2.123 (195.229.2.123) 119.835 ms 118.693 ms 119.978 ms
6 ams-ix.as13335 .net (80.249.211.140) 120.303 ms 120.540 ms 119.773 ms
7 1dot1dot1dot1.cloudflare-dns .com (1.0.0.1) 120.474 ms 119.496 ms 120.813 ms

Traceroute for 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 72 byte packets
1 www.routerlogin .com (192.168.1.1) 1.002 ms 0.705 ms 0.678 ms
2 86.99.β€”-.3 (86.99.β€”-.3) 9.345 ms 3.739 ms 1.932 ms
3 10.246.251.62 (10.246.251.62) 3.847 ms 3.532 ms 4.229 ms
4 195.229.4.78 (195.229.4.78) 7.593 ms 7.357 ms 7.763 ms
5 195.229.4.51 (195.229.4.51) 6.343 ms 4.933 ms 6.089 ms
6 108.170.247.17 (108.170.247.17) 5.027 ms 5.714 ms 6.727 ms
7 216.239.62.187 (216.239.62.187) 5.254 ms 5.290 ms 5.797 ms
8 google-public-dns-a.google .com (8.8.8.8) 5.664 ms 5.077 ms 6.099 ms


#4

I can see your ip address.


#5

we will check with Etisalat. thank you for letting us know


#6

Thank you


#7

Same issue here on Du.

traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
1 * * *
2 10.100.137.77 (10.100.137.77) 5.055 ms 4.363 ms 7.612 ms
3 10.100.137.86 (10.100.137.86) 8.673 ms 6.083 ms 7.673 ms
4 10.44.152.173 (10.44.152.173) 8.678 ms
10.44.152.93 (10.44.152.93) 8.217 ms
10.44.152.173 (10.44.152.173) 7.804 ms
5 cloudflare.v4.peers.djix.dj (196.223.38.207) 377.882 ms 307.068 ms 307.631 ms
6 1dot1dot1dot1.cloudflare-dns.com (1.1.1.1) 307.684 ms 384.136 ms 306.732 ms

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 * * *
2 10.100.136.77 (10.100.136.77) 8.193 ms 4.788 ms 7.983 ms
3 10.100.136.86 (10.100.136.86) 11.400 ms 7.654 ms 8.001 ms
4 10.229.200.129 (10.229.200.129) 10.823 ms 8.989 ms
10.229.200.121 (10.229.200.121) 17.479 ms
5 72.14.216.152 (72.14.216.152) 11.372 ms 6.307 ms 8.505 ms
6 108.170.247.1 (108.170.247.1) 12.053 ms 11.278 ms 8.749 ms
7 216.239.63.85 (216.239.63.85) 10.379 ms
216.239.62.187 (216.239.62.187) 11.948 ms
216.239.63.85 (216.239.63.85) 12.068 ms
8 * google-public-dns-a.google.com (8.8.8.8) 5.775 ms 7.348 ms


#8

@sabbour Can you share your IP?
You can drop a mail to [email protected] if you don’t want to post your IP address publicly.


#9

Sent privately


#10

@sharbeen For Etisalat, it should be fixed now


#11

Thanks. Just noticed ipv6 ping is still poor.

traceroute to 2606:4700:4700::1111 (2606:4700:4700::1111), 30 hops max, 80 byte packets
1 2001:2e8:665:0:2:2:0:1 (2001:2e8:665:0:2:2:0:1) 0.082 ms 0.096 ms 0.047 ms
2 2001:2e8:22:204::2 (2001:2e8:22:204::2) 0.971 ms 1.071 ms 0.847 ms
3 2001:2e8:20::22:11 (2001:2e8:20::22:11) 0.907 ms 48.699 ms 0.988 ms
4 xe-0-0-12-2.a02.tokyjp05.jp.bb.gin.ntt.net (2001:218:2000:5000::61) 1.105 ms 1.333 ms 1.213 ms
5 ae-25.r02.tokyjp05.jp.bb.gin.ntt.net (2001:218:0:2000::59) 1.248 ms ae-4.r03.tokyjp05.jp.bb.gin.ntt.net (2001:218:0:2000::95) 1.275 ms 1.258 ms
6 ae-2.a00.tokyjp03.jp.bb.gin.ntt.net (2001:218:0:2000::be) 1.626 ms 2.099 ms ae-1.a00.tokyjp03.jp.bb.gin.ntt.net (2001:218:0:2000::aa) 2.020 ms
7 2001:218:2000:5000::44a (2001:218:2000:5000::44a) 58.402 ms 58.598 ms 58.523 ms
8 2400:cb00:22:1024::6ca2:e31c (2400:cb00:22:1024::6ca2:e31c) 58.736 ms 2400:cb00:22:1024::6ca2:e328 (2400:cb00:22:1024::6ca2:e328) 62.923 ms 2400:cb00:22:1024::6ca2:e346 (2400:cb00:22:1024::6ca2:e346) 58.416 ms


#12

This is Du:

tracert 1.0.0.1

1 1 ms 2 ms 2 ms DeviceDHCP.Home [192.168.1.1]
2 13 ms 10 ms 11 ms xxx
3 12 ms 12 ms 12 ms 10.100.128.13
4 14 ms 12 ms 12 ms 10.100.34.78
5 18 ms 16 ms 16 ms 10.89.91.173
6 94 ms 86 ms 84 ms cloudflare.v4.peers.djix.dj [196.223.38.207]
7 85 ms 85 ms 85 ms 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]


Google DNS

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 5 ms 4 ms 4 ms DeviceDHCP.Home [192.168.1.1]
2 11 ms 10 ms 17 ms xxxx
3 12 ms 12 ms 12 ms 10.100.129.13
4 13 ms 12 ms 13 ms 10.100.35.78
5 19 ms 16 ms 17 ms 10.89.91.177
6 16 ms 15 ms 15 ms 72.14.216.152
7 13 ms 15 ms 14 ms 108.170.247.1
8 14 ms 14 ms 14 ms 216.239.63.85
9 14 ms 16 ms 15 ms google-public-dns-a.google.com [8.8.8.8]

Tracing route to google-public-dns-b.google.com [8.8.4.4]
over a maximum of 30 hops:

1 1 ms 2 ms 3 ms DeviceDHCP.Home [192.168.1.1]
2 10 ms 19 ms 16 ms xxxx
3 12 ms 12 ms 12 ms 10.100.128.13
4 12 ms 13 ms 12 ms 10.100.34.78
5 17 ms 18 ms 14 ms 10.89.91.177
6 15 ms 15 ms 14 ms 72.14.216.152
7 12 ms 14 ms 14 ms 108.170.247.1
8 14 ms 14 ms 13 ms 216.239.63.85
9 14 ms 13 ms 13 ms google-public-dns-b.google.com [8.8.4.4]

CloudFlare DNS is definitely performing not as good as Google DNS.


#13

Any updates?


#14

Still the same with du. My workplace got du connection by due to their network security I’m unable to trace route to write here. Also the ipv6 with Etisalat got very poor ping around 160-250ms, I’ve already sent that but no reply.