I keep trying to submit to HN but I keep getting an error. What's wrong with the internet? FaceBook is down. My friend from Slovenia is having trouble with discord. It eats his messages. I can't load photos from my friend in telegram and the messages take a relatively long time - multiple seconds! - to get received. TrackMania players have talked about having input lag. ycombinator is really slow and reports an error…
Facebook-owned sites were down
661–670 of 1001 posts
Re: Facebook-owned sites were down
#662Earlier quoted context omitted.
And there his account went poof, thanks for archiving.
They were quoted on multiple news sites including Ars Technica. I would imagine they were not authorized to post that information. I hope they don't lose their job. Shareholders and other business leaders I'm sure are much happier reporting this as a series of unfortunate technical failures (which I'm sure is part of it) rather than a company-wide organizational failure. The fact they can't physically badge in the pe…
Re: Facebook-owned sites were down
#663Interestingly, their .onion site¹ is also down. https://en.wikipedia.org/wiki/Facebook_onion_address
Re: Facebook-owned sites were down
#664Re: Facebook-owned sites were down
#665Ignore.
Re: Facebook-owned sites were down
#666Earlier quoted context omitted.
My suspicion is that since a lot of internal comms runs through the FB domain and since everyone is still WFH, then its probably a massive issue just to get people talking to each other to solve the problem.
time to start working at your mfing desk again, johnson
Re: Facebook-owned sites were down
#667Earlier quoted context omitted.
Yeah the patch to fix BGP to reach the DNS is sent by email to @facebook.com. Ooops no DNS to resolve the MX records to send the patch to fix the BGP routers.
Seriously? Is that how it works?
Re: Facebook-owned sites were down
#668Re: Facebook-owned sites were down
#669There's still no connectivity to Facebook's DNS servers: > traceroute a.ns.facebook.com traceroute to a.ns.facebook.com (129.134.30.12), 30 hops max, 60 byte packets 1 dsldevice.attlocal.net (192.168.1.254) 0.484 ms 0.474 ms 0.422 ms 2 107-131-124-1.lightspeed.sntcca.sbcglobal.net (107.131.124.1) 1.592 ms 1.657 ms 1.607 ms 3 71.148.149.196 (71.148.149.196) 1.676 ms 1.697 ms 1.705 ms 4 12.242.105.110 (12.242.105.110)…
My suspicion is that since a lot of internal comms runs through the FB domain and since everyone is still WFH, then its probably a massive issue just to get people talking to each other to solve the problem.
I guess good decentralized public communication services could solve those issues for everybody.