Coincidence? I think not. A complete outage for a service like this is unlikely at best unless it was self inflicted to protect them from the upcoming whistleblower hearings and the released “Pandora documents”. They will probably claim maintenance or a blocked hack attempt, however the timing is way to suspicious. On top of that, you will not be able to post anything related to the incident without being put in Facebook jail or booted completely.
Will update on this just like daytime TV, As the world burns, Genital hospital, One post to live.
After some investigation, it would appear that FB houses and owns it’s own DNS registrar a-d.facbook.com DNS servers that all seem to be having difficulty. Simply put the chances of this happening are extremely slim, unless they put all them in the same network which would be idiotic. With no apparent “back up DNS failover like cloud fair or even an old dell computer sitting in a corner office somewhere is preposterous.
This was an intentional act. They are scrubbing their digital data like an FBI raid was coming to the Wolf of Wall Street.
Complete DNS failure would and does stop ALL NORMAL public traffic to normal people, internet ninja’s could use the direct IP if it wasn’t purposely manipulated, that is a vast task as they have hundreds if not thousands. This just another measure to cover up what ever the whistleblower has in those documents and or data from the Pandora release which would probably point fingers and some people who would rather not be documented.
2030 EST: PBS reports indicate that an “internal Update” was the cause that did not only stop public view but internal communications as well. So, an internal update for a tech giant that is almost impossible to achieve a total failure what was the update for? Oh yeh we don’t know. Sorry folks this “internal update” was a purge of data and footprints, i assure you. They will play the “bad timing” card and we will forget this ever happened. I assure you, there is something else lurking.
