
Anyone else having Google DNS problems? Google DNS appears to be very, very spotty from our site. Coming from prefix 69.36.128.0/20. I can ping the IPs, but DNS lookups mostly timeout. Haven't been able to replicate from other sites/prefixes. Haven't been able to find a service status page for it either. $ dig @8.8.8.8 google.com ; <<>> DiG 9.9.0 <<>> @8.8.8.8 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ 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 [RFC 1918] 2 <1 ms <1 ms <1 ms [RFC 1918] 3 <1 ms <1 ms <1 ms [RFC 1918] 4 <1 ms <1 ms <1 ms 69.36.131.227 5 <1 ms <1 ms <1 ms ge-11-0-2.mpr2.pao1.us.above.net [64.125.199.237] 6 1 ms 1 ms 1 ms xe-2-2-0.cr2.sjc2.us.above.net [64.125.31.70] 7 1 ms 1 ms 1 ms xe-0-1-0.mpr4.sjc7.us.above.net [64.125.30.178] 8 2 ms 2 ms 1 ms 74.125.49.13 9 2 ms 2 ms 2 ms 216.239.49.168 10 2 ms 2 ms 2 ms 209.85.250.64 11 * * * Request timed out. 12 42 ms 46 ms 23 ms 72.14.233.202 13 24 ms 23 ms 23 ms 64.233.174.129 14 * * * Request timed out. 15 23 ms 24 ms 23 ms google-public-dns-a.google.com [8.8.8.8] Trace complete. -- Crist J. Clark

Seems fine for me. C:\Users\jluthman>dig google.com @8.8.8.8 +short 72.14.204.100 72.14.204.101 72.14.204.138 72.14.204.113 72.14.204.102 C:\Users\jluthman>dig random.org @8.8.8.8 +short 174.143.173.125 C:\Users\jluthman>dig inxwireless.com @8.8.8.8 +short 74.218.88.172 Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Apr 10, 2012 at 5:17 PM, Crist J. Clark <pumpky@sonic.net> wrote:
Anyone else having Google DNS problems? Google DNS appears to be very, very spotty from our site. Coming from prefix 69.36.128.0/20. I can ping the IPs, but DNS lookups mostly timeout. Haven't been able to replicate from other sites/prefixes. Haven't been able to find a service status page for it either.
$ dig @8.8.8.8 google.com
; <<>> DiG 9.9.0 <<>> @8.8.8.8 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ 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 [RFC 1918] 2 <1 ms <1 ms <1 ms [RFC 1918] 3 <1 ms <1 ms <1 ms [RFC 1918] 4 <1 ms <1 ms <1 ms 69.36.131.227 5 <1 ms <1 ms <1 ms ge-11-0-2.mpr2.pao1.us.above.net [64.125.199.237] 6 1 ms 1 ms 1 ms xe-2-2-0.cr2.sjc2.us.above.net [64.125.31.70] 7 1 ms 1 ms 1 ms xe-0-1-0.mpr4.sjc7.us.above.net [64.125.30.178] 8 2 ms 2 ms 1 ms 74.125.49.13 9 2 ms 2 ms 2 ms 216.239.49.168 10 2 ms 2 ms 2 ms 209.85.250.64 11 * * * Request timed out. 12 42 ms 46 ms 23 ms 72.14.233.202 13 24 ms 23 ms 23 ms 64.233.174.129 14 * * * Request timed out. 15 23 ms 24 ms 23 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
-- Crist J. Clark _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

Twitter search shows a bunch of people reporting Google DNS trouble over the past hour. https://twitter.com/#!/search/realtime/google%20dns -george -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Crist J. Clark Sent: Tuesday, April 10, 2012 4:18 PM To: outages@outages.org Subject: [outages] Google DNS Trouble Anyone else having Google DNS problems? Google DNS appears to be very, very spotty from our site. Coming from prefix 69.36.128.0/20. I can ping the IPs, but DNS lookups mostly timeout. Haven't been able to replicate from other sites/prefixes. Haven't been able to find a service status page for it either. $ dig @8.8.8.8 google.com ; <<>> DiG 9.9.0 <<>> @8.8.8.8 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ 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 [RFC 1918] 2 <1 ms <1 ms <1 ms [RFC 1918] 3 <1 ms <1 ms <1 ms [RFC 1918] 4 <1 ms <1 ms <1 ms 69.36.131.227 5 <1 ms <1 ms <1 ms ge-11-0-2.mpr2.pao1.us.above.net [64.125.199.237] 6 1 ms 1 ms 1 ms xe-2-2-0.cr2.sjc2.us.above.net [64.125.31.70] 7 1 ms 1 ms 1 ms xe-0-1-0.mpr4.sjc7.us.above.net [64.125.30.178] 8 2 ms 2 ms 1 ms 74.125.49.13 9 2 ms 2 ms 2 ms 216.239.49.168 10 2 ms 2 ms 2 ms 209.85.250.64 11 * * * Request timed out. 12 42 ms 46 ms 23 ms 72.14.233.202 13 24 ms 23 ms 23 ms 64.233.174.129 14 * * * Request timed out. 15 23 ms 24 ms 23 ms google-public-dns-a.google.com [8.8.8.8] Trace complete. -- Crist J. Clark _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

