Facebook suffered technical issues on Friday causing its second outage in two months and affecting users worldwide.
The major service disruption meant users were greeted with an error message stating little more than “sorry, something went wrong”, when the social media giant, which serves over 1.3 billion users across the globe, became unexpectedly inaccessible for an unconfirmed amount of time.
While initial reports on Twitter appeared around 5pm, the service being back up and running in the UK by 6pm.
Facebook’s brief message apologised for the outage and said its team were “working on getting this fixed as soon as possible”.
The site’s Platform Status Page said, “Facebook is currently experiencing an issue that is affecting all API and web surfaces. Our engineers detected the issue quickly and are working to resolve it ASAP. We’ll update shortly.”
The company had also reported that it was having API issues on Wednesday.
“We had an increased rate of errors for the Graph API at 18:01-18:14 (PDT) today,” Facebook noted. “We reverted the change that caused the issue and we’re sorry for any inconvenience caused.”
Facebook are yet to say why the down time occured.
During the outage, “#facebookdown” was a trending topic in the US, according to the microblogging company, proving the extent of concern among users over the outage.
Some of the top Tweets joked about the outage, including one from @thetweetofgod, which said, “Attention world: #facebookdown. Please remain calm and do not attempt to interact with human beings”.
Another from @rashi_kakkar slammed Google’s rival social network.
The real reason why people freak out when Facebook is down is because the possibility of using Google+ becomes REAL. #facebookdown
— Rashi Kakkar (@rashi_kakkar) August 1, 2014
Shares of the company followed a similar trend in the hours following the outage and fell less than one percent to $72.25 in New York by 6:30pm UK time. Until Thursday, Facebook’s shares had climbed 32 percent this year.
Facebook experienced similar problems on 19 June when the service went down for 30 minutes. It also crashed in the US in February this year, after previously going offline for four hours due to network maintenance in October last year.