Facebook, Instagram, and WhatsApp down: What is known about global Meta outage
Meta servers can’t handle the load (photo: Unsplash)
On Friday, June 12, Meta services experienced a major technical outage. Users around the world are reporting problems accessing popular social networks and messaging apps, according to real-time data from the international monitoring service Down for Everyone or Just Me.
Scope of the issue and outage geography
The first signs of unstable platform performance were recorded at around 4:20 p.m. Kyiv time, and by around 5:00 p.m., the wave of error reports had become massive and rapidly escalating.
The outage is global in scale — users in Ukraine, the United Kingdom, the United States, Poland, Germany, Denmark, and many other countries are reporting an inability to open the apps.
According to statistics from specialized monitoring platforms, the nature of the issues is distributed as follows:
- Full inaccessibility (58% of reports): users see blank pages, tabs fail to refresh, and apps display messages indicating a lack of network connection.
- Authentication issues (22% of reports): security systems automatically log users out of active sessions, and attempts to log back in trigger password error messages.
- Server errors (20% of reports): web versions of the sites display a general server error instead of the usual interface.
Another blow to Meta’s servers
This incident has become the second major test for Mark Zuckerberg’s corporation in the past ten days. The previous significant Facebook outage, lasting around 45 minutes, was recorded quite recently — on Wednesday, June 3, 2026.
At that time, engineers managed to quickly restore the data centers. However, today’s situation proved to be far more complex, as all of the company’s key products went down simultaneously, including Threads.
Meta representatives have not yet officially commented on the exact cause of the internal infrastructure failure. However, cybersecurity experts suggest that the issue may have been triggered by an internal error during a server routing configuration update.
