{"id":348736,"date":"2021-10-05T22:12:38","date_gmt":"2021-10-05T19:12:38","guid":{"rendered":"https:\/\/en.buradabiliyorum.com\/facebook-deleted-itself-from-the-internet-but-how-review-geek\/"},"modified":"2021-10-05T22:12:38","modified_gmt":"2021-10-05T19:12:38","slug":"facebook-deleted-itself-from-the-internet-but-how-review-geek","status":"publish","type":"post","link":"https:\/\/buradabiliyorum.com\/en\/facebook-deleted-itself-from-the-internet-but-how-review-geek\/","title":{"rendered":"#Facebook Deleted Itself From the Internet\u2014But How? \u2013 Review Geek"},"content":{"rendered":"

“#Facebook<\/a> Deleted Itself From the Internet\u2014But How? \u2013 Review Geek”<\/strong><\/p>\n

\n
\"The
Facebook<\/span><\/figcaption><\/figure>\n

Facebook hasn\u2019t had a great week. Or a great month, really. Leaked internal documents show that the company has intentionally promoted anger and misinformation on its platform, a revelation that\u2019s forced Facebook to defend itself in front of Congress<\/a>. But as it struggled to control its public image on Monday, something odd happ<\/a>ened\u2014Facebook and its services disappeared from the internet for six hours.<\/p>\n

The unexpected outage, which is the longest Facebook has experienced since 2008<\/a>, took down all of its apps and services. People across the globe were unable to use Instagram, WhatsApp, Oculus, and other Facebook-owned platforms during the outage. And because many people use Facebook to log into 3rd party apps, they found themselves locked out of game<\/a>s, athletic apps, and other software.<\/p>\n

So what happened? Well, we\u2019ve known the basic details since yesterday. Facebook and its domains were pulled from global routing tables, effectively blocking anyone from connecting with the company\u2019s servers. The \u201cfacebook.com\u201d domain disappeared from the internet, and even showed up as \u201cfor sale\u201d on domain websites (an accident, but still).<\/p>\n

\n

To the huge community of people and businesses around the world who depend on us: we’re sorry. We\u2019ve been working hard to restore access to our apps and services and are happy to report they are coming back online now. Thank you for bearing with us.<\/p>\n

\u2014 Facebook (@Facebook) October 4, 2021<\/a><\/p>\n<\/blockquote>\n

Because Facebook operates its own registrar, we concluded that something bad happened within<\/em> the company\u2019s facilities. A successful hacking attempt at this scale is unlikely, so we were left with two possibilities\u2014either Facebook\u2019s server infrastructure encountered a critical failure, or a Facebook employee pulled the plug. The latter option seemed like a strong possibility, given the bombshell 60 Minutes<\/em> interview with a Facebook whistleblower that occurred on Sunday.<\/p>\n

But Facebook now says<\/a> that a \u201croutine maintenance job\u201d led to the outage. The company\u2019s engineers issued a command to assess Facebook\u2019s global network capacity, and for whatever reason, the command \u201cunintentionally took down all the connections in our backbone network, effectively disconnecting Facebook data centers globally.\u201d<\/p>\n

Facebook\u2019s networks could no longer respond to DNS queries, making them totally inaccessible. This problem required a hands-on fix from engineers, who had trouble getting on-site because Facebook facilities are defended by smart security systems, such as network-connected keycards. Unfortunately, Facebook hosts these security systems on its own servers, which were unresponsive<\/em>.<\/p>\n

We\u2019re not really sure how Facebook engineers got to the company\u2019s servers\u2014reports that they used an angle grinder<\/a> to break down doors and cages have not been verified by Facebook or independent sources. Either way, Facebook managed to resolve the issue, but it had to slowly bring its services online to prevent a surge in traffic, which would trigger a dramatic increase in power consumption and damage Facebook\u2019s server hardware.<\/p>\n

\n

Between 15:50 UTC and 15:52 UTC Facebook and related properties disappeared from the Internet in a flurry of BGP updates. This is what it looked like to @Cloudflare<\/a>. pic.twitter.com\/PFw5FR2W5j<\/a><\/p>\n

\u2014 John Graham-Cumming (@jgrahamc) October 4, 2021<\/a><\/p>\n<\/blockquote>\n

The consequences to this outage may not seem obvious. After all, you probably had a pretty productive workday without Instagram! But in some countries, namely India<\/a>, WhatsApp is the<\/em> primary form of mobile communication. If the Facebook outage had gone on for a full week, or even just a few days, it could have had a serious impact on Indian business, emergency medicine, and society.<\/p>\n

And as documented by CloudFlare<\/a>, people began to repeatedly refresh Facebook and its services after they went down, leading to a 30X traffic increase. While this traffic increase probably didn\u2019t hurt Facebook\u2019s efforts to bring its servers back to life, it did put a small strain on non-Facebook networks, a sign that future outages could cripple internet infrastructure as a whole.<\/p>\n

While we enjoyed taking a six-hour break from social media, we\u2019re worried that Facebook\u2019s recent outage may be a sign of things to come. One small mistake brought down an empire for a full day and tanked Facebook stock<\/a>\u2014when a mistake is this easy to make, it will almost certainly happen again. Even if you\u2019re conspiratorially-minded and think that a disgruntled employee brought down Facebook, the idea that one engineer could pull off such a feat isn\u2019t very reassuring.<\/p>\n

Source: Facebook (1<\/a>, 2)<\/a> via BleepingComputer<\/a><\/small>\n<\/div>\n