Facebook is known to behold people’s interactions and communication. What if it goes down?
Facebook Went Down: In-Depth
Users have faced major problems according to reports online. But eventually came up with page specific error this time. Things changed from 5:00 PM (GMT), all the pages on Facebook went down eventually stopping us from accessing it and it also showed the error message, “Sorry, something went wrong. We’re working on getting this fixed as soon as we can.”
An Independent website DownDetector.com, that tracks connectivity issues with major online platforms, many users have complained/reported about the outrage. Though social networking website allows you to login but the recent posts on the news feed or in the timeline are updating.
ALSO READ: Now, Podcast In Facebook? Live Audio Comes To Social Network!
How Much Money Did Lose?
According to a lot of infographic website, the social networking giant earns an estimate of $230USD per second (2016, yet to update the report). This figure is based on Facebook’s yearly earning divided by the number of working seconds.
So, according to the above figures, for 30 minutes downtime, they lost a total of $414,000. How?
$230USD per second x 60 Seconds x 30 minutes (estimate) = $414,000 USD
Though the losses are more than what we calculated, as the social networking giant’s revenue involves likes, embedded websites, ads and so on. Well, all these speculations are assumptions based on the different infographics (nothing is official).
ALSO READ: You Can Monetize Your Facebook Videos Soon: YouTube’s Competitor!
#FacebookDown: Trending
Many users have reported about this issue on Down Detector and many have outraged this issue and took it over to Twitter with a hashtag “#facebookdown”.
Facebook is down! Friday the 13th! #friday13th #facebook #facebookdown pic.twitter.com/0DPGTd08sh
— Egzon Bunjaku (@egzonche) January 13, 2017
Just waiting for Facebook pages to get back online #facebookdown pic.twitter.com/vjpYqVEXEz
— Nomy Sahir (@Nomysahir) January 13, 2017
According to some news/reports, it is some server problem, which is now solved. It took over 3 hours to completely sort the problem. There is no official statement from by the company about the issue yet, though the problem/issue was resolved.
