Home Cyber Security News Here’s What Caused Facebook’s Global Outage

Here’s What Caused Facebook’s Global Outage

by Abeerah Hashim
Facebook outage

Global Facebook Services Outage

Facebook recently had a terrible outage that caused all its services to go offline globally. The incident caught attention as the users flooded Twitter with WhatsApp, Instagram, and Facebook’s inaccessibility complaints.

Many people initially suspected it to be an issue with their ISP, it turned out that the issues appeared at Facebook’s end. Consequently, Facebook, WhatsApp, Instagram, and Oculus remained unavailable for over six hours, causing massive trouble.

It is pertinent to mention that Facebook services hold a necessary stance for business and individual users for their day-to-day communications and business activities. Hence, these outages were frustrating for some users.

Finally, Facebook authorities confirmed the glitches via their official Twitter accounts.

After all the chaos, Facebook has finally revealed what triggered the issue.

As elaborated in a blog post from Santosh Janardhan, Facebook’s VP, Infrastructure, the outages happened due to a technical issue during “configuration changes on backbone routers”.

Our engineering teams have learned that configuration changes on the backbone routers that coordinate network traffic between our data centers caused issues that interrupted this communication. This disruption to network traffic had a cascading effect on the way our data centers communicate, bringing our services to a halt.

This problem affected not only the services but also the tech giant’s internal systems. Hence, it became difficult for the teams to resolve the matter.

According to reports, even Facebook employees couldn’t enter their workplaces as their badges to access the doors stopped working.

What Facebook Disappeared From The Internet

Although Facebook’s explanatory post doesn’t reveal many technical details about why exactly it suddenly disappeared from the internet. What people observed during the outages was that visiting “facebook.com” would return no results. Rather the domain appeared to be ‘for sale’ (due to a third-party mess-up unrelated to Facebook’s technical issue).

Explaining the matter, Johannes B. Ullrich from the SANS Technology Institute highlighted the problem as a DNS error. As elaborated,

The BGP routes pointing traffic to Facebook’s IP address space have been withdrawn. The Internet no longer knows where to find Facebook’s IPs. One symptom is that DNS requests are failing. But this is just the result of Facebook hosting its DNS servers inside its own network. Even with working DNS (for example if you still have cached results), the IPs are currently not reachable.

Service Restoration Underway

Hours after the outages, Facebook officials eventually started restoration efforts (of course, after getting into the data centers, finally). As Janardhan explained in the post, the team is actively working for 100% service restoration. He also ruled out any cyber attacks behind this situation.

We want to make clear at this time we believe the root cause of this outage was a faulty configuration change. We also have no evidence that user data was compromised as a result of this downtime.

Indeed, many users worldwide can now access their Facebook, Instagram, and WhatsApp accounts again. Anyone still facing issues should rest assured to get the access back shortly.

Let us know your thoughts in the comments.

You may also like


Bazmohammad October 9, 2021 - 6:27 am

I want my freedom

veleiro October 6, 2021 - 3:17 pm


Comments are closed.

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid