On Friday, June 12, users across the globe faced an unprecedented outage in the digital ecosystem of the American corporation Meta. Simultaneously, key social networks—Facebook and Instagram—as well as messaging apps WhatsApp and Messenger, and the new text platform Threads, ceased to function.
Scale of the Problem
Information about the global nature of the outage is confirmed by data from the international monitoring service Down for Everyone or Just Me. The first alarming signals began to arrive around 16:20 Kyiv time. By 17:00, the flow of error reports had become avalanche-like.
Access issues have been recorded in dozens of countries, including Ukraine, the UK, the USA, Poland, Germany, and Denmark. The incident affected millions of users accustomed to the round-the-clock operation of these services.
Glitch Statistics
An analysis of user complaints allowed for the identification of three main categories of technical problems encountered by device owners:
- Complete Unavailability (58% of cases): Users see blank pages, browsers fail to refresh tabs, and mobile apps report a lack of network connection.
- Authorization Issues (22% of cases): Security systems forcibly terminate active sessions. Upon attempting to log in again, users encounter a password error, despite the data being correct.
- Server Errors (20% of cases): Web versions of sites display standard messages about technical glitches on the server side instead of the familiar interface.
Causes and Context
This incident became the second serious test for Mark Zuckerberg's corporation in the last ten days. On Wednesday, June 3, 2026, a Facebook outage lasting about 45 minutes was already recorded. At that time, engineers managed to quickly restore the operation of data centers.
However, the situation on June 12 turned out to be significantly more complex: absolutely all key products of the company went offline, including the recently launched Threads platform. At this moment, Meta representatives have not officially commented on the exact causes of the internal infrastructure failure. Nevertheless, cybersecurity experts lean towards the version of an internal error during the update of server routing configuration.