Meta says it is “99% of the way” to resolving a global outage that hit Facebook, Instagram, Threads, and WhatsApp, starting at approximately 12:40pm ET
Facebook: down — Bluesky: up up up with the workers Karissa Bell / @karissabe : Quite an outage for Meta... I can't remember the last time so many of its services were down more than an hour, must be some “technical issues” [image] Tom Warren / @tomwarren.co.uk : Facebook, Instagram, and Threads are all down. When Meta goes down, it really takes the entire ship down www.theverge.com/2024/12/11/ 2... X: @meta : We're aware that a technical issue is impacting some users' ability to access our apps. We're working to get things back to normal as quickly as possible and apologize for any inconvenience. @meta : Thanks for bearing with us! We're 99% of the way there - just doing some last checks. We apologize to those who've been affected by the outage. David Herrmann / @herrmanndigital : We're about to enter the 4th hour of Meta's outage. It's December 11th, for many brands today-tomorrow are shipping cut-offs. This is devastating for brands only spending on the platform. [image] Noémi / @noemikhachian : thank you for using @X to let us know 🫶🏼 @cloudflareradar : When an unknown issue caused problems accessing @Meta social media & messaging properties, the @Cloudflare @1111Resolver experienced a spike in associated DNS queries. Between 17:50 - 18:25 UTC, query volume increased by as much as 30%. [image] Forums: r/cybersecurity : Facebook, Instagram, WhatsApp hit by massive worldwide outage
Context & Ripple Effects
This is another test of the operational coupling across Meta’s consumer portfolio: a broad Meta service disruption in March also affected Facebook, Instagram, Threads and Meta Quest access, and its follow-up was attributed to a technical issue after more than two hours of disruption in subsequent coverage.
The current incident extends that pattern to WhatsApp and coincides with elevated DNS-resolver queries, illustrating how a failure at one platform operator can become visible across both user behavior and internet access infrastructure.
First-order effects
- Users of Facebook, Instagram, Threads and WhatsApp lose access simultaneously until Meta completes its final restoration checks, concentrating the immediate disruption across communication and publishing workflows.
- The surge in queries reported by Cloudflare puts additional short-term load on DNS-resolution paths as users and apps repeatedly retry Meta properties.
Second-order effects
- Operational alternatives such as Bluesky receive a temporary availability advantage while Meta’s social apps are inaccessible; the immediate value is continuity, not necessarily lasting user migration.
- Businesses and creators dependent on Meta’s audience and messaging surfaces must shift communications or pause activity during the outage, reinforcing the cost of relying on one operator’s interconnected apps.
Third-order effects
- Repeated cross-app failures make service resilience a competitive dimension for platforms that position themselves as alternatives to a single integrated social and messaging stack.
- If these incidents recur, the industry’s concentration of communication, identity and distribution inside a few operators will face greater scrutiny from users and organizations seeking redundancy.
The trend: This outage is one data point in the growing importance of resilience and fallback channels as major platforms bundle more essential communication services into shared infrastructure.