Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Facebook-owned sites were down

facebook.com

Post reply on HN
Print view View original

671–680 of 1001 posts

Re: Facebook-owned sites were down

#671

Post by yk »

rocho wrote: post #194
elboru wrote: post #169

Is it just me or HN also feels kinda laggy?

I can confirm, HN, GitHub and Slack are very slow for me as well. Google is very fast, on the other hand.

People either have to work, creating load on GitHub, or waste their time elsewhere, creating load on HN and Slack.

Re: Facebook-owned sites were down

#672

Post by kiernanmcgowan »

secondcoming wrote: post #656
kiernanmcgowan wrote: post #643

Earlier 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.

Unlikely, PagerDuty was invented for this kind of thing

Oh I'm sure everyone knows whats wrong, but how am I supposed to send an email, find a coworkers phone number, get the crisis team on video chat etc etc if all of those connections rely on the facebook domain existing?

Re: Facebook-owned sites were down

#674

Post by htrp »

In the post-mortem, we'll find out that Facebook's alerting and comms systems all run on Facebook. As a result, they can't even coordinate the restart to roll back changes.

Re: Facebook-owned sites were down

#677

Post by coolspot »

teddyh wrote: post #505

Interestingly, their .onion site¹ is also down. https://en.wikipedia.org/wiki/Facebook_onion_address

The onion site is just a reverse-proxy to the main web-site. So if the main site is down (due to internal DNS or BGP issues) onion reverse-proxy can’t get to it as well.

Re: Facebook-owned sites were down

#678

Post by suyash »

Animats wrote: post #628

There'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)…

Source (hacker group Anonymous) : https://twitter.com/YourAnonOne/status/1445082304393719818

Re: Facebook-owned sites were down

#679

Post by chippy »

marchingvehicle wrote: post #640

Where could the physical data centers be that they need to access? How far away could it be?

maybe, there are reports (i.e. unverified tweets) that employees cannot access sites due to the security systems also being down. I imagine email, and messaging for employees would also be down too.

It may be very hard for employees to get to the physical boxes, and/or bypass any physical or software security systems.

Post reply on HN