Facebook-owned sites were down
211–220 of 1001 posts
Great time to take a break from Facebook and Instagram. Use Telegram instead of WhatsApp
Re: Facebook-owned sites were down
#212Re: Facebook-owned sites were down
#213Is it just me or HN also feels kinda laggy?
With the Facebook properties down, the rest of the internet will have a significant increase in usage.
Plus I don't know about you, but I came to HN just now specifically to check if there was any insight into why it was down! The thundering herd just arrived :)
Re: Facebook-owned sites were down
#214Oculus is also down
Indeed. People seem to forget that when Facebook goes down, it's not just your feed of depressing posts, photos and messages that go away, but also the entire Oculus VR platform, since they demanded a FB account to use Quest headsets.
Re: Facebook-owned sites were down
#215Let's hope it's permanent.
Of all the big tech companies Facebook is the only one where it can completely disappear overnight and my life would be completely unaffected (or possibly improved by not having to explain to people I don't use facebook, please email or text me your invitations rather than use messenger). If Google, Amazon, Netflix, Apple disappeared the story would be completely different.
Re: Facebook-owned sites were down
#216Re: Facebook-owned sites were down
#217Re: Facebook-owned sites were down
#218The joy that people are getting from this is quite shitty. I hate social media but there are people earning a living working for these companies. Like others have pointed out, businesses and neighborhood watches rely on tech like this.
At some point we've all had sites/apps go down, in a situation like that the last thing you want is people enjoying it.
The lack of empathy in this thread is telling.
Re: Facebook-owned sites were down
#219Re: Facebook-owned sites were down
#220For 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
Is this related in any way to what happened to Slack recently in their DNS?
So far the pattern isn't the same. Slack published a DNSSEC record that got cached and then deleted it, which broke clients that tried to validate DNSSEC for slack.com. But in this case, the records are just completely gone. As if "facebook.com", "instagram.com", et al just didn't exist.