Hi all, Is anybody else having issues with the Google DNS public servers? From the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results. Met vriendelijke groet / with kind regards / Atenciosamente, Wieger Bontekoe +31 (0)20 760 4909 | w.bontekoe@wipabv.nl<mailto:w.bontekoe@wipabv.nl> [WIPA Nederland B.V.]<http://www.wipa.nl/> [Facebook]<https://www.facebook.com/WIPABV> [Twitter] <https://www.twitter.com/WIPABV> [Skype] <skype:wipabv> Office the Netherlands: Paul van Vlissingenstraat 16 1096 BK Amsterdam Office Brasil: Av. Eng. Antônio de Góes 60 - 7º e 14º Boa Viagem, Recife, Brasil This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. WIPA is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company. Op al onze leveringen zijn onze algemene voorwaarden van toepassing. Wanneer u iets bij ons besteld gaat u met deze voorwaarden akkoord. Alle prijzen zijn exclusief BTW en onder voorbehoud van eventuele wijzigingen en/of typ- en schrijfouten.
On Tue, Feb 10, 2015 at 5:58 PM, Wieger Bontekoe via Outages < outages@outages.org> wrote:
Hi all,
Is anybody else having issues with the Google DNS public servers? From the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results.
no problem in Japan. ; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 ox.ac.uk NS ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12558 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ox.ac.uk. IN NS ;; ANSWER SECTION: ox.ac.uk. 21419 IN NS ns2.ja.net. ox.ac.uk. 21419 IN NS dns2.ox.ac.uk. ox.ac.uk. 21419 IN NS dns0.ox.ac.uk. ox.ac.uk. 21419 IN NS dns1.ox.ac.uk. ;; Query time: 43 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Tue Feb 10 18:09:43 2015 ;; MSG SIZE rcvd: 107 ; <<>> DiG 9.8.3-P1 <<>> @8.8.4.4 ox.ac.uk NS ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25190 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ox.ac.uk. IN NS ;; ANSWER SECTION: ox.ac.uk. 21599 IN NS ns2.ja.net. ox.ac.uk. 21599 IN NS dns0.ox.ac.uk. ox.ac.uk. 21599 IN NS dns2.ox.ac.uk. ox.ac.uk. 21599 IN NS dns1.ox.ac.uk. ;; Query time: 301 msec ;; SERVER: 8.8.4.4#53(8.8.4.4) ;; WHEN: Tue Feb 10 18:09:43 2015 ;; MSG SIZE rcvd: 107 ; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8888 ox.ac.uk NS ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34841 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ox.ac.uk. IN NS ;; ANSWER SECTION: ox.ac.uk. 5821 IN NS dns1.ox.ac.uk. ox.ac.uk. 5821 IN NS dns0.ox.ac.uk. ox.ac.uk. 5821 IN NS dns2.ox.ac.uk. ox.ac.uk. 5821 IN NS ns2.ja.net. ;; Query time: 67 msec ;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888) ;; WHEN: Tue Feb 10 18:09:43 2015 ;; MSG SIZE rcvd: 107 ; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8844 ox.ac.uk NS ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36150 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ox.ac.uk. IN NS ;; ANSWER SECTION: ox.ac.uk. 21419 IN NS ns2.ja.net. ox.ac.uk. 21419 IN NS dns2.ox.ac.uk. ox.ac.uk. 21419 IN NS dns0.ox.ac.uk. ox.ac.uk. 21419 IN NS dns1.ox.ac.uk. ;; Query time: 72 msec ;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844) ;; WHEN: Tue Feb 10 18:09:43 2015 ;; MSG SIZE rcvd: 107 traceroute from 192.168.0.9 to 8.8.8.8 1 192.168.0.1 0.691 ms [mtu: 1500] 2 121.106.107.1 2.943 ms [mtu: 1500] 3 125.48.119.34 1.452 ms [mtu: 1500] 4 118.152.208.134 2.283 ms [mtu: 1500] 5 118.152.210.45 3.166 ms [mtu: 1500] 6 106.162.175.153 3.487 ms [mtu: 1500] 7 59.128.5.86 2.968 ms [mtu: 1500] 8 72.14.204.58 48.487 ms [mtu: 1500] 9 72.14.237.70 48.530 ms [mtu: 1500] 10 66.249.95.109 3.489 ms [mtu: 1500] 11 8.8.8.8 6.759 ms [mtu: 1500] traceroute from 192.168.0.9 to 8.8.4.4 1 192.168.0.1 0.648 ms [mtu: 1500] 2 121.106.107.1 1.987 ms [mtu: 1500] 3 125.48.119.34 2.616 ms [mtu: 1500] 4 118.152.208.134 1.720 ms [mtu: 1500] 5 111.86.159.109 3.594 ms [mtu: 1500] 6 106.162.175.161 3.249 ms [mtu: 1500] 7 59.128.5.94 2.328 ms [mtu: 1500] 8 72.14.204.58 45.635 ms [mtu: 1500] 9 72.14.236.215 3.090 ms [mtu: 1500] 10 72.14.239.165 3.717 ms [mtu: 1500] 11 8.8.4.4 2.895 ms [mtu: 1500] traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888 1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.709 ms [mtu: 1500] 2 240f:10:4000::1 3.340 ms [mtu: 1500] 3 2001:268:f203:4d1::1 1.437 ms [mtu: 1500] 4 2001:268:f203:1ff::1 2.254 ms [mtu: 1500] 5 2001:268:fa01:7fe::1 4.246 ms [mtu: 1500] 6 2001:268:fa00:ffcf::1 5.791 ms [mtu: 1500] 7 2001:268:fb02:9e::2 3.439 ms [mtu: 1500] 8 2001:4860:1:1:0:9d4:: 3.930 ms [mtu: 1500] 9 2001:4860::1:0:8f9a 3.978 ms [mtu: 1500] 10 2001:4860::1:0:6302 6.586 ms [mtu: 1500] 11 2001:4860::8:0:73ad 61.583 ms [mtu: 1500] 12 2001:4860::2:0:b7 64.719 ms [mtu: 1500] 13 * 14 2001:4860:4860::8888 65.174 ms [mtu: 1500] traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844 1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.704 ms [mtu: 1500] 2 240f:10:4000::1 2.721 ms [mtu: 1500] 3 2001:268:f203:4d1::1 2.078 ms [mtu: 1500] 4 2001:268:f203:1ff::1 2.604 ms [mtu: 1500] 5 2001:268:fa01:7ff::1 3.682 ms [mtu: 1500] 6 2001:268:fa00:ffdf::1 2.755 ms [mtu: 1500] 7 2001:268:fb02:9e::2 3.403 ms [mtu: 1500] 8 2001:4860:1:1:0:9d4:: 3.550 ms [mtu: 1500] 9 2001:4860::1:0:6626 4.762 ms [mtu: 1500] 10 2001:4860::1:0:6302 6.027 ms [mtu: 1500] 11 2001:4860::8:0:73ad 60.917 ms [mtu: 1500] 12 2001:4860::2:0:b7 65.229 ms [mtu: 1500] 13 * 14 2001:4860:4860::8844 64.426 ms [mtu: 1500] ping 192.168.0.9 to 8.8.8.8: 84 byte packets 84 bytes from 8.8.8.8, seq=0 ttl=53 time=4.318 ms 84 bytes from 8.8.8.8, seq=1 ttl=53 time=4.421 ms 84 bytes from 8.8.8.8, seq=2 ttl=53 time=4.213 ms 84 bytes from 8.8.8.8, seq=3 ttl=53 time=4.031 ms 84 bytes from 8.8.8.8, seq=4 ttl=53 time=4.815 ms 84 bytes from 8.8.8.8, seq=5 ttl=53 time=3.960 ms 84 bytes from 8.8.8.8, seq=6 ttl=53 time=3.998 ms 84 bytes from 8.8.8.8, seq=7 ttl=53 time=4.327 ms 84 bytes from 8.8.8.8, seq=8 ttl=53 time=3.995 ms 84 bytes from 8.8.8.8, seq=9 ttl=53 time=4.683 ms --- 8.8.8.8 ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 3.960/4.276/4.815/0.283 ms ping 192.168.0.9 to 8.8.4.4: 84 byte packets 84 bytes from 8.8.4.4, seq=0 ttl=54 time=3.246 ms 84 bytes from 8.8.4.4, seq=1 ttl=54 time=3.746 ms 84 bytes from 8.8.4.4, seq=2 ttl=54 time=3.370 ms 84 bytes from 8.8.4.4, seq=3 ttl=54 time=3.285 ms 84 bytes from 8.8.4.4, seq=4 ttl=54 time=3.463 ms 84 bytes from 8.8.4.4, seq=5 ttl=54 time=3.314 ms 84 bytes from 8.8.4.4, seq=6 ttl=54 time=3.836 ms 84 bytes from 8.8.4.4, seq=7 ttl=54 time=3.174 ms 84 bytes from 8.8.4.4, seq=8 ttl=54 time=3.284 ms 84 bytes from 8.8.4.4, seq=9 ttl=54 time=3.718 ms --- 8.8.4.4 ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 3.174/3.443/3.836/0.224 ms ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888: 104 byte packets 104 bytes from 2001:4860:4860::8888, seq=0 ttl=0 time=64.964 ms 104 bytes from 2001:4860:4860::8888, seq=1 ttl=0 time=64.570 ms 104 bytes from 2001:4860:4860::8888, seq=2 ttl=0 time=64.540 ms 104 bytes from 2001:4860:4860::8888, seq=3 ttl=0 time=65.294 ms 104 bytes from 2001:4860:4860::8888, seq=4 ttl=0 time=64.672 ms 104 bytes from 2001:4860:4860::8888, seq=5 ttl=0 time=65.249 ms 104 bytes from 2001:4860:4860::8888, seq=6 ttl=0 time=65.371 ms 104 bytes from 2001:4860:4860::8888, seq=7 ttl=0 time=65.215 ms 104 bytes from 2001:4860:4860::8888, seq=8 ttl=0 time=64.641 ms 104 bytes from 2001:4860:4860::8888, seq=9 ttl=0 time=65.535 ms --- 2001:4860:4860::8888 ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 64.540/65.005/65.535/0.353 ms ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844: 104 byte packets 104 bytes from 2001:4860:4860::8844, seq=0 ttl=0 time=66.139 ms 104 bytes from 2001:4860:4860::8844, seq=1 ttl=0 time=65.642 ms 104 bytes from 2001:4860:4860::8844, seq=2 ttl=0 time=66.495 ms 104 bytes from 2001:4860:4860::8844, seq=3 ttl=0 time=66.542 ms 104 bytes from 2001:4860:4860::8844, seq=4 ttl=0 time=65.978 ms 104 bytes from 2001:4860:4860::8844, seq=5 ttl=0 time=66.279 ms 104 bytes from 2001:4860:4860::8844, seq=6 ttl=0 time=66.440 ms 104 bytes from 2001:4860:4860::8844, seq=7 ttl=0 time=66.343 ms 104 bytes from 2001:4860:4860::8844, seq=8 ttl=0 time=65.817 ms 104 bytes from 2001:4860:4860::8844, seq=9 ttl=0 time=66.205 ms --- 2001:4860:4860::8844 ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 65.642/66.188/66.542/0.282 ms
I am seeing intermittent issue from EU, specifically from Amsterdam. US and Asian datacenters are fine for me. curl: (6) Could not resolve host: www.XYZ.com Regards, Aditya Patawari http://blog.adityapatawari.com/ India On Tue, Feb 10, 2015 at 2:41 PM, dikshie via Outages <outages@outages.org> wrote:
On Tue, Feb 10, 2015 at 5:58 PM, Wieger Bontekoe via Outages <outages@outages.org> wrote:
Hi all,
Is anybody else having issues with the Google DNS public servers? From the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results.
no problem in Japan.
; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12558
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21419 IN NS ns2.ja.net.
ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
;; Query time: 43 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @8.8.4.4 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25190
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21599 IN NS ns2.ja.net.
ox.ac.uk. 21599 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21599 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21599 IN NS dns1.ox.ac.uk.
;; Query time: 301 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8888 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34841
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 5821 IN NS dns1.ox.ac.uk.
ox.ac.uk. 5821 IN NS dns0.ox.ac.uk.
ox.ac.uk. 5821 IN NS dns2.ox.ac.uk.
ox.ac.uk. 5821 IN NS ns2.ja.net.
;; Query time: 67 msec
;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8844 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36150
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21419 IN NS ns2.ja.net.
ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
;; Query time: 72 msec
;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
traceroute from 192.168.0.9 to 8.8.8.8
1 192.168.0.1 0.691 ms [mtu: 1500]
2 121.106.107.1 2.943 ms [mtu: 1500]
3 125.48.119.34 1.452 ms [mtu: 1500]
4 118.152.208.134 2.283 ms [mtu: 1500]
5 118.152.210.45 3.166 ms [mtu: 1500]
6 106.162.175.153 3.487 ms [mtu: 1500]
7 59.128.5.86 2.968 ms [mtu: 1500]
8 72.14.204.58 48.487 ms [mtu: 1500]
9 72.14.237.70 48.530 ms [mtu: 1500]
10 66.249.95.109 3.489 ms [mtu: 1500]
11 8.8.8.8 6.759 ms [mtu: 1500]
traceroute from 192.168.0.9 to 8.8.4.4
1 192.168.0.1 0.648 ms [mtu: 1500]
2 121.106.107.1 1.987 ms [mtu: 1500]
3 125.48.119.34 2.616 ms [mtu: 1500]
4 118.152.208.134 1.720 ms [mtu: 1500]
5 111.86.159.109 3.594 ms [mtu: 1500]
6 106.162.175.161 3.249 ms [mtu: 1500]
7 59.128.5.94 2.328 ms [mtu: 1500]
8 72.14.204.58 45.635 ms [mtu: 1500]
9 72.14.236.215 3.090 ms [mtu: 1500]
10 72.14.239.165 3.717 ms [mtu: 1500]
11 8.8.4.4 2.895 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.709 ms [mtu: 1500]
2 240f:10:4000::1 3.340 ms [mtu: 1500]
3 2001:268:f203:4d1::1 1.437 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.254 ms [mtu: 1500]
5 2001:268:fa01:7fe::1 4.246 ms [mtu: 1500]
6 2001:268:fa00:ffcf::1 5.791 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.439 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.930 ms [mtu: 1500]
9 2001:4860::1:0:8f9a 3.978 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.586 ms [mtu: 1500]
11 2001:4860::8:0:73ad 61.583 ms [mtu: 1500]
12 2001:4860::2:0:b7 64.719 ms [mtu: 1500]
13 *
14 2001:4860:4860::8888 65.174 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.704 ms [mtu: 1500]
2 240f:10:4000::1 2.721 ms [mtu: 1500]
3 2001:268:f203:4d1::1 2.078 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.604 ms [mtu: 1500]
5 2001:268:fa01:7ff::1 3.682 ms [mtu: 1500]
6 2001:268:fa00:ffdf::1 2.755 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.403 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.550 ms [mtu: 1500]
9 2001:4860::1:0:6626 4.762 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.027 ms [mtu: 1500]
11 2001:4860::8:0:73ad 60.917 ms [mtu: 1500]
12 2001:4860::2:0:b7 65.229 ms [mtu: 1500]
13 *
14 2001:4860:4860::8844 64.426 ms [mtu: 1500]
ping 192.168.0.9 to 8.8.8.8: 84 byte packets
84 bytes from 8.8.8.8, seq=0 ttl=53 time=4.318 ms
84 bytes from 8.8.8.8, seq=1 ttl=53 time=4.421 ms
84 bytes from 8.8.8.8, seq=2 ttl=53 time=4.213 ms
84 bytes from 8.8.8.8, seq=3 ttl=53 time=4.031 ms
84 bytes from 8.8.8.8, seq=4 ttl=53 time=4.815 ms
84 bytes from 8.8.8.8, seq=5 ttl=53 time=3.960 ms
84 bytes from 8.8.8.8, seq=6 ttl=53 time=3.998 ms
84 bytes from 8.8.8.8, seq=7 ttl=53 time=4.327 ms
84 bytes from 8.8.8.8, seq=8 ttl=53 time=3.995 ms
84 bytes from 8.8.8.8, seq=9 ttl=53 time=4.683 ms
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.960/4.276/4.815/0.283 ms
ping 192.168.0.9 to 8.8.4.4: 84 byte packets
84 bytes from 8.8.4.4, seq=0 ttl=54 time=3.246 ms
84 bytes from 8.8.4.4, seq=1 ttl=54 time=3.746 ms
84 bytes from 8.8.4.4, seq=2 ttl=54 time=3.370 ms
84 bytes from 8.8.4.4, seq=3 ttl=54 time=3.285 ms
84 bytes from 8.8.4.4, seq=4 ttl=54 time=3.463 ms
84 bytes from 8.8.4.4, seq=5 ttl=54 time=3.314 ms
84 bytes from 8.8.4.4, seq=6 ttl=54 time=3.836 ms
84 bytes from 8.8.4.4, seq=7 ttl=54 time=3.174 ms
84 bytes from 8.8.4.4, seq=8 ttl=54 time=3.284 ms
84 bytes from 8.8.4.4, seq=9 ttl=54 time=3.718 ms
--- 8.8.4.4 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.174/3.443/3.836/0.224 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888: 104 byte packets
104 bytes from 2001:4860:4860::8888, seq=0 ttl=0 time=64.964 ms
104 bytes from 2001:4860:4860::8888, seq=1 ttl=0 time=64.570 ms
104 bytes from 2001:4860:4860::8888, seq=2 ttl=0 time=64.540 ms
104 bytes from 2001:4860:4860::8888, seq=3 ttl=0 time=65.294 ms
104 bytes from 2001:4860:4860::8888, seq=4 ttl=0 time=64.672 ms
104 bytes from 2001:4860:4860::8888, seq=5 ttl=0 time=65.249 ms
104 bytes from 2001:4860:4860::8888, seq=6 ttl=0 time=65.371 ms
104 bytes from 2001:4860:4860::8888, seq=7 ttl=0 time=65.215 ms
104 bytes from 2001:4860:4860::8888, seq=8 ttl=0 time=64.641 ms
104 bytes from 2001:4860:4860::8888, seq=9 ttl=0 time=65.535 ms
--- 2001:4860:4860::8888 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 64.540/65.005/65.535/0.353 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844: 104 byte packets
104 bytes from 2001:4860:4860::8844, seq=0 ttl=0 time=66.139 ms
104 bytes from 2001:4860:4860::8844, seq=1 ttl=0 time=65.642 ms
104 bytes from 2001:4860:4860::8844, seq=2 ttl=0 time=66.495 ms
104 bytes from 2001:4860:4860::8844, seq=3 ttl=0 time=66.542 ms
104 bytes from 2001:4860:4860::8844, seq=4 ttl=0 time=65.978 ms
104 bytes from 2001:4860:4860::8844, seq=5 ttl=0 time=66.279 ms
104 bytes from 2001:4860:4860::8844, seq=6 ttl=0 time=66.440 ms
104 bytes from 2001:4860:4860::8844, seq=7 ttl=0 time=66.343 ms
104 bytes from 2001:4860:4860::8844, seq=8 ttl=0 time=65.817 ms
104 bytes from 2001:4860:4860::8844, seq=9 ttl=0 time=66.205 ms
--- 2001:4860:4860::8844 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 65.642/66.188/66.542/0.282 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I too have been registering failures when attempting to use Googles public resolvers at 8.8.8.8 via the AMSIX exchange. This began at roughly 0200 GMT. We have not attempted via transit or alternative Google DNS resolvers. -Nick On 2/10/15, 4:37 PM, "Aditya Patawari via Outages" <outages@outages.org> wrote:
I am seeing intermittent issue from EU, specifically from Amsterdam. US and Asian datacenters are fine for me. curl: (6) Could not resolve host: www.XYZ.com
Regards, Aditya Patawari http://blog.adityapatawari.com/ India
On Tue, Feb 10, 2015 at 2:41 PM, dikshie via Outages <outages@outages.org> wrote:
On Tue, Feb 10, 2015 at 5:58 PM, Wieger Bontekoe via Outages <outages@outages.org> wrote:
Hi all,
Is anybody else having issues with the Google DNS public servers? From the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results.
no problem in Japan.
; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12558
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21419 IN NS ns2.ja.net.
ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
;; Query time: 43 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @8.8.4.4 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25190
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21599 IN NS ns2.ja.net.
ox.ac.uk. 21599 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21599 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21599 IN NS dns1.ox.ac.uk.
;; Query time: 301 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8888 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34841
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 5821 IN NS dns1.ox.ac.uk.
ox.ac.uk. 5821 IN NS dns0.ox.ac.uk.
ox.ac.uk. 5821 IN NS dns2.ox.ac.uk.
ox.ac.uk. 5821 IN NS ns2.ja.net.
;; Query time: 67 msec
;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8844 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36150
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21419 IN NS ns2.ja.net.
ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
;; Query time: 72 msec
;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
traceroute from 192.168.0.9 to 8.8.8.8
1 192.168.0.1 0.691 ms [mtu: 1500]
2 121.106.107.1 2.943 ms [mtu: 1500]
3 125.48.119.34 1.452 ms [mtu: 1500]
4 118.152.208.134 2.283 ms [mtu: 1500]
5 118.152.210.45 3.166 ms [mtu: 1500]
6 106.162.175.153 3.487 ms [mtu: 1500]
7 59.128.5.86 2.968 ms [mtu: 1500]
8 72.14.204.58 48.487 ms [mtu: 1500]
9 72.14.237.70 48.530 ms [mtu: 1500]
10 66.249.95.109 3.489 ms [mtu: 1500]
11 8.8.8.8 6.759 ms [mtu: 1500]
traceroute from 192.168.0.9 to 8.8.4.4
1 192.168.0.1 0.648 ms [mtu: 1500]
2 121.106.107.1 1.987 ms [mtu: 1500]
3 125.48.119.34 2.616 ms [mtu: 1500]
4 118.152.208.134 1.720 ms [mtu: 1500]
5 111.86.159.109 3.594 ms [mtu: 1500]
6 106.162.175.161 3.249 ms [mtu: 1500]
7 59.128.5.94 2.328 ms [mtu: 1500]
8 72.14.204.58 45.635 ms [mtu: 1500]
9 72.14.236.215 3.090 ms [mtu: 1500]
10 72.14.239.165 3.717 ms [mtu: 1500]
11 8.8.4.4 2.895 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.709 ms [mtu: 1500]
2 240f:10:4000::1 3.340 ms [mtu: 1500]
3 2001:268:f203:4d1::1 1.437 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.254 ms [mtu: 1500]
5 2001:268:fa01:7fe::1 4.246 ms [mtu: 1500]
6 2001:268:fa00:ffcf::1 5.791 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.439 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.930 ms [mtu: 1500]
9 2001:4860::1:0:8f9a 3.978 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.586 ms [mtu: 1500]
11 2001:4860::8:0:73ad 61.583 ms [mtu: 1500]
12 2001:4860::2:0:b7 64.719 ms [mtu: 1500]
13 *
14 2001:4860:4860::8888 65.174 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.704 ms [mtu: 1500]
2 240f:10:4000::1 2.721 ms [mtu: 1500]
3 2001:268:f203:4d1::1 2.078 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.604 ms [mtu: 1500]
5 2001:268:fa01:7ff::1 3.682 ms [mtu: 1500]
6 2001:268:fa00:ffdf::1 2.755 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.403 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.550 ms [mtu: 1500]
9 2001:4860::1:0:6626 4.762 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.027 ms [mtu: 1500]
11 2001:4860::8:0:73ad 60.917 ms [mtu: 1500]
12 2001:4860::2:0:b7 65.229 ms [mtu: 1500]
13 *
14 2001:4860:4860::8844 64.426 ms [mtu: 1500]
ping 192.168.0.9 to 8.8.8.8: 84 byte packets
84 bytes from 8.8.8.8, seq=0 ttl=53 time=4.318 ms
84 bytes from 8.8.8.8, seq=1 ttl=53 time=4.421 ms
84 bytes from 8.8.8.8, seq=2 ttl=53 time=4.213 ms
84 bytes from 8.8.8.8, seq=3 ttl=53 time=4.031 ms
84 bytes from 8.8.8.8, seq=4 ttl=53 time=4.815 ms
84 bytes from 8.8.8.8, seq=5 ttl=53 time=3.960 ms
84 bytes from 8.8.8.8, seq=6 ttl=53 time=3.998 ms
84 bytes from 8.8.8.8, seq=7 ttl=53 time=4.327 ms
84 bytes from 8.8.8.8, seq=8 ttl=53 time=3.995 ms
84 bytes from 8.8.8.8, seq=9 ttl=53 time=4.683 ms
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.960/4.276/4.815/0.283 ms
ping 192.168.0.9 to 8.8.4.4: 84 byte packets
84 bytes from 8.8.4.4, seq=0 ttl=54 time=3.246 ms
84 bytes from 8.8.4.4, seq=1 ttl=54 time=3.746 ms
84 bytes from 8.8.4.4, seq=2 ttl=54 time=3.370 ms
84 bytes from 8.8.4.4, seq=3 ttl=54 time=3.285 ms
84 bytes from 8.8.4.4, seq=4 ttl=54 time=3.463 ms
84 bytes from 8.8.4.4, seq=5 ttl=54 time=3.314 ms
84 bytes from 8.8.4.4, seq=6 ttl=54 time=3.836 ms
84 bytes from 8.8.4.4, seq=7 ttl=54 time=3.174 ms
84 bytes from 8.8.4.4, seq=8 ttl=54 time=3.284 ms
84 bytes from 8.8.4.4, seq=9 ttl=54 time=3.718 ms
--- 8.8.4.4 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.174/3.443/3.836/0.224 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888: 104 byte packets
104 bytes from 2001:4860:4860::8888, seq=0 ttl=0 time=64.964 ms
104 bytes from 2001:4860:4860::8888, seq=1 ttl=0 time=64.570 ms
104 bytes from 2001:4860:4860::8888, seq=2 ttl=0 time=64.540 ms
104 bytes from 2001:4860:4860::8888, seq=3 ttl=0 time=65.294 ms
104 bytes from 2001:4860:4860::8888, seq=4 ttl=0 time=64.672 ms
104 bytes from 2001:4860:4860::8888, seq=5 ttl=0 time=65.249 ms
104 bytes from 2001:4860:4860::8888, seq=6 ttl=0 time=65.371 ms
104 bytes from 2001:4860:4860::8888, seq=7 ttl=0 time=65.215 ms
104 bytes from 2001:4860:4860::8888, seq=8 ttl=0 time=64.641 ms
104 bytes from 2001:4860:4860::8888, seq=9 ttl=0 time=65.535 ms
--- 2001:4860:4860::8888 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 64.540/65.005/65.535/0.353 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844: 104 byte packets
104 bytes from 2001:4860:4860::8844, seq=0 ttl=0 time=66.139 ms
104 bytes from 2001:4860:4860::8844, seq=1 ttl=0 time=65.642 ms
104 bytes from 2001:4860:4860::8844, seq=2 ttl=0 time=66.495 ms
104 bytes from 2001:4860:4860::8844, seq=3 ttl=0 time=66.542 ms
104 bytes from 2001:4860:4860::8844, seq=4 ttl=0 time=65.978 ms
104 bytes from 2001:4860:4860::8844, seq=5 ttl=0 time=66.279 ms
104 bytes from 2001:4860:4860::8844, seq=6 ttl=0 time=66.440 ms
104 bytes from 2001:4860:4860::8844, seq=7 ttl=0 time=66.343 ms
104 bytes from 2001:4860:4860::8844, seq=8 ttl=0 time=65.817 ms
104 bytes from 2001:4860:4860::8844, seq=9 ttl=0 time=66.205 ms
--- 2001:4860:4860::8844 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 65.642/66.188/66.542/0.282 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
"There are indications of a broken fiber cable connection, causing a massive network issue in the Amsterdam area." - https://twitter.com/StatusPltfrmIQ/status/565078428442198016 A dutch person told me he cant access many government sites and some news sites. An example site he cant access is http://www.rijksoverheid.nl On Tue, Feb 10, 2015 at 5:04 PM, Nicholas Schmidt via Outages < outages@outages.org> wrote:
I too have been registering failures when attempting to use Googles public resolvers at 8.8.8.8 via the AMSIX exchange. This began at roughly 0200 GMT.
We have not attempted via transit or alternative Google DNS resolvers.
-Nick
On 2/10/15, 4:37 PM, "Aditya Patawari via Outages" <outages@outages.org> wrote:
I am seeing intermittent issue from EU, specifically from Amsterdam. US and Asian datacenters are fine for me. curl: (6) Could not resolve host: www.XYZ.com
Regards, Aditya Patawari http://blog.adityapatawari.com/ India
On Tue, Feb 10, 2015 at 2:41 PM, dikshie via Outages <outages@outages.org> wrote:
On Tue, Feb 10, 2015 at 5:58 PM, Wieger Bontekoe via Outages <outages@outages.org> wrote:
Hi all,
Is anybody else having issues with the Google DNS public servers? From the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results.
no problem in Japan.
; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12558
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21419 IN NS ns2.ja.net.
ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
;; Query time: 43 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @8.8.4.4 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25190
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21599 IN NS ns2.ja.net.
ox.ac.uk. 21599 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21599 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21599 IN NS dns1.ox.ac.uk.
;; Query time: 301 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8888 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34841
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 5821 IN NS dns1.ox.ac.uk.
ox.ac.uk. 5821 IN NS dns0.ox.ac.uk.
ox.ac.uk. 5821 IN NS dns2.ox.ac.uk.
ox.ac.uk. 5821 IN NS ns2.ja.net.
;; Query time: 67 msec
;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8844 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36150
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21419 IN NS ns2.ja.net.
ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
;; Query time: 72 msec
;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
traceroute from 192.168.0.9 to 8.8.8.8
1 192.168.0.1 0.691 ms [mtu: 1500]
2 121.106.107.1 2.943 ms [mtu: 1500]
3 125.48.119.34 1.452 ms [mtu: 1500]
4 118.152.208.134 2.283 ms [mtu: 1500]
5 118.152.210.45 3.166 ms [mtu: 1500]
6 106.162.175.153 3.487 ms [mtu: 1500]
7 59.128.5.86 2.968 ms [mtu: 1500]
8 72.14.204.58 48.487 ms [mtu: 1500]
9 72.14.237.70 48.530 ms [mtu: 1500]
10 66.249.95.109 3.489 ms [mtu: 1500]
11 8.8.8.8 6.759 ms [mtu: 1500]
traceroute from 192.168.0.9 to 8.8.4.4
1 192.168.0.1 0.648 ms [mtu: 1500]
2 121.106.107.1 1.987 ms [mtu: 1500]
3 125.48.119.34 2.616 ms [mtu: 1500]
4 118.152.208.134 1.720 ms [mtu: 1500]
5 111.86.159.109 3.594 ms [mtu: 1500]
6 106.162.175.161 3.249 ms [mtu: 1500]
7 59.128.5.94 2.328 ms [mtu: 1500]
8 72.14.204.58 45.635 ms [mtu: 1500]
9 72.14.236.215 3.090 ms [mtu: 1500]
10 72.14.239.165 3.717 ms [mtu: 1500]
11 8.8.4.4 2.895 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.709 ms [mtu: 1500]
2 240f:10:4000::1 3.340 ms [mtu: 1500]
3 2001:268:f203:4d1::1 1.437 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.254 ms [mtu: 1500]
5 2001:268:fa01:7fe::1 4.246 ms [mtu: 1500]
6 2001:268:fa00:ffcf::1 5.791 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.439 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.930 ms [mtu: 1500]
9 2001:4860::1:0:8f9a 3.978 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.586 ms [mtu: 1500]
11 2001:4860::8:0:73ad 61.583 ms [mtu: 1500]
12 2001:4860::2:0:b7 64.719 ms [mtu: 1500]
13 *
14 2001:4860:4860::8888 65.174 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.704 ms [mtu: 1500]
2 240f:10:4000::1 2.721 ms [mtu: 1500]
3 2001:268:f203:4d1::1 2.078 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.604 ms [mtu: 1500]
5 2001:268:fa01:7ff::1 3.682 ms [mtu: 1500]
6 2001:268:fa00:ffdf::1 2.755 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.403 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.550 ms [mtu: 1500]
9 2001:4860::1:0:6626 4.762 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.027 ms [mtu: 1500]
11 2001:4860::8:0:73ad 60.917 ms [mtu: 1500]
12 2001:4860::2:0:b7 65.229 ms [mtu: 1500]
13 *
14 2001:4860:4860::8844 64.426 ms [mtu: 1500]
ping 192.168.0.9 to 8.8.8.8: 84 byte packets
84 bytes from 8.8.8.8, seq=0 ttl=53 time=4.318 ms
84 bytes from 8.8.8.8, seq=1 ttl=53 time=4.421 ms
84 bytes from 8.8.8.8, seq=2 ttl=53 time=4.213 ms
84 bytes from 8.8.8.8, seq=3 ttl=53 time=4.031 ms
84 bytes from 8.8.8.8, seq=4 ttl=53 time=4.815 ms
84 bytes from 8.8.8.8, seq=5 ttl=53 time=3.960 ms
84 bytes from 8.8.8.8, seq=6 ttl=53 time=3.998 ms
84 bytes from 8.8.8.8, seq=7 ttl=53 time=4.327 ms
84 bytes from 8.8.8.8, seq=8 ttl=53 time=3.995 ms
84 bytes from 8.8.8.8, seq=9 ttl=53 time=4.683 ms
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.960/4.276/4.815/0.283 ms
ping 192.168.0.9 to 8.8.4.4: 84 byte packets
84 bytes from 8.8.4.4, seq=0 ttl=54 time=3.246 ms
84 bytes from 8.8.4.4, seq=1 ttl=54 time=3.746 ms
84 bytes from 8.8.4.4, seq=2 ttl=54 time=3.370 ms
84 bytes from 8.8.4.4, seq=3 ttl=54 time=3.285 ms
84 bytes from 8.8.4.4, seq=4 ttl=54 time=3.463 ms
84 bytes from 8.8.4.4, seq=5 ttl=54 time=3.314 ms
84 bytes from 8.8.4.4, seq=6 ttl=54 time=3.836 ms
84 bytes from 8.8.4.4, seq=7 ttl=54 time=3.174 ms
84 bytes from 8.8.4.4, seq=8 ttl=54 time=3.284 ms
84 bytes from 8.8.4.4, seq=9 ttl=54 time=3.718 ms
--- 8.8.4.4 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.174/3.443/3.836/0.224 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888: 104 byte packets
104 bytes from 2001:4860:4860::8888, seq=0 ttl=0 time=64.964 ms
104 bytes from 2001:4860:4860::8888, seq=1 ttl=0 time=64.570 ms
104 bytes from 2001:4860:4860::8888, seq=2 ttl=0 time=64.540 ms
104 bytes from 2001:4860:4860::8888, seq=3 ttl=0 time=65.294 ms
104 bytes from 2001:4860:4860::8888, seq=4 ttl=0 time=64.672 ms
104 bytes from 2001:4860:4860::8888, seq=5 ttl=0 time=65.249 ms
104 bytes from 2001:4860:4860::8888, seq=6 ttl=0 time=65.371 ms
104 bytes from 2001:4860:4860::8888, seq=7 ttl=0 time=65.215 ms
104 bytes from 2001:4860:4860::8888, seq=8 ttl=0 time=64.641 ms
104 bytes from 2001:4860:4860::8888, seq=9 ttl=0 time=65.535 ms
--- 2001:4860:4860::8888 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 64.540/65.005/65.535/0.353 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844: 104 byte packets
104 bytes from 2001:4860:4860::8844, seq=0 ttl=0 time=66.139 ms
104 bytes from 2001:4860:4860::8844, seq=1 ttl=0 time=65.642 ms
104 bytes from 2001:4860:4860::8844, seq=2 ttl=0 time=66.495 ms
104 bytes from 2001:4860:4860::8844, seq=3 ttl=0 time=66.542 ms
104 bytes from 2001:4860:4860::8844, seq=4 ttl=0 time=65.978 ms
104 bytes from 2001:4860:4860::8844, seq=5 ttl=0 time=66.279 ms
104 bytes from 2001:4860:4860::8844, seq=6 ttl=0 time=66.440 ms
104 bytes from 2001:4860:4860::8844, seq=7 ttl=0 time=66.343 ms
104 bytes from 2001:4860:4860::8844, seq=8 ttl=0 time=65.817 ms
104 bytes from 2001:4860:4860::8844, seq=9 ttl=0 time=66.205 ms
--- 2001:4860:4860::8844 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 65.642/66.188/66.542/0.282 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Confirming that I also cant reach the above address out of AS5466 (Eircom) in Ireland via AMS-IX Tracing route to rijksoverheid.nl [178.22.85.8] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 20 ms 20 ms 20 ms b-ras1.bbh.dublin.eircom.net [159.134.155.19] 3 20 ms 20 ms 20 ms ge-9-1-1.pe1.bbh.bbh-prp.eircom.net [86.43.246.2 21] 4 20 ms 20 ms 20 ms tenge-6-1-1.core1.srl.core.eircom.net [86.43.253 .121] 5 20 ms 19 ms 19 ms lag-1.core2.srl.core.eircom.net [86.43.252.62] 6 * * 21 ms 86.47.63.108 7 214 ms 174 ms 230 ms ams-ix.prolocation.net [80.249.210.128] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. On Tue, Feb 10, 2015 at 11:28 AM, Sajal Kayan via Outages < outages@outages.org> wrote:
"There are indications of a broken fiber cable connection, causing a massive network issue in the Amsterdam area." - https://twitter.com/StatusPltfrmIQ/status/565078428442198016
A dutch person told me he cant access many government sites and some news sites. An example site he cant access is http://www.rijksoverheid.nl
On Tue, Feb 10, 2015 at 5:04 PM, Nicholas Schmidt via Outages < outages@outages.org> wrote:
I too have been registering failures when attempting to use Googles public resolvers at 8.8.8.8 via the AMSIX exchange. This began at roughly 0200 GMT.
We have not attempted via transit or alternative Google DNS resolvers.
-Nick
On 2/10/15, 4:37 PM, "Aditya Patawari via Outages" <outages@outages.org> wrote:
I am seeing intermittent issue from EU, specifically from Amsterdam. US and Asian datacenters are fine for me. curl: (6) Could not resolve host: www.XYZ.com
Regards, Aditya Patawari http://blog.adityapatawari.com/ India
On Tue, Feb 10, 2015 at 2:41 PM, dikshie via Outages <outages@outages.org> wrote:
On Tue, Feb 10, 2015 at 5:58 PM, Wieger Bontekoe via Outages <outages@outages.org> wrote:
Hi all,
Is anybody else having issues with the Google DNS public servers?
From
the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results.
no problem in Japan.
; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12558
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21419 IN NS ns2.ja.net.
ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
;; Query time: 43 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @8.8.4.4 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25190
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21599 IN NS ns2.ja.net.
ox.ac.uk. 21599 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21599 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21599 IN NS dns1.ox.ac.uk.
;; Query time: 301 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8888 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34841
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 5821 IN NS dns1.ox.ac.uk.
ox.ac.uk. 5821 IN NS dns0.ox.ac.uk.
ox.ac.uk. 5821 IN NS dns2.ox.ac.uk.
ox.ac.uk. 5821 IN NS ns2.ja.net.
;; Query time: 67 msec
;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8844 ox.ac.uk NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36150
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk. IN NS
;; ANSWER SECTION:
ox.ac.uk. 21419 IN NS ns2.ja.net.
ox.ac.uk. 21419 IN NS dns2.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns0.ox.ac.uk.
ox.ac.uk. 21419 IN NS dns1.ox.ac.uk.
;; Query time: 72 msec
;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
traceroute from 192.168.0.9 to 8.8.8.8
1 192.168.0.1 0.691 ms [mtu: 1500]
2 121.106.107.1 2.943 ms [mtu: 1500]
3 125.48.119.34 1.452 ms [mtu: 1500]
4 118.152.208.134 2.283 ms [mtu: 1500]
5 118.152.210.45 3.166 ms [mtu: 1500]
6 106.162.175.153 3.487 ms [mtu: 1500]
7 59.128.5.86 2.968 ms [mtu: 1500]
8 72.14.204.58 48.487 ms [mtu: 1500]
9 72.14.237.70 48.530 ms [mtu: 1500]
10 66.249.95.109 3.489 ms [mtu: 1500]
11 8.8.8.8 6.759 ms [mtu: 1500]
traceroute from 192.168.0.9 to 8.8.4.4
1 192.168.0.1 0.648 ms [mtu: 1500]
2 121.106.107.1 1.987 ms [mtu: 1500]
3 125.48.119.34 2.616 ms [mtu: 1500]
4 118.152.208.134 1.720 ms [mtu: 1500]
5 111.86.159.109 3.594 ms [mtu: 1500]
6 106.162.175.161 3.249 ms [mtu: 1500]
7 59.128.5.94 2.328 ms [mtu: 1500]
8 72.14.204.58 45.635 ms [mtu: 1500]
9 72.14.236.215 3.090 ms [mtu: 1500]
10 72.14.239.165 3.717 ms [mtu: 1500]
11 8.8.4.4 2.895 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.709 ms [mtu: 1500]
2 240f:10:4000::1 3.340 ms [mtu: 1500]
3 2001:268:f203:4d1::1 1.437 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.254 ms [mtu: 1500]
5 2001:268:fa01:7fe::1 4.246 ms [mtu: 1500]
6 2001:268:fa00:ffcf::1 5.791 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.439 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.930 ms [mtu: 1500]
9 2001:4860::1:0:8f9a 3.978 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.586 ms [mtu: 1500]
11 2001:4860::8:0:73ad 61.583 ms [mtu: 1500]
12 2001:4860::2:0:b7 64.719 ms [mtu: 1500]
13 *
14 2001:4860:4860::8888 65.174 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.704 ms [mtu: 1500]
2 240f:10:4000::1 2.721 ms [mtu: 1500]
3 2001:268:f203:4d1::1 2.078 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.604 ms [mtu: 1500]
5 2001:268:fa01:7ff::1 3.682 ms [mtu: 1500]
6 2001:268:fa00:ffdf::1 2.755 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.403 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.550 ms [mtu: 1500]
9 2001:4860::1:0:6626 4.762 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.027 ms [mtu: 1500]
11 2001:4860::8:0:73ad 60.917 ms [mtu: 1500]
12 2001:4860::2:0:b7 65.229 ms [mtu: 1500]
13 *
14 2001:4860:4860::8844 64.426 ms [mtu: 1500]
ping 192.168.0.9 to 8.8.8.8: 84 byte packets
84 bytes from 8.8.8.8, seq=0 ttl=53 time=4.318 ms
84 bytes from 8.8.8.8, seq=1 ttl=53 time=4.421 ms
84 bytes from 8.8.8.8, seq=2 ttl=53 time=4.213 ms
84 bytes from 8.8.8.8, seq=3 ttl=53 time=4.031 ms
84 bytes from 8.8.8.8, seq=4 ttl=53 time=4.815 ms
84 bytes from 8.8.8.8, seq=5 ttl=53 time=3.960 ms
84 bytes from 8.8.8.8, seq=6 ttl=53 time=3.998 ms
84 bytes from 8.8.8.8, seq=7 ttl=53 time=4.327 ms
84 bytes from 8.8.8.8, seq=8 ttl=53 time=3.995 ms
84 bytes from 8.8.8.8, seq=9 ttl=53 time=4.683 ms
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.960/4.276/4.815/0.283 ms
ping 192.168.0.9 to 8.8.4.4: 84 byte packets
84 bytes from 8.8.4.4, seq=0 ttl=54 time=3.246 ms
84 bytes from 8.8.4.4, seq=1 ttl=54 time=3.746 ms
84 bytes from 8.8.4.4, seq=2 ttl=54 time=3.370 ms
84 bytes from 8.8.4.4, seq=3 ttl=54 time=3.285 ms
84 bytes from 8.8.4.4, seq=4 ttl=54 time=3.463 ms
84 bytes from 8.8.4.4, seq=5 ttl=54 time=3.314 ms
84 bytes from 8.8.4.4, seq=6 ttl=54 time=3.836 ms
84 bytes from 8.8.4.4, seq=7 ttl=54 time=3.174 ms
84 bytes from 8.8.4.4, seq=8 ttl=54 time=3.284 ms
84 bytes from 8.8.4.4, seq=9 ttl=54 time=3.718 ms
--- 8.8.4.4 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.174/3.443/3.836/0.224 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888: 104 byte packets
104 bytes from 2001:4860:4860::8888, seq=0 ttl=0 time=64.964 ms
104 bytes from 2001:4860:4860::8888, seq=1 ttl=0 time=64.570 ms
104 bytes from 2001:4860:4860::8888, seq=2 ttl=0 time=64.540 ms
104 bytes from 2001:4860:4860::8888, seq=3 ttl=0 time=65.294 ms
104 bytes from 2001:4860:4860::8888, seq=4 ttl=0 time=64.672 ms
104 bytes from 2001:4860:4860::8888, seq=5 ttl=0 time=65.249 ms
104 bytes from 2001:4860:4860::8888, seq=6 ttl=0 time=65.371 ms
104 bytes from 2001:4860:4860::8888, seq=7 ttl=0 time=65.215 ms
104 bytes from 2001:4860:4860::8888, seq=8 ttl=0 time=64.641 ms
104 bytes from 2001:4860:4860::8888, seq=9 ttl=0 time=65.535 ms
--- 2001:4860:4860::8888 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 64.540/65.005/65.535/0.353 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844: 104 byte packets
104 bytes from 2001:4860:4860::8844, seq=0 ttl=0 time=66.139 ms
104 bytes from 2001:4860:4860::8844, seq=1 ttl=0 time=65.642 ms
104 bytes from 2001:4860:4860::8844, seq=2 ttl=0 time=66.495 ms
104 bytes from 2001:4860:4860::8844, seq=3 ttl=0 time=66.542 ms
104 bytes from 2001:4860:4860::8844, seq=4 ttl=0 time=65.978 ms
104 bytes from 2001:4860:4860::8844, seq=5 ttl=0 time=66.279 ms
104 bytes from 2001:4860:4860::8844, seq=6 ttl=0 time=66.440 ms
104 bytes from 2001:4860:4860::8844, seq=7 ttl=0 time=66.343 ms
104 bytes from 2001:4860:4860::8844, seq=8 ttl=0 time=65.817 ms
104 bytes from 2001:4860:4860::8844, seq=9 ttl=0 time=66.205 ms
--- 2001:4860:4860::8844 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 65.642/66.188/66.542/0.282 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Yours, Jay Gannon Editor/Photographer The Factory
That twitter posting is gone, at least when I try to go to it. I also can’t reach www.rijksoverheid.nl <http://www.rijksoverheid.nl> . Frank From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Sajal Kayan via Outages Sent: Tuesday, February 10, 2015 5:28 AM To: Nicholas Schmidt Cc: outages@outages.org Subject: Re: [outages] Outages google DNS "There are indications of a broken fiber cable connection, causing a massive network issue in the Amsterdam area." - https://twitter.com/StatusPltfrmIQ/status/565078428442198016 A dutch person told me he cant access many government sites and some news sites. An example site he cant access is http://www.rijksoverheid.nl On Tue, Feb 10, 2015 at 5:04 PM, Nicholas Schmidt via Outages <outages@outages.org <mailto:outages@outages.org> > wrote: I too have been registering failures when attempting to use Googles public resolvers at 8.8.8.8 via the AMSIX exchange. This began at roughly 0200 GMT. We have not attempted via transit or alternative Google DNS resolvers. -Nick On 2/10/15, 4:37 PM, "Aditya Patawari via Outages" <outages@outages.org <mailto:outages@outages.org> > wrote:
I am seeing intermittent issue from EU, specifically from Amsterdam. US and Asian datacenters are fine for me. curl: (6) Could not resolve host: www.XYZ.com <http://www.XYZ.com>
Regards, Aditya Patawari http://blog.adityapatawari.com/ India
On Tue, Feb 10, 2015 at 2:41 PM, dikshie via Outages <outages@outages.org <mailto:outages@outages.org> > wrote:
On Tue, Feb 10, 2015 at 5:58 PM, Wieger Bontekoe via Outages <outages@outages.org <mailto:outages@outages.org> > wrote:
Hi all,
Is anybody else having issues with the Google DNS public servers? From the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results.
no problem in Japan.
; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 <http://8.8.8.8> ox.ac.uk <http://ox.ac.uk> NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12558
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk <http://ox.ac.uk> . IN NS
;; ANSWER SECTION:
ox.ac.uk <http://ox.ac.uk> . 21419 IN NS ns2.ja.net <http://ns2.ja.net> .
ox.ac.uk <http://ox.ac.uk> . 21419 IN NS dns2.ox.ac.uk <http://dns2.ox.ac.uk> .
ox.ac.uk <http://ox.ac.uk> . 21419 IN NS dns0.ox.ac.uk <http://dns0.ox.ac.uk> .
ox.ac.uk <http://ox.ac.uk> . 21419 IN NS dns1.ox.ac.uk <http://dns1.ox.ac.uk> .
;; Query time: 43 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @8.8.4.4 <http://8.8.4.4> ox.ac.uk <http://ox.ac.uk> NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25190
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk <http://ox.ac.uk> . IN NS
;; ANSWER SECTION:
ox.ac.uk <http://ox.ac.uk> . 21599 IN NS ns2.ja.net <http://ns2.ja.net> .
ox.ac.uk <http://ox.ac.uk> . 21599 IN NS dns0.ox.ac.uk <http://dns0.ox.ac.uk> .
ox.ac.uk <http://ox.ac.uk> . 21599 IN NS dns2.ox.ac.uk <http://dns2.ox.ac.uk> .
ox.ac.uk <http://ox.ac.uk> . 21599 IN NS dns1.ox.ac.uk <http://dns1.ox.ac.uk> .
;; Query time: 301 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8888 ox.ac.uk <http://ox.ac.uk> NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34841
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk <http://ox.ac.uk> . IN NS
;; ANSWER SECTION:
ox.ac.uk <http://ox.ac.uk> . 5821 IN NS dns1.ox.ac.uk <http://dns1.ox.ac.uk> .
ox.ac.uk <http://ox.ac.uk> . 5821 IN NS dns0.ox.ac.uk <http://dns0.ox.ac.uk> .
ox.ac.uk <http://ox.ac.uk> . 5821 IN NS dns2.ox.ac.uk <http://dns2.ox.ac.uk> .
ox.ac.uk <http://ox.ac.uk> . 5821 IN NS ns2.ja.net <http://ns2.ja.net> .
;; Query time: 67 msec
;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8844 ox.ac.uk <http://ox.ac.uk> NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36150
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ox.ac.uk <http://ox.ac.uk> . IN NS
;; ANSWER SECTION:
ox.ac.uk <http://ox.ac.uk> . 21419 IN NS ns2.ja.net <http://ns2.ja.net> .
ox.ac.uk <http://ox.ac.uk> . 21419 IN NS dns2.ox.ac.uk <http://dns2.ox.ac.uk> .
ox.ac.uk <http://ox.ac.uk> . 21419 IN NS dns0.ox.ac.uk <http://dns0.ox.ac.uk> .
ox.ac.uk <http://ox.ac.uk> . 21419 IN NS dns1.ox.ac.uk <http://dns1.ox.ac.uk> .
;; Query time: 72 msec
;; SERVER: 2001:4860:4860::8844#53(2001:4860:4860::8844)
;; WHEN: Tue Feb 10 18:09:43 2015
;; MSG SIZE rcvd: 107
traceroute from 192.168.0.9 to 8.8.8.8
1 192.168.0.1 0.691 ms [mtu: 1500]
2 121.106.107.1 2.943 ms [mtu: 1500]
3 125.48.119.34 1.452 ms [mtu: 1500]
4 118.152.208.134 2.283 ms [mtu: 1500]
5 118.152.210.45 3.166 ms [mtu: 1500]
6 106.162.175.153 3.487 ms [mtu: 1500]
7 59.128.5.86 2.968 ms [mtu: 1500]
8 72.14.204.58 48.487 ms [mtu: 1500]
9 72.14.237.70 48.530 ms [mtu: 1500]
10 66.249.95.109 3.489 ms [mtu: 1500]
11 8.8.8.8 6.759 ms [mtu: 1500]
traceroute from 192.168.0.9 to 8.8.4.4
1 192.168.0.1 0.648 ms [mtu: 1500]
2 121.106.107.1 1.987 ms [mtu: 1500]
3 125.48.119.34 2.616 ms [mtu: 1500]
4 118.152.208.134 1.720 ms [mtu: 1500]
5 111.86.159.109 3.594 ms [mtu: 1500]
6 106.162.175.161 3.249 ms [mtu: 1500]
7 59.128.5.94 2.328 ms [mtu: 1500]
8 72.14.204.58 45.635 ms [mtu: 1500]
9 72.14.236.215 3.090 ms [mtu: 1500]
10 72.14.239.165 3.717 ms [mtu: 1500]
11 8.8.4.4 2.895 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.709 ms [mtu: 1500]
2 240f:10:4000::1 3.340 ms [mtu: 1500]
3 2001:268:f203:4d1::1 1.437 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.254 ms [mtu: 1500]
5 2001:268:fa01:7fe::1 4.246 ms [mtu: 1500]
6 2001:268:fa00:ffcf::1 5.791 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.439 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.930 ms [mtu: 1500]
9 2001:4860::1:0:8f9a 3.978 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.586 ms [mtu: 1500]
11 2001:4860::8:0:73ad 61.583 ms [mtu: 1500]
12 2001:4860::2:0:b7 64.719 ms [mtu: 1500]
13 *
14 2001:4860:4860::8888 65.174 ms [mtu: 1500]
traceroute from 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844
1 240f:10:40c3:1:a612:42ff:fe8e:b90c 0.704 ms [mtu: 1500]
2 240f:10:4000::1 2.721 ms [mtu: 1500]
3 2001:268:f203:4d1::1 2.078 ms [mtu: 1500]
4 2001:268:f203:1ff::1 2.604 ms [mtu: 1500]
5 2001:268:fa01:7ff::1 3.682 ms [mtu: 1500]
6 2001:268:fa00:ffdf::1 2.755 ms [mtu: 1500]
7 2001:268:fb02:9e::2 3.403 ms [mtu: 1500]
8 2001:4860:1:1:0:9d4:: 3.550 ms [mtu: 1500]
9 2001:4860::1:0:6626 4.762 ms [mtu: 1500]
10 2001:4860::1:0:6302 6.027 ms [mtu: 1500]
11 2001:4860::8:0:73ad 60.917 ms [mtu: 1500]
12 2001:4860::2:0:b7 65.229 ms [mtu: 1500]
13 *
14 2001:4860:4860::8844 64.426 ms [mtu: 1500]
ping 192.168.0.9 to 8.8.8.8 <http://8.8.8.8> : 84 byte packets
84 bytes from 8.8.8.8, seq=0 ttl=53 time=4.318 ms
84 bytes from 8.8.8.8, seq=1 ttl=53 time=4.421 ms
84 bytes from 8.8.8.8, seq=2 ttl=53 time=4.213 ms
84 bytes from 8.8.8.8, seq=3 ttl=53 time=4.031 ms
84 bytes from 8.8.8.8, seq=4 ttl=53 time=4.815 ms
84 bytes from 8.8.8.8, seq=5 ttl=53 time=3.960 ms
84 bytes from 8.8.8.8, seq=6 ttl=53 time=3.998 ms
84 bytes from 8.8.8.8, seq=7 ttl=53 time=4.327 ms
84 bytes from 8.8.8.8, seq=8 ttl=53 time=3.995 ms
84 bytes from 8.8.8.8, seq=9 ttl=53 time=4.683 ms
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.960/4.276/4.815/0.283 ms
ping 192.168.0.9 to 8.8.4.4 <http://8.8.4.4> : 84 byte packets
84 bytes from 8.8.4.4, seq=0 ttl=54 time=3.246 ms
84 bytes from 8.8.4.4, seq=1 ttl=54 time=3.746 ms
84 bytes from 8.8.4.4, seq=2 ttl=54 time=3.370 ms
84 bytes from 8.8.4.4, seq=3 ttl=54 time=3.285 ms
84 bytes from 8.8.4.4, seq=4 ttl=54 time=3.463 ms
84 bytes from 8.8.4.4, seq=5 ttl=54 time=3.314 ms
84 bytes from 8.8.4.4, seq=6 ttl=54 time=3.836 ms
84 bytes from 8.8.4.4, seq=7 ttl=54 time=3.174 ms
84 bytes from 8.8.4.4, seq=8 ttl=54 time=3.284 ms
84 bytes from 8.8.4.4, seq=9 ttl=54 time=3.718 ms
--- 8.8.4.4 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.174/3.443/3.836/0.224 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8888: 104 byte packets
104 bytes from 2001:4860:4860::8888, seq=0 ttl=0 time=64.964 ms
104 bytes from 2001:4860:4860::8888, seq=1 ttl=0 time=64.570 ms
104 bytes from 2001:4860:4860::8888, seq=2 ttl=0 time=64.540 ms
104 bytes from 2001:4860:4860::8888, seq=3 ttl=0 time=65.294 ms
104 bytes from 2001:4860:4860::8888, seq=4 ttl=0 time=64.672 ms
104 bytes from 2001:4860:4860::8888, seq=5 ttl=0 time=65.249 ms
104 bytes from 2001:4860:4860::8888, seq=6 ttl=0 time=65.371 ms
104 bytes from 2001:4860:4860::8888, seq=7 ttl=0 time=65.215 ms
104 bytes from 2001:4860:4860::8888, seq=8 ttl=0 time=64.641 ms
104 bytes from 2001:4860:4860::8888, seq=9 ttl=0 time=65.535 ms
--- 2001:4860:4860::8888 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 64.540/65.005/65.535/0.353 ms
ping 240f:10:40c3:1:646b:c3a2:fee4:3ee0 to 2001:4860:4860::8844: 104 byte packets
104 bytes from 2001:4860:4860::8844, seq=0 ttl=0 time=66.139 ms
104 bytes from 2001:4860:4860::8844, seq=1 ttl=0 time=65.642 ms
104 bytes from 2001:4860:4860::8844, seq=2 ttl=0 time=66.495 ms
104 bytes from 2001:4860:4860::8844, seq=3 ttl=0 time=66.542 ms
104 bytes from 2001:4860:4860::8844, seq=4 ttl=0 time=65.978 ms
104 bytes from 2001:4860:4860::8844, seq=5 ttl=0 time=66.279 ms
104 bytes from 2001:4860:4860::8844, seq=6 ttl=0 time=66.440 ms
104 bytes from 2001:4860:4860::8844, seq=7 ttl=0 time=66.343 ms
104 bytes from 2001:4860:4860::8844, seq=8 ttl=0 time=65.817 ms
104 bytes from 2001:4860:4860::8844, seq=9 ttl=0 time=66.205 ms
--- 2001:4860:4860::8844 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 65.642/66.188/66.542/0.282 ms
_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
We're on the AMSIX and not seeing any issue. D. $ dig @8.8.8.8 google.com ; <<>> DiG 9.7.3 <<>> @8.8.8.8 google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8314 ;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com. IN A ;; ANSWER SECTION: google.com. 299 IN A 173.194.65.113 google.com. 299 IN A 173.194.65.100 google.com. 299 IN A 173.194.65.139 google.com. 299 IN A 173.194.65.101 google.com. 299 IN A 173.194.65.138 google.com. 299 IN A 173.194.65.102 ;; Query time: 36 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Tue Feb 10 13:41:18 2015 ;; MSG SIZE rcvd: 124 Oplerno is built upon empowering faculty and students -- Daniël W. Crompton <daniel.crompton@gmail.com> <http://specialbrands.net/> <http://specialbrands.net/> http://specialbrands.net/ <http://twitter.com/webhat> <http://www.facebook.com/webhat> <http://plancast.com/webhat> <http://www.linkedin.com/in/redhat> FAB8 4200 587A 6BB2 9D64 9DB9 D9D8 7346 D4F7 B651 On 10 February 2015 at 09:58, Wieger Bontekoe via Outages < outages@outages.org> wrote:
Hi all,
Is anybody else having issues with the Google DNS public servers? From the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results.
Met vriendelijke groet / with kind regards / Atenciosamente,
*Wieger Bontekoe* +31 (0)20 760 4909 | w.bontekoe@wipabv.nl
[image: WIPA Nederland B.V.] <http://www.wipa.nl/>
[image: Facebook] <https://www.facebook.com/WIPABV> [image: Twitter] <https://www.twitter.com/WIPABV> [image: Skype]
*Office the Netherlands:* Paul van Vlissingenstraat 16 1096 BK Amsterdam
*Office Brasil:* Av. Eng. Antônio de Góes 60 - 7º e 14º Boa Viagem, Recife, Brasil
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. WIPA is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
Op al onze leveringen zijn onze algemene voorwaarden van toepassing. Wanneer u iets bij ons besteld gaat u met deze voorwaarden akkoord. Alle prijzen zijn exclusief BTW en onder voorbehoud van eventuele wijzigingen en/of typ- en schrijfouten.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
It looks like Google DNS is fine, but that 'prolocation.net' is having some kind of peering issue that leads to trouble for 'rijksoverheid.nl'. Both XS4ALL and TransIP stop at 'openpeering.prolocation.net' on what looks to be NIKHEF; == $ traceroute rijksoverheid.nl traceroute to rijksoverheid.nl (178.22.85.11), 30 hops max, 60 byte packets 1 v312.router1.dcga.ams.transip.net (37.97.128.220) 0.221 ms 0.196 ms 0.268 ms 2 80.249.208.189 (80.249.208.189) 3.417 ms 3.369 ms 3.272 ms 3 nikhef.openpeering.nl (82.150.154.25) 6.258 ms 6.206 ms 6.124 ms 4 openpeering.prolocation.net (82.150.158.187) 2.981 ms 2.915 ms 2.866 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * == And the same from DigitalOcean's AMS2 location runs into issues on the NL-IX at Telecity; $ traceroute rijksoverheid.nl traceroute to rijksoverheid.nl (178.22.85.9), 30 hops max, 60 byte packets 1 95.85.52.254 (95.85.52.254) 7.371 ms 95.85.52.253 (95.85.52.253) 0.312 ms 0.295 ms 2 95.85.0.229 (95.85.0.229) 0.206 ms 95.85.0.241 (95.85.0.241) 0.254 ms 0.236 ms 3 95.85.0.250 (95.85.0.250) 0.266 ms 0.249 ms prolocation.telecity2.nl-ix.net (193.239.116.205) 0.865 ms 4 * prolocation.telecity2.nl-ix.net (193.239.116.205) 0.877 ms * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * == Perhaps those who are seeing trouble with Google DNS are somehow running into this, or it was a different, transient issue that has since been resolved? Or I am simply getting a direct peering to '8.8.8.8' from the locations I am testing from, bypassing the trouble area altogether. Mvg, Joni -- On 10 Feb 2015, at 14:43, Daniël W. Crompton via Outages <outages@outages.org> wrote:
We're on the AMSIX and not seeing any issue.
D.
[snip]
On 10 February 2015 at 09:58, Wieger Bontekoe via Outages <outages@outages.org> wrote: Hi all,
Is anybody else having issues with the Google DNS public servers? From the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results.
Met vriendelijke groet / with kind regards / Atenciosamente,
Wieger Bontekoe +31 (0)20 760 4909 | w.bontekoe@wipabv.nl
I see similar issues from the Netherlands. Here is a graph of the last 24 hours http://i.imgur.com/8NinbFO.png On Tue, Feb 10, 2015 at 8:43 AM, Daniël W. Crompton <outages@outages.org> wrote:
We're on the AMSIX and not seeing any issue.
D.
$ dig @8.8.8.8 google.com
; <<>> DiG 9.7.3 <<>> @8.8.8.8 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8314
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 299 IN A 173.194.65.113
google.com. 299 IN A 173.194.65.100
google.com. 299 IN A 173.194.65.139
google.com. 299 IN A 173.194.65.101
google.com. 299 IN A 173.194.65.138
google.com. 299 IN A 173.194.65.102
;; Query time: 36 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Feb 10 13:41:18 2015
;; MSG SIZE rcvd: 124
Oplerno is built upon empowering faculty and students
-- Daniël W. Crompton <daniel.crompton@gmail.com>
<http://specialbrands.net/> http://specialbrands.net/
<http://twitter.com/webhat> <http://www.facebook.com/webhat> <http://plancast.com/webhat> <http://www.linkedin.com/in/redhat> FAB8 4200 587A 6BB2 9D64 9DB9 D9D8 7346 D4F7 B651
On 10 February 2015 at 09:58, Wieger Bontekoe via Outages < outages@outages.org> wrote:
Hi all,
Is anybody else having issues with the Google DNS public servers? From the Amsterdam region (specifically using the Amsterdam Internet Exchange or other peering platforms) Google DNS is unresponsive. Several other providers here see the same results.
Met vriendelijke groet / with kind regards / Atenciosamente,
*Wieger Bontekoe* +31 (0)20 760 4909 | w.bontekoe@wipabv.nl
[image: WIPA Nederland B.V.] <http://www.wipa.nl/>
[image: Facebook] <https://www.facebook.com/WIPABV> [image: Twitter] <https://www.twitter.com/WIPABV> [image: Skype]
*Office the Netherlands:* Paul van Vlissingenstraat 16 1096 BK Amsterdam
*Office Brasil:* Av. Eng. Antônio de Góes 60 - 7º e 14º Boa Viagem, Recife, Brasil
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. WIPA is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
Op al onze leveringen zijn onze algemene voorwaarden van toepassing. Wanneer u iets bij ons besteld gaat u met deze voorwaarden akkoord. Alle prijzen zijn exclusief BTW en onder voorbehoud van eventuele wijzigingen en/of typ- en schrijfouten.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (10)
-
Aditya Patawari -
Daniël W. Crompton -
dikshie -
DTNX Postmaster -
Frank Bulk -
Jay Gannon -
Justin -
Nicholas Schmidt -
Sajal Kayan -
Wieger Bontekoe