Facebook Instagram And WhatsApp Are Working Again
Facebook is back up and active again after the worldwide outage that occurred this morning. Thank the God of the Internet - we don't have to actually talk to each other anymore.
Oh, and the hordes of people who suddenly defected over to Twitter can now come crawling back with their tails between their legs.
Seriously though, we don't actually know what caused the outage, which saw millions of people unable to access WhatsApp, Instagram, or Facebook. It's happened quite a bit recently though, hasn't it?
The outage was first reported by traffic monitoring site Down Detector. They received more than 6,000 reports from people complaining about not being able to use their favourite social media site for a matter of hours.
It occurred at about 10am this morning and there were reports from Asia, the United States, and all across Europe. It didn't affect everyone, so perhaps you were able to get on. For most of us - particularly those who work on the internet - it's been something of a mild inconvenience.
Regardless, you can now get back to idly scrolling through Instagram to avoid talking to your loved ones over Sunday dinner, or perhaps you prefer monitoring the slightly racist and off colour jokes shared by your uncle on Facebook.
More Like This
Anonymous Instagram Influencer Complains About Working Eight Hour Day Since Likes Were Hidden
Perhaps you enjoy nothing more than bombarding your friends with memes at every hour of the day in your private WhatsApp chats? Whatever it is, you can get back to doing it as it's all back on.
Of course, it's not exactly an unusual phenomenon this, is it? In fact, it was only last month that we experienced something similar in the UK.
The good news was that it wasn't anything sinister. Rumours started circling pretty quickly from people claiming that Facebook had suffered from a severe hacking incident, or a distributed denial-of-service attack.
The social media giant eventually cleared it all up and said that the problems were as a result of a "server configuration change".
Exactly what that means is anybody's guess. Either way, it's back now.