
Anyone seeing issues reaching Cloudflare-hosted sites in the Pacific Northwest, specifically on IPv4? Maybe related to Frank's earlier note re: maintenance and Cloudflare losing their AAAA? Or maybe https://www.cloudflarestatus.com/incidents/h2rgfrxtwk69 (which just got posted after I finished writing the rest below...)? One sample site (http://tecadmin.net/) can be retrieved over v6 but v4 fails to connect, while another gives a 503 on v6 while also failing to connect on v4: hslabbert@bamboo:~$ wget http://tecadmin.net --2015-11-10 21:52:49-- http://tecadmin.net/ Resolving tecadmin.net (tecadmin.net)... 2400:cb00:2048:1::681b:bcd9, 2400:cb00:2048:1::681b:bdd9, 104.27.189.217, ... Connecting to tecadmin.net (tecadmin.net)|2400:cb00:2048:1::681b:bcd9|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘index.html’ [ <=> ] 91,024 --.-K/s in 0.02s 2015-11-10 21:52:49 (3.69 MB/s) - ‘index.html’ saved [91024] hslabbert@bamboo:~$ wget -4 http://tecadmin.net --2015-11-10 21:53:02-- http://tecadmin.net/ Resolving tecadmin.net (tecadmin.net)... 104.27.189.217, 104.27.188.217 Connecting to tecadmin.net (tecadmin.net)|104.27.189.217|:80... failed: Connection timed out. Connecting to tecadmin.net (tecadmin.net)|104.27.188.217|:80... failed: Connection timed out. Retrying. --2015-11-10 21:57:18-- (try: 2) http://tecadmin.net/ Connecting to tecadmin.net (tecadmin.net)|104.27.189.217|:80... failed: Connection timed out. Connecting to tecadmin.net (tecadmin.net)|104.27.188.217|:80... failed: Connection timed out. Retrying. --2015-11-10 22:01:34-- (try: 3) http://tecadmin.net/ Connecting to tecadmin.net (tecadmin.net)|104.27.189.217|:80... As the wgets also show, host is resolving as: $ dig tecadmin.net A +noadditional +noauthority ; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> tecadmin.net A +noadditional +noauthority ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19744 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 13, ADDITIONAL: 16 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;tecadmin.net. IN A ;; ANSWER SECTION: tecadmin.net. 248 IN A 104.27.188.217 tecadmin.net. 248 IN A 104.27.189.217 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Nov 10 21:58:40 PST 2015 ;; MSG SIZE rcvd: 558 $ dig tecadmin.net AAAA +noadditional +noauthority ; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> tecadmin.net AAAA +noadditional +noauthority ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2868 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 13, ADDITIONAL: 16 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;tecadmin.net. IN AAAA ;; ANSWER SECTION: tecadmin.net. 300 IN AAAA 2400:cb00:2048:1::681b:bdd9 tecadmin.net. 300 IN AAAA 2400:cb00:2048:1::681b:bcd9 ;; Query time: 6 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Nov 10 21:59:28 PST 2015 ;; MSG SIZE rcvd: 582 Currently reaching it through VANIX, though the route is less than 6 hours old with no recent flaps on the peer. Traceroutes die after the VANIX peer. -- Hugo

Seems to have come right at ~09:24 AM PST this morning. Any word from Cloudflare? Was I alone in seeing this? -- Hugo On Tue 2015-Nov-10 22:15:23 -0800, Hugo Slabbert <hslabbert@stargate.ca> wrote:
Anyone seeing issues reaching Cloudflare-hosted sites in the Pacific Northwest, specifically on IPv4?
Maybe related to Frank's earlier note re: maintenance and Cloudflare losing their AAAA? Or maybe https://www.cloudflarestatus.com/incidents/h2rgfrxtwk69 (which just got posted after I finished writing the rest below...)?
One sample site (http://tecadmin.net/) can be retrieved over v6 but v4 fails to connect, while another gives a 503 on v6 while also failing to connect on v4:
#snipped
participants (1)
-
Hugo Slabbert