[HN Gopher] Tell HN: 1.1.1.1 Appears to Be Down
___________________________________________________________________
Tell HN: 1.1.1.1 Appears to Be Down
Cloudflare's DNS server doesn't appear to be working.
6:03PM storm ~ % ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84)
bytes of data. ^C --- 1.1.1.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3103ms
Author : Wingy
Score : 104 points
Date : 2025-07-14 22:04 UTC (56 minutes ago)
| nagisa wrote:
| Can confirm its down here too.
|
| 1.0.0.1 is also down.
| EtienneK wrote:
| Yup, same here (Europe). Opened up HN to confirm. Thanks :)
| SCHiM wrote:
| It's down. Tested from two servers, 8.8.8.8 and others are up.
| msvcredist2022 wrote:
| Confirmed down in the PNW & Virginia (east1) as well.
| pablonara wrote:
| Down in iowa and montreal too
| tom1337 wrote:
| and here (EU West) I am debugging why my internet is not working
| and using ping 1.1.1.1 as a check
| zubspace wrote:
| Same here! Restarted my router and pi hole twice. Now i feel
| stupid.
| PaulHoule wrote:
| No shit. My "internet" just went down and I switched over to
| 8.8.8.8 and got back up.
| strongpigeon wrote:
| Same. I assumed it was my ISP as it had some hiccups lately,
| but when I saw that 8.8.8.8 was responding to ICMPs I suspected
| 1.1.1.1 was down.
| explodingwaffle wrote:
| I tested with 1.1.1.1 first, didn't get anything, and gave up
| for the night. Maybe I should put a different provider as DNS
| backup? (any DNS gurus to say that that's a bad idea?)
| sashk wrote:
| their status page shows there is no problems with it.
| thecosas wrote:
| Looks like they have it listed as of a few minutes ago:
| https://www.cloudflarestatus.com/incidents/28r0vbbxsh8f
| homero wrote:
| It's dead here
| durakot wrote:
| Looks to be down globally... another friendly reminder of our
| overdependence on a few services (and how many servers are
| configured to use 1.1.1.1 for DNS queries?)
| thekid314 wrote:
| In NYC it appears down for me too. MacBook-Pro ~ % ping 1.1.1.1
| PING 1.1.1.1 (1.1.1.1): 56 data bytes Request timeout for
| icmp_seq 0
| hunkins wrote:
| Yep, timeouts on my end.
|
| PING 1.1.1.1 (1.1.1.1): 56 data bytes Request timeout for
| icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for
| icmp_seq 2 Request timeout for icmp_seq 3 ^C --- 1.1.1.1 ping
| statistics --- 5 packets transmitted, 0 packets received, 100.0%
| packet loss
| armitron wrote:
| Don't use Cloudflare, they've done enough damage to the Internet
| with their centralized bs without you needing to further reward
| them by handing over all your DNS data.
| Beaving wrote:
| https://x.com/nadeu/status/1944881376366616749
| fastily wrote:
| the curse of bgp strikes again
| tom1337 wrote:
| https://www.cloudflarestatus.com/incidents/28r0vbbxsh8f
| alecsm wrote:
| It's down in Spain too.
| pwr22 wrote:
| Down for me from UK
| nodesocket wrote:
| I just got 45 e-mail notifications from Uptime Kuma and knew
| something was afoot.
| SuperSandro2000 wrote:
| near total global outage according to
| https://atlas.ripe.net/measurements/117762218/
| gerdesj wrote:
| DNS shouldn't be tested with ICMP. Try dig or nslookup instead.
| ICMP echo request/reply may help to decide reachability and
| nothing more.
|
| This is a reasonable test of the DNS service on 1.1.1.1:
| $ dig @1.1.1.1 www.cloudflare.com A ; <<>> DiG
| 9.20.4-3ubuntu1.1-Ubuntu <<>> @1.1.1.1 www.cloudflare.com A
| ; (1 server found) ;; global options: +cmd ;; Got
| answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:
| 34112 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY:
| 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS:
| version: 0, flags:; udp: 1232 ;; QUESTION SECTION:
| ;www.cloudflare.com. IN A ;; ANSWER
| SECTION: www.cloudflare.com. 36 IN A
| 104.16.123.96 www.cloudflare.com. 36 IN A
| 104.16.124.96 ;; Query time: 39 msec ;; SERVER:
| 1.1.1.1#53(1.1.1.1) (UDP) ;; WHEN: Mon Jul 14 23:32:57 BST
| 2025 ;; MSG SIZE rcvd: 79
|
| [EDIT]: $ ping 1.1.1.1 PING 1.1.1.1
| (1.1.1.1) 56(84) bytes of data. From 141.101.70.116
| icmp_seq=1 Time to live exceeded 64 bytes from 1.1.1.1:
| icmp_seq=2 ttl=50 time=126 ms
|
| So ping fails a bit (and then works - firewall) but DNS works.
|
| The service required is DNS not ping. Test the service.
| landofyoshi wrote:
| Well, typically 1.1.1.1 responds to pings. So it not responding
| is an indication that it's no longer working.
| captainkrtek wrote:
| Or that it started filtering ICMP. If DNS works then it's
| doing its job
| gerdesj wrote:
| ... or a change of policy, funky firewall or whatever.
|
| It does seem to be responding to ping again and since my edit
| above, the first packet is being responded to so I suspect a
| NOC is having a fun old time somewhere.
|
| You do need to test the service properly. I do this malarky
| for a living 8) I'm ever so popular with kiddies and their
| gaming related fixation with ping times ...
| forbiddenlake wrote:
| This is all true, but DNS was also down.
|
| Signed, someone who was using 1.1.1.1 as their DNS server and
| hadn't configured a fallback
| gerdesj wrote:
| As a punishment: Compile and install ISC BIND from source and
| configure it 8)
|
| Many home routers can resolve starting from root or if you
| must then: 1.1.1.1, 8.8.8.8, 8.8.4.4 will get you started.
| You might consider 9.9.9.9 and there are quite a few others.
|
| I never, ever, ever, recommend using ISP provided DNS unless
| you know how they are configured. The anycast jobbies at
| least publish a policy of some sort.
| indigodaddy wrote:
| By using ping or MTR, they are testing general connectivity to
| an endpoint, doesn't matter what service is in play. For
| example, if you are getting significant packet loss on the
| endpoint itself in the output of an MTR, then that IS
| indicative of a network/connectivity problem, somewhere along
| the route (could still be an endpoint issue but definitely not
| always). The service in question doesn't matter much at that
| point. Whether the service itself is healthy or not, you are
| still troubleshooting the overarching issue presented by the
| bad ping/MTR.
| DoctorOW wrote:
| I recently switched from Cloudflare to ControlD and it was
| perfect timing to miss this!
| SuperSandro2000 wrote:
| hehe https://radar.cloudflare.com/routing/anomalies/hijack-107469
|
| their bgp monitoring found it :)
| madisp wrote:
| modern state of status pages makes me sad :( You were a good 10
| minutes quicker to note the issue than Cloudflare's status page
| was
| guluarte wrote:
| raise up chads using their own custom DNS resolver with 10+
| upstream providers
| nh43215rgb wrote:
| I wonder how uptime ratio of 1.1.1.1 is against 8.8.8.8
|
| Maybe there is noticeable difference?
| indigodaddy wrote:
| 10-15 minutes ago was getting intermittent TTL exceeded errors
| when pinging 1.1.1.1. Seems clean now and seem to be resolving ok
| now
| gcau wrote:
| The cloudflare status page had nothing reported, so I just
| assumed its some issue elsewhere (and the HN post didn't exist
| yet), if it wasn't for HN I'd probably be ordering a new router
| and ripping apart all my network settings and complaining to my
| ISP.
___________________________________________________________________
(page generated 2025-07-14 23:01 UTC)