A little slow on the trace from my side but seems to be responding to me as expected from all 3 locations I tested. Coming from 72.165.142.0/24 173.248.152.0/25 and 75.151.89.0/24. Seems to slow down when it hits the Google network from Comcast and Centurylink. Blake Pfankuch -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Crist J. Clark Sent: Tuesday, April 10, 2012 3:18 PM To: outages@outages.org Subject: [outages] Google DNS Trouble Anyone else having Google DNS problems? Google DNS appears to be very, very spotty from our site. Coming from prefix 69.36.128.0/20. I can ping the IPs, but DNS lookups mostly timeout. Haven't been able to replicate from other sites/prefixes. Haven't been able to find a service status page for it either. $ dig @8.8.8.8 google.com ; <<>> DiG 9.9.0 <<>> @8.8.8.8 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ 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 [RFC 1918] 2 <1 ms <1 ms <1 ms [RFC 1918] 3 <1 ms <1 ms <1 ms [RFC 1918] 4 <1 ms <1 ms <1 ms 69.36.131.227 5 <1 ms <1 ms <1 ms ge-11-0-2.mpr2.pao1.us.above.net [64.125.199.237] 6 1 ms 1 ms 1 ms xe-2-2-0.cr2.sjc2.us.above.net [64.125.31.70] 7 1 ms 1 ms 1 ms xe-0-1-0.mpr4.sjc7.us.above.net [64.125.30.178] 8 2 ms 2 ms 1 ms 74.125.49.13 9 2 ms 2 ms 2 ms 216.239.49.168 10 2 ms 2 ms 2 ms 209.85.250.64 11 * * * Request timed out. 12 42 ms 46 ms 23 ms 72.14.233.202 13 24 ms 23 ms 23 ms 64.233.174.129 14 * * * Request timed out. 15 23 ms 24 ms 23 ms google-public-dns-a.google.com [8.8.8.8] Trace complete. -- Crist J. Clark _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

Remember that it's anycasted and others aren't going to get directed to the same servers that you are (unless they're in the same area as you are, network wise). It's probably a localized issue. -- Jeremy L. Gaddis On Apr 10, 2012, at 5:17 PM, Crist J. Clark wrote:
Anyone else having Google DNS problems? Google DNS appears to be very, very spotty from our site. Coming from prefix 69.36.128.0/20. I can ping the IPs, but DNS lookups mostly timeout. Haven't been able to replicate from other sites/prefixes. Haven't been able to find a service status page for it either.
$ dig @8.8.8.8 google.com
; <<>> DiG 9.9.0 <<>> @8.8.8.8 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ 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 [RFC 1918] 2 <1 ms <1 ms <1 ms [RFC 1918] 3 <1 ms <1 ms <1 ms [RFC 1918] 4 <1 ms <1 ms <1 ms 69.36.131.227 5 <1 ms <1 ms <1 ms ge-11-0-2.mpr2.pao1.us.above.net [64.125.199.237] 6 1 ms 1 ms 1 ms xe-2-2-0.cr2.sjc2.us.above.net [64.125.31.70] 7 1 ms 1 ms 1 ms xe-0-1-0.mpr4.sjc7.us.above.net [64.125.30.178] 8 2 ms 2 ms 1 ms 74.125.49.13 9 2 ms 2 ms 2 ms 216.239.49.168 10 2 ms 2 ms 2 ms 209.85.250.64 11 * * * Request timed out. 12 42 ms 46 ms 23 ms 72.14.233.202 13 24 ms 23 ms 23 ms 64.233.174.129 14 * * * Request timed out. 15 23 ms 24 ms 23 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
-- Crist J. Clark _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (5)
-
Blake Pfankuch
-
Crist J. Clark
-
George Sarlas
-
Jeremy L. Gaddis
-
Josh Luthman