Ping to Google DNS is very high!

10,261 views
Skip to first unread message

gіаиg

unread,
Jan 12, 2010, 9:18:42 AM1/12/10
to public-dns-discuss
Hi,

Ping to Google DNS (8.8.8.8) was very good, around 6xms. But, now,
it's not good anymore, around 32xms, what's wrong with Google DNS?

Country: VietNam
OS: Windows 7

Wilmer van der Gaast

unread,
Jan 12, 2010, 9:20:04 AM1/12/10
to public-dn...@googlegroups.com
Hello,

2010/1/12 gіаиg <dask...@gmail.com>:


>
> Ping to Google DNS (8.8.8.8) was very good, around 6xms. But, now,
> it's not good anymore, around 32xms, what's wrong with Google DNS?
>

That's very high indeed. Can you show the output of "tracert 8.8.8.8"?


Cheers,

--
Wilmer van der Gaast, Dublin Traffic SRE.
Google Ireland.

hEADcRASH

unread,
Jan 14, 2010, 5:41:48 PM1/14/10
to public-dns-discuss
Here's what I'm seeing from a few different (USA-based) sites:

FROM getnet.net TO 8.8.8.8.
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 40 byte packets
1 daisy.getnet.net (216.19.223.119) 0.045 ms 0.012 ms 0.012 ms
2 phnx-gsr0.getnet.net (216.19.201.241) 0.601 ms 0.588 ms 0.574
ms
3 wsip-72-214-215-145.ph.ph.cox.net (72.214.215.145) 1.141 ms
1.164 ms 1.262 ms
4 70.169.73.45 (70.169.73.45) 23.411 ms 23.400 ms 23.495 ms
5 langbbrj02-as0.r2.la.cox.net (68.1.1.231) 14.795 ms 14.604 ms
14.765 ms
6 216.239.46.182 (216.239.46.182) 13.749 ms 13.721 ms 13.707 ms
7 72.14.232.85 (72.14.232.85) 41.035 ms 40.160 ms 40.145 ms
8 216.239.43.220 (216.239.43.220) 42.754 ms 42.731 ms
209.85.250.144 (209.85.250.144) 42.856 ms
9 64.233.174.129 (64.233.174.129) 42.690 ms 41.948 ms
64.233.174.123 (64.233.174.123) 42.399 ms
10 216.239.49.166 (216.239.49.166) 49.628 ms 209.85.254.150
(209.85.254.150) 49.598 ms 209.85.254.146 (209.85.254.146) 47.256 ms
11 google-public-dns-a.google.com (8.8.8.8) 42.525 ms 42.455 ms
42.782 ms
---
Executing exec(traceroute, -m 30 -q 1 -w 3 -f 3, 76.126.192.35, 140)
traceroute to 76.126.192.35 (76.126.192.35), 30 hops max, 140 byte
packets
3 rtr-border2-p2p-core2.slac.stanford.edu (134.79.252.145) 0.542 ms
4 slac-mr2-p2p-rtr-border2.slac.stanford.edu (192.68.191.249) 0.360
ms
5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.920 ms
6 sunncr1-sunnsdn2.es.net (134.55.209.98) 1.051 ms
7 eqxsjrt1-sunncr1.es.net (134.55.220.85) 1.425 ms
8 if-3-0.core2.SanJose.Teleglobe.net (206.223.116.81) 13.941 ms
9 te-0-5-0-5-pe01.11greatoaks.ca.ibone.comcast.net (75.149.228.253)
2.658 ms
10 pos-0-4-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.86.53) 5.785
ms
11 pos-0-15-0-0-ar01.sfsutro.ca.sfba.comcast.net (68.86.90.154)
7.164 ms
12 te-8-2-ur01.sanrafael.ca.sfba.comcast.net (68.85.154.177) 7.292
ms
13 *
14 c-76-126-192-35.hsd1.ca.comcast.net (76.126.192.35) 15.671 ms !X
---
1 biad401-fe0-0-0-3-isl-1.gip.net (204.59.152.205) 0.966 ms 0.714
ms 0.668 ms
2 57.64.2.77 (57.64.2.77) 0.766 ms 0.69 ms 0.664 ms
3 57.64.2.205 (57.64.2.205) 15.474 ms 15.567 ms 15.438 ms
4 57.64.2.218 (57.64.2.218) 81.034 ms 70.226 ms 70.073 ms
5 57.64.2.213 (57.64.2.213) 80.313 ms 80.678 ms 80.666 ms
6 57.76.128.245 (57.76.128.245) 82.282 ms 82.696 ms 82.624 ms
7 core2-1-1-0.pao.net.google.com (198.32.176.31) 82.707 ms 82.57
ms 82.962 ms
8 216.239.49.250 (216.239.49.250) 142.441 ms 85.912 ms 85.004 ms
9 216.239.47.186 (216.239.47.186) 100.235 ms 99.271 ms 98.49 ms
10 216.239.43.150 (216.239.43.150) 101.959 ms 101.715 ms
216.239.43.208 (216.239.43.208) 101.407 ms
11 216.239.48.167 (216.239.48.167) 100.185 ms 104.155 ms
216.239.48.165 (216.239.48.165) 101.504 ms
12 216.239.49.246 (216.239.49.246) 113.911 ms 209.85.254.150
(209.85.254.150) 113.448 ms 209.85.254.146 (209.85.254.146) 106.192
ms
13 google-public-dns-a.google.com (8.8.8.8) 101.757 ms 101.466 ms
101.653 ms
---
traceroute to 8.8.8.8 (8.8.8.8), 128 hops max, 40 byte packets
1 gw (192.168.1.1) 0.706 ms 0.687 ms 0.988 ms
2 * * *
3 gig-7-0-7-103.orldfldlnd-rtr2.cfl.rr.com (24.95.230.22) 10.995
ms 13.656 ms 13.471 ms
4 gig4-0-0.orldflaabv-rtr4.cfl.rr.com (24.95.228.193) 20.488 ms
21.621 ms 37.810 ms
5 ge-1-3-0.cr1.atl20.tbone.rr.com (66.109.6.104) 26.112 ms 27.075
ms 25.796 ms
6 ae-1-0.pr0.atl20.tbone.rr.com (66.109.6.177) 23.768 ms 23.950
ms 25.951 ms
7 66.109.9.90 (66.109.9.90) 27.199 ms 27.848 ms 29.850 ms
8 72.14.239.100 (72.14.239.100) 27.043 ms 64.233.174.2
(64.233.174.2) 216.704 ms 72.14.239.100 (72.14.239.100) 27.094 ms
9 72.14.232.213 (72.14.232.213) 29.409 ms 28.484 ms 72.14.232.215
(72.14.232.215) 30.169 ms
10 209.85.253.137 (209.85.253.137) 24.898 ms 209.85.253.145
(209.85.253.145) 31.758 ms 28.016 ms
11 google-public-dns-a.google.com (8.8.8.8) 25.171 ms 28.943 ms
27.978 ms
---
traceroute: Warning: Multiple interfaces found; using 132.249.21.58 @
bge0:1
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 40 byte packets
1 lightning.sdsc.edu (132.249.20.6) 0.498 ms 0.346 ms 0.357 ms
2 dolphin.sdsc.edu (132.249.31.17) 11.208 ms 0.365 ms 0.361 ms
3 dc-tus-dc--sdsc-sdsc1-ge.cenic.net (137.164.24.169) 2.108 ms
2.131 ms 2.235 ms
4 dc-lax-core2--tus-agg1-10ge.cenic.net (137.164.46.6) 3.732 ms
3.501 ms 3.483 ms
5 dc-lax-peer1--lax-core2-ge.cenic.net (137.164.46.118) 3.232 ms
3.259 ms 3.234 ms
6 gi1-1--46.tr01-lsanca01.transitrail.net (137.164.131.245) 3.480
ms 3.511 ms 3.855 ms
7 74.125.49.165 (74.125.49.165) 3.479 ms 3.536 ms 3.474 ms
8 216.239.46.182 (216.239.46.182) 3.728 ms 3.826 ms 3.852 ms
9 72.14.232.85 (72.14.232.85) 30.693 ms 30.625 ms 30.708 ms
10 216.239.43.220 (216.239.43.220) 33.173 ms 33.182 ms 33.168 ms
11 64.233.174.129 (64.233.174.129) 33.178 ms 64.233.174.131
(64.233.174.131) 33.138 ms 64.233.174.129 (64.233.174.129) 43.062 ms
12 216.239.49.166 (216.239.49.166) 40.216 ms 209.85.254.150
(209.85.254.150) 60.031 ms 216.239.49.246 (216.239.49.246) 40.846 ms
13 google-public-dns-a.google.com (8.8.8.8) 32.993 ms 33.117 ms
33.311 ms
---
HOST: evil.alameda.net Loss% Snt Last Avg Best Wrst
StDev
1. rtr-194-55-105-1.alameda.net 0.0% 20 3.6 1.8 1.1
3.9 0.9
2. 66.238.114.202.ptr.us.xo.net 0.0% 20 0.7 0.9 0.6
4.5 0.9
3. ge9-0.DCR1.DC-Fremont-CA.us. 0.0% 20 0.7 0.7 0.6
1.3 0.2
4. ge2-0.dcr2.dc-fremont-ca.us. 0.0% 20 0.6 0.6 0.5
0.9 0.1
5. p5-2-0-2.RAR1.LA-CA.us.xo.ne 0.0% 20 9.4 13.7 9.4
71.8 14.4
6. te-3-1-0.rar3.la-ca.us.xo.ne 0.0% 20 10.3 10.7 10.2
12.3 0.5
7. ae0d1.cir1.la3-ca.us.xo.net 0.0% 20 9.4 14.0 9.4
81.8 16.5
8. 205.158.79.218.ptr.us.xo.net 0.0% 20 10.3 11.7 10.2
25.3 3.8
9. cr1.la2ca.ip.att.net 0.0% 20 15.8 15.6 15.2
16.0 0.2
10. cr1.sffca.ip.att.net 0.0% 20 14.4 14.5 14.1
15.4 0.3
11. 12.122.137.169 0.0% 20 14.6 19.5 14.5
45.8 9.3
12. 12.88.147.10 0.0% 20 13.3 16.6 12.6
62.9 12.4
13. 209.85.240.231 0.0% 20 13.5 17.2 13.3
87.1 16.5
14. 216.239.49.198 0.0% 20 30.1 33.1 30.0
64.7 8.7
15. 216.239.43.228 0.0% 20 33.0 34.5 32.0
67.5 7.8
16. 64.233.174.129 0.0% 20 32.4 32.5 32.1
35.2 0.7
17. 209.85.254.146 0.0% 20 39.6 40.2 32.4
45.9 4.1
18. google-public-dns-a.google.c 0.0% 20 42.0 33.0 32.1
42.0 2.1
---
1 | host191-1 (207.151.191.1) ( 0.292/ 2.115/
5.712) 3/3 100.0%
2 | 1wil-7206 (206.124.224.26) ( 0.681/ 0.906/
1.246) 3/3 100.0%
3 | interworld-gig.lcine (216.66.254.241) ( 0.688/ 0.819/
0.976) 3/3 100.0%
4 | google.com.any2ix.co (206.223.143.41) ( 0.793/ 0.991/
1.347) 3/3 100.0%
5 | 216.239.43.14 (216.239.43.14) ( 1.223/ 1.758/
2.618) 3/3 100.0%
6 | 72.14.232.85 (72.14.232.85) ( 24.655/ 24.891/
25.038) 3/3 100.0%
7 | 216.239.48.34* (216.239.48.34)* ( 27.408/ 27.662/
28.144) 3/3 100.0%
8 | 64.233.174.131** (64.233.174.131)** ( 27.244/ 27.427/
27.557) 3/3 100.0%
9 | 209.85.254.146* (209.85.254.146)* ( 27.553/ 35.299/
40.534) 3/3 100.0%
10 | google-public-dns-a. (8.8.8.8) ( 27.438/ 27.880/
28.641) 3/3 100.0%
---

