% ping whatsapp.com
ping: whatsapp.com: Name or service not known
% ping web.whatsapp.com
ping: web.whatsapp.com: Name or service not known
% ping facebook.com
ping: facebook.com: Name or service not known
% ping instagram.com
PING instagram.com (31.13.65.174) 56(84) bytes of data.
64 bytes from 31.13.65.174 (31.13.65.174): icmp_seq=1 ttl=53 time=110 msFacebook-owned sites were down
31–40 of 1001 posts
Re: Facebook-owned sites were down
#32good
Re: Facebook-owned sites were down
#33Hopefully permanently.
Yeah let's keep it that way.
Re: Facebook-owned sites were down
#34Looks like the routes to their hosted nameservers are down, e.g. A.NS.FACEBOOK.COM
Re: Facebook-owned sites were down
#35Oh no...
Anyway...
Re: Facebook-owned sites were down
#36For Facebook and WhatsApp it looks like a DNS issue, name resolution fails with SERVFAIL:
$ dig facebook.com
; > DiG 9.16.21 > facebook.com
;; global options: +cmd
;; Got answer:
;; ->>HEADERRe: Facebook-owned sites were down
#37Nothing of value was lost
This cannot be said enough.
Re: Facebook-owned sites were down
#38good ridance
Re: Facebook-owned sites were down
#39For Facebook and WhatsApp it looks like a DNS issue, name resolution fails with SERVFAIL: $ dig facebook.com ; > DiG 9.16.21 > facebook.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER
Maybe they tried everything else before that.
At first it was working but they couldn't serve responses: https://i.imgur.com/UaCtOiX.png
Notice the "2020"
Re: Facebook-owned sites were down
#40Just wondering - would the engineer who made the mistake be fired?