Last Monday, netizens caused an uproar due to the sudden Facebook Instagram outage. This Facebook Instagram outage was reported in several countries in Asia, Australia, Europe, and the America. Users were greeted with error messages like "Sorry, something went wrong." Computer and mobile access of Facebook and Twitter also experienced glitches for about an hour, which briefly made humans to have an actual and personal interaction.

A day after, Facebook released a statement via USA Today, saying: ""Earlier today, many people had trouble accessing Facebook and Instagram. This was not the result of a third party attack, but instead occurred after we introduced a change that affected our configuration systems. We moved quickly to fix the problem, and both services are back to 100% for everyone." As opposed to some rumors, the error was self-inflicted.

Meanwhile, Lizard Squad, a black hat hacking group, blamed Twitter for the Facebook Instagram outage. They claimed hacking Microsoft and Sony gaming networks last Christmas. The group even tweeted: "Facebook, Instagram, Tinder, AIM, Hipchat #offline #LizardSquad." Some did not focus on what this group's claim believing Lizard Squad just wanted attention.

Aside from Facebook-owned Instagram, Tinder also experienced this error as this dating app relies on Facebook. Millions were affected by this certain Facebook Instagram outage. Currently, Facebook serves 1.35 billion users, while Instagram is home to 300 million photo-posting individuals. About four-fifth of Facebook's active users reside outside North America.

Due to Facebook Instagram outage, some Twitter users joked about this happening, saying that they can now read actual books and talk to friends live. Tweets about this mishap occurred on Twitter shortly after the outage, with "#SocialMeltdown2015" and #facebookdown" quickly trending. A gamut of comments and reactions dominated Twitter during that hour.

This Facebook Instagram outage has been Facebook's largest outage since September 2010 when the social network was temporarily inaccessible for about 2.5 hours.