Wilmer van der Gaast

unread,
Jan 16, 2010, 6:19:49 AM1/16/10
to public-dn...@googlegroups.com
Hello,

Most of your traceroutes seem fine. The one that shows a >100ms path
is not a Google problem and probably affects more traffic:

2010/1/14 hEADcRASH <headc...@gmail.com>:


> 1  biad401-fe0-0-0-3-isl-1.gip.net (204.59.152.205)  0.966 ms  0.714
> ms  0.668 ms
>  2  57.64.2.77 (57.64.2.77)  0.766 ms  0.69 ms  0.664 ms
>  3  57.64.2.205 (57.64.2.205)  15.474 ms  15.567 ms  15.438 ms
>  4  57.64.2.218 (57.64.2.218)  81.034 ms  70.226 ms  70.073 ms
>  5  57.64.2.213 (57.64.2.213)  80.313 ms  80.678 ms  80.666 ms
>  6  57.76.128.245 (57.76.128.245)  82.282 ms  82.696 ms  82.624 ms
>  7  core2-1-1-0.pao.net.google.com (198.32.176.31)  82.707 ms  82.57
> ms  82.962 ms

As you can see going from hop 3 to hop 4 already takes 60-70ms. By the
time you hit the Google network you're already at 80ms. There's little
we can do about that.

