Replies

I would have thought a company like Facebook would have had monitors in place to detect this sort of tweaking and pre-existing relationships with the big DNS hosts to get it fixed quickly if it happened.

But now that this has gone on for several hours, I’m starting to wonder how it is that it hasn’t been fixed yet unless it was intentional by Facebook (for some reason I don’t comprehend). If it was some sort of hack, it really should have been fixed by now at least on the top level servers. Just thinking about the ad revenue they’re losing is pretty mind-blowing - it would certainly justify any resources necessary to get this fixed.

It all came back up an hour ago... maybe more. It's a strange story though. From what I read, it was major "ownage" by somebody who very probably was on the inside to start with. I read that not only did somebody delete their DNS data, but there was also a customer data breach of 1.5 billion accounts, AND that somebody hacked their entry control systems on their buildings so that tech support personnel couldn't get in to troubleshoot.

Some of that doesn't add up. In order for what I just wrote to be absolutely TRUE, FaceBook network services personnel would have had to NOT have access to internal networks via VPN, which is difficult to believe in this day of "virtual office" and social distancing. So IF they needed to be ON SITE to fix this problem, then it was indeed a monumental problem to start with... then to NOT be able to get inside the buildings because of entry control system problems? It all adds up to a much, MUCH larger problem, and NOT the "limited" thing they're making it out to be.

I'd like to have been a fly on the wall within their network services team, but suffice to say, this wasn't NOT a "simple DNS hack". Somebody p0wn3d them badly, and for most of the day as well.