Is it just me or HN also feels kinda laggy?
Some internet backbone provider is probably down itself.
Facebook-owned sites were down
241–250 of 1001 posts
Re: Facebook-owned sites were down
#242Unsurprisingly, Oculus is down as well, as are most services for the VR headset. So that's 4 major properties right now.
Re: Facebook-owned sites were down
#243Somebody published vogon poetry and pictures and the internet routed around the damage...
Re: Facebook-owned sites were down
#244Doesn't seem too clever that Facebook's NS servers are a.ns.facebook.com, b.ns.facebook.com etc. IIRC that kind of setup requires some glue records.
If you mean because the name servers are in the same zone, this is very common. When an NS is returned for a zone, you also get an “additional” A and AAAA to resolve the NS name. It’s called glue . dig NS example.com ; ANSWER example.com. NS ns1.example.com. ; ADDITIONAL ns1.example.com. A 1.2.3.4 Edit: I didn’t see your glue comment when I wrote this.
Cheers, I'd edited my post.
Thought the common wisdom nowadays was to use nameservers on different TLDs and sub-labels for the best resilience.
/added, they seem to have glue records so I'd assume it's the nameservers themselves having issues.
$ dig NS @g.gtld-servers.net. a.ns.facebook.com
;; AUTHORITY SECTION:
facebook.com. 172800 IN NS a.ns.facebook.com.
facebook.com. 172800 IN NS b.ns.facebook.com.
facebook.com. 172800 IN NS
c.ns.facebook.com.
facebook.com. 172800 IN NS d.ns.facebook.com.
;; ADDITIONAL SECTION:
a.ns.facebook.com. 172800 IN A 129.134.30.12
a.ns.facebook.com. 172800 IN AAAA 2a03:2880:f0fc:c:face:b00c:0:35
b.ns.facebook.com. 172800 IN A 129.134.31.12
b.ns.facebook.com. 172800 IN AAAA 2a03:2880:f0fd:c:face:b00c:0:35
c.ns.facebook.com. 172800 IN A 185.89.218.12
c.ns.facebook.com. 172800 IN AAAA 2a03:2880:f1fc:c:face:b00c:0:35
d.ns.facebook.com. 172800 IN A 185.89.219.12
d.ns.facebook.com. 172800 IN AAAA 2a03:2880:f1fd:c:face:b00c:0:35
Re: Facebook-owned sites were down
#245Checked isitdownrightnow.com and said Netflix was also down. Any chance these are related?
Netflix is up
Re: Facebook-owned sites were down
#246rich people serve their revenge for pandora papers
Re: Facebook-owned sites were down
#247What are some of the possible scnarios beyond the DNS issue suggested? (and might it be an attack?)
This is what i came to comments for.
Unfortunately, we have literally dozens of comments that amount to nothing more than schadenfreude, and another handful of non-FANG employees speculating how one of the largest internet operations in existence could improve their game (lol)
Re: Facebook-owned sites were down
#248Suspecting it might be related to the recent letsencrypt cert authority expiring? Was just debugging an issue earlier today and just couldn't help wondering how much of the internet is secured by letsencrypt. All of the static hosts providing free SSL: vercel, netlify, render, firebase hosting, github pages, heroku etc. ... It does work on modern browsers and devices but goes terribly broken on a lot of old devices.
Obviously not possible to check right now to provide proof, but I feel quite confident in saying that Facebook does not use Let's Encrypt. It's also clearly not an SSL issue.
Re: Facebook-owned sites were down
#249Earlier quoted context omitted.
https://downdetector.com/ seems to be working for me at least.
It's amusing that the top 3 trending reports are the FB sites that are down, and then the mobile carriers themselves, presumably because when FB doesn't load they assume it's their mobile network's fault. People really do think FB is the internet
> People really do think FB is the internet
It's the AOL of 2021
Re: Facebook-owned sites were down
#250This is taking a longer time than expected for a company like Facebook - must be serious where a rollback isn't possible or trivial.