gіаиg

unread,
Jan 19, 2010, 9:47:15 AM1/19/10
to public-dns-discuss

On Jan 12, 9:20 pm, Wilmer van der Gaast <wil...@google.com> wrote:
> Hello,
>
> 2010/1/12 gіаиg <daskl...@gmail.com>:


Hi,

Here is my tracert to 8.8.8.8

C:\Users\Giang>tracert 8.8.8.8

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 38 ms 37 ms 43 ms GiangPC [113.162.200.1]
3 38 ms 38 ms 37 ms GiangPC [123.29.14.81]
4 62 ms 62 ms 62 ms GiangPC [123.29.13.85]
5 * * * Request timed out.
6 38 ms 38 ms 38 ms GiangPC [123.29.11.42]
7 419 ms 427 ms 440 ms 219.158.33.101
8 478 ms 447 ms 431 ms 219.158.25.33
9 675 ms 676 ms 639 ms 219.158.25.29
10 320 ms 320 ms 354 ms 219.158.27.118
11 323 ms 317 ms 318 ms 209.85.249.192
12 324 ms 318 ms 318 ms 209.85.250.90
13 317 ms 321 ms 318 ms 209.85.250.101
14 330 ms 318 ms 328 ms 209.85.241.162
15 318 ms 318 ms 317 ms google-public-dns-a.google.com
[8.8.8.8]

I wish you guys could fix this problem because I love Google much and
I don't want to go back to another DNS provider :-s

Best Regards,

Giang

Leonardo González

unread,
Jan 25, 2016, 9:15:16 AM1/25/16
to public-dns-discuss
Hi,

ping to Google dns give me a ping of 153ms

what´s wrong with Google Dns?

Shen Wan

unread,
Jan 25, 2016, 9:57:39 AM1/25/16
to public-dns-discuss
Hi,

Please follow https://developers.google.com/speed/public-dns/docs/using#troubleshooting to diagnose and provide us your result if you still need help.

Thanks!

ming 07

unread,
Feb 23, 2024, 2:49:09 PMFeb 23
to public-dns-discuss
Ping to Google DNS is very high!

📌📌📌📌📌📌📌📌

⚡️📞ติดต่อเรา📞⚡️
LINE: @wy88win
https://cutt.ly/LiCMBLw        

📲 ทางเข้า WY88 📲
https://cutt.ly/HocwybBL                

💸 สมัครสมาชิก 💸
https://cutt.ly/RecwybBL              

📲 WY88 📲
🎰 เล่นเกมสล็อต 🎰
📌 รับเครดิตฟรี 100 บาท
💸 เพียงฝากเข้า 100 บาทขึ้นไป 💸

ทดลอง เล่น สล็อต
สล็อตทดลอง
ทดลอง เล่นสล็อต
ทดลองเล่นสล็อต pg
ทดลองเล่นสล็อต ฟรี
ทดลองเล่นสล็อต
ทดลองเล่นสล็อตฟรี
ทดลองเล่นสล็อต pg ซื้อฟรีสปิน
ทดลองเล่นสล็อต pg ฟรี
ทดลองเล่นสล็อตฟรี 100 บาท
ทดลองเล่นสล็อต pp
สล็อต ทดลอง
สล็อต ทดลอง เล่น
สล็อตทดลองเล่น
สล็อต แจก user ทดลอง เล่น ฟรี ถอน ได้
สล็อต ทดลอง เล่น ฟรี ถอน ได้
ทดลอง เล่น สล็อต pp
ทดลอง เล่น สล็อต โร ม่า
ทดลอง เล่น สล็อต ฟรี ได้ เงิน จริง
ทดลอง เล่น สล็อต ฟรี 88
ทดลอง เล่น เล่น สล็อต ฟาโรห์
ทดลอง เล่น สล็อต pg เบ ท สูง
ทดลอง เล่น สล็อต ยิง ปลา
ทดลอง เล่น สล็อต 888
สล็อต ธอร์
เล่น สล็อต jili บนเว็บ
ทดลอง เล่น สล็อต ฟรี 100 บาท
ทดลอง เล่น สล็อต ฟรี 100 บาท วอ เลท       

Ryan J. Galler

unread,
Feb 23, 2024, 2:49:21 PMFeb 23
to public-dns-discuss
Has anyone seen googledns having high pings for the last few months?

I wonder if it has something to do with the square space transition in google domains...

pun...@google.com

unread,
Feb 23, 2024, 4:23:15 PMFeb 23
to public-dns-discuss
The two are not related.

The network path from your ISP to Google Public DNS IP addresses is completely independent of who is the registrar for your or the query domains.
Reply all
Reply to author
Forward
0 new messages