At roughly 14:36 British Summer Time on Tuesday, Instagram and Facebook—both owned by Meta—went dark for millions of users worldwide. The failure triggered a cascade of error messages, login problems, and a surge of frantic posts on X as people tried to confirm whether the glitch was personal or global. Within minutes, outage monitors logged thousands of complaints, and humor quickly followed the chaos.

Down Detector logs 3,000 Instagram reports and 21,860 Facebook alerts in the first half hour

According to data from outage monitoring service Down Detector, more than 3,000 users reported Instagram issues within the first 30 minutes, with 68% citing app crashes or freezes and 12% unable to log in at all . facebook fared worse, attracting 21,860 reports in the same window, half of which involved mobile app malfunctions and a third describing login failures. The rapid accumulation of complaints turned the technical glitch into a public spectacle, as users flocked to X to verify the problem.

Desktop browsers showed a stark "Sorry, this page isn’t available" error, while mobile apps behaved inconsistently

Users accessing Instagram via desktop browsers were met with a plain error page stating, "Sorry, this page isn’t available," effectively blocking all activity. Mobile experiences varied: iPhone testers from The Daily Mail noted that the main feed eventually loaded, but Direct Messages and Stories remained inaccessible. Facebook Messenger also suffered, with 8,694 reports by 14:46 BST, 52% of which were login failures. The disparity between desktop and mobile performance underscores the complexity of Meta’s backend infrastructure.

Cybersecurity experts point to DNS fragility as a likely cause, not a hack

Jake Moore, a global cybersecurity advisor at ESET, told reporters that widespread outages of this nature are rarely the result of malicious attacks. Instead, he highlighted the Domain Name System (DNS) – an "outdated, legacy network" that translates URLs into IP addresses – as a single point of failure that can trigger a "catastrophic collapse" across dependent services. Replacing DNS is a monumental task, which explains why similar disruptions keep resurfacing across the internet’s major platforms.

Who will Meta blame? No official comment as users scramble for answers

As of the article’s publication, Meta had not issued any statement on its corporate X or Threads accounts, and The Daily Mail’s request for comment went unanswered. The silence leaves users and analysts guessing whether the outage stems from internal server overload, a DNS misconfiguration, or another technical glitch. The lack of transparency fuels speculation and adds to the anxiety of users fearing account compromise.

What remains unverified about the outage?

  • Whether the DNS issue was isolated to Meta’s own infrastructure or involved a third‑party provider.
  • The exact duration of the outage and when full functionality was restored for all regions .
  • If any data loss or security breach occurred during the downtime.