Tag Archives: DNS

Why Facebook, Messenger, WhatsApp, Instagram Went Down!

Facebook and ALL of its messaging and social media platforms went down for about six hours, including Messenger, WhatsApp and Instagram!

Find out why they all went down at the same time, and for so long!


Facebook, Messenger, WhatsApp, Instagram + More DOWN!

The entire slew of messaging and social media platforms owned by Facebook was inaccessible for about six hours, including :

  • Facebook
  • Facebook Messenger
  • WhatsApp
  • Instagram
  • Oculus
  • Workplace

The failure also extended to Facebook authentication, which you may be using to log into third-party apps and games, with Pokemon Go and Match Master gamers have reported problems logging in.

This left Twitter as the only major social media network still up and running, which is ironic since it became the only way for Facebook to reach out to the world…

This massive outage couldn’t come at a worse time for Facebook, whose stock slumped about 5.5% after former employee and whistleblower, Frances Haugen, leaked internal documents to the Wall Street Journal.

She also accused her former firm of repeatedly and knowingly allowing the proliferation of hate speech and misinformation for profit. Really tough times for Team Zuckerberg indeed…

Even Edward Snowden chimed in, saying that the world has become a healthier place for one shining day…


Why Did Facebook, Messenger, WhatsApp, Instagram, etc. Go DOWN?

This massive, unprecedented GLOBAL outage appears to be caused by a DNS (Domain Name Server) failure.

The DNS service “translates” the plaintext link we use (www.facebook.com for example) into its actual numerical IP address ( for example), allowing your app or browser to connect to the right server.

Without a working DNS service, no one is able to connect to any Facebook-owned service because the Internet no longer knows how to locate the right server.

CloudFlare senior vice-president Dane Knecht shared that the Facebook BGP (Border Gateway Protocol) routes have been “withdrawn from the Internet”, causing failure to connect through CloudFlare’s DNS service.

This was likely due to a configuration error on Facebook’s side, but coming one day after the story broke on Frances Haugen? It would be folly to rule out internal sabotage or a rush to remove some controversial features before she testified to the US Congress.

The conspiracy theory that it was a DDOS (Distributed Denial-of-Service) attack by Anonymous or some vigilante group is really farfetched. It would require an incredible amount of resources and coordination to not only bring down Facebook, but all the other services as well… at the same time!

Read more : Did 13 Year Old Sun Jisu Hack Facebook, WhatsApp, Instagram?

Facebook’s Vice-President of Infrastructure, Santosh Janardhan, later confirmed that “configuration changes” on their “backbone routers” caused the 6-hour long failure.

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.

He also asserted that it was a faulty configuration change, and no user data was compromised.

Our services are now back online and we’re actively working to fully return them to regular operations. 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.

While he blamed “the underlying cause” for impacting their ability. to “quickly diagnose and resolve the problem”, it is notable that it took Facebook engineering teams more than 6 hours to resolve a DNS failure.

It is now believed that the changes were made to Facebook’s Border Gateway Protocol, a mechanism that exchanges routing information to help figure out the fastest route for any request.

Apparently, the changes “withdrew” Facebook services from the DNS system, making it impossible for anyone to connect to them.

Even worse, Facebook ran their own systems through the same servers, so everything from engineering tool, messaging services and even security systems that controlled the key fob locks were no longer accessible.

So their engineering team had to rush to their data centres to manually reset the servers there.

Needless to say, this will be a big wake-up call for their engineering teams, and in the words of Russell Peters – “Somebody’s gonna get a hurt real bad!

It is also a big wake-up call for everyone using Facebook services. This massive outage is a reminder that we should NOT put all our eggs in one basket.

I believe it will at least temporarily spur the adoption of alternative messaging services like Telegram and Signal. Even Twitter should see a nice boost in Tweets and maybe new users.

Now, I’m not into conspiracy theories… but what are the odds of this failure happening just one day after Frances Haugen came out publicly against Facebook, and a day before she was set to testify before the US Congress?

Could these “configuration changes” be designed to remove some controversial features before Haugen’s testimony to the US Congress?

Could Facebook’s own engineering team have accidentally triggered the failure in their rush to remove those controversial features before she testified?


Please Support My Work!

Support my work through a bank transfer /  PayPal / credit card!

Name : Adrian Wong
Bank Transfer : CIMB 7064555917 (Swift Code : CIBBMYKL)
Credit Card / Paypal : https://paypal.me/techarp

Dr. Adrian Wong has been writing about tech and science since 1997, even publishing a book with Prentice Hall called Breaking Through The BIOS Barrier (ISBN 978-0131455368) while in medical school.

He continues to devote countless hours every day writing about tech, medicine and science, in his pursuit of facts in a post-truth world.


Recommended Reading

Go Back To > Internet | Software | Tech ARP


Support Tech ARP!

Please support us by visiting our sponsors, participating in the Tech ARP Forums, or donating to our fund. Thank you!

Heads Up! ICANN Rolling DNS Key Change In October!

Los Angeles, California – For the first time ever, the Internet Corporation for Assigned Names and Numbers (ICANN) is about to change the cryptographic keys that help secure the Internet’s Domain Name System (DNS).

“It is critical that Internet Service Providers and network operators around the world make certain they are ready for this change as failure to do so can result in their users being unable to look up domain names and thus be unable to reach any site on the Internet” said David Conrad, ICANN’s Chief Technology Officer. Conrad added, “Network operators should ensure they have up-to-date software, have enabled DNSSEC, and verified that their systems can update their keys automatically or they have processes in place to manually update to the new key by 1600 UTC on 11 October 2017.”


The ICANN DNS Key Change

The changing, or “rolling” of the DNS key, is an important step in keeping the global DNS safe and secure. It is very much in line with commonly accepted operational practices that ensure that important security infrastructure can support changing password if the need were to ever arise.

[adrotate group=”2″]

“We’ve launched a testing platform so network operators can make certain that they are ready for the key roll well ahead of October 11,” said Conrad. That testing platform can be accessed at https://go.icann.org/KSKtest. Internet users should contact their ISP or network operators to make certain they are ready for the key change.

ICANN has been working with technical partners such as the Regional Internet Registries, Network Operations Groups, and domain name registries and registrars as well as others in the Internet ecosystem, such as the Internet Society and Internet trade associations, to make certain that those around the world who may be impacted by the key roll are aware of the pending change.

ICANN Chief Executive Officer Göran Marby has sent correspondence to more than 170 government officials including regulators and participants in ICANN’s Government Advisory Committee, asking that they make certain the network operators in their respective countries are aware and ready for the DNS key change.


Support Tech ARP!

If you like our work, you can help support our work by visiting our sponsors, participating in the Tech ARP Forums, or even donating to our fund. Any help you can render is greatly appreciated!