[deleted]
Facebook-owned sites were down
921–930 of 1001 posts
Re: Facebook-owned sites were down
#922Looks like someone found the light switch and turned everything back on!
Re: Facebook-owned sites were down
#923Reddit r/Sysadmin user that claims to be on the "Recovery Team" for this ongoing issue: > As many of you know, DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now…
> Reddit r/Sysadmin user that claims to be on the "Recovery Team"
They have time to make public posts, and think it's a good idea?
Sure, I'm on the 'Recovery Team' too! How about you?
Re: Facebook-owned sites were down
#924It's back as of approx 14:47 PST.
Agreed, website loading here, still no whatsapp though.
Re: Facebook-owned sites were down
#925Is it just me or HN also feels kinda laggy?
General tip: If HN is being laggy and you're determined you want to waste some time here, open it in a private window. HN works extremely quickly if it doesn't know who you are.
This would make for a very good deep-dive technical discussion in an interview setting, I'm using this.
Re: Facebook-owned sites were down
#926Facebook and Messenger are working now.
Instagram and WhatsApp - not yet.
Re: Facebook-owned sites were down
#927They must have shut it off and turned it back on
Re: Facebook-owned sites were down
#928Facebook and Messenger are working now. Instagram and WhatsApp - not yet.
I was hoping it would stay down for longer haha
Re: Facebook-owned sites were down
#929There'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)…
"facebook.com" is registered with "registrarsafe.com" as registrar. "registrarsafe.com" is unreachable because it's using Facebook's DNS servers and is probably a unit of Facebook. "registrarsafe.com" itself is registered with "registrarsafe.com". I'm not sure of all the implications of those circular dependencies, but it probably makes it harder to get things back up if the whole chain goes down. That's also probabl…
Notes as Facebook comes back up:
"registrarsafe.com" is back up. It is, indeed, Facebook's very own registrar for Facebook's own domains. "RegistrarSEC, LLC and RegistrarSafe, LLC are ICANN-accredited registrars formed in Delaware and are wholly-owned subsidiaries of Facebook, Inc. We are not accepting retail domain name registrations." Their address is Facebook HQ in Menlo Park.
That's what you have to do to really own a domain.
Re: Facebook-owned sites were down
#930Earlier quoted context omitted.
This sounds like something that might have been done with security in mind. Although generally speaking, remote hands don't have to be elite hackors.
Have you ever tried to remotely troubleshoot THROUGH another person?!
Not OP, but many times. Really makes you think hard about log messages after an upset customer has to read them line by line over the phone.
One was particularly painful, as it was a "funny" log message I had added the code when something went wrong. Lesson learned was to never add funny / stupid / goofy fail messages in the logs. You will regret it sooner or later.