The Circuitry
THE CIRCUITRYYour one-stop source for all tech news
HOMETODAYNEWSFEEDEVENTS
BOOKMARKS
RSS
© 2026 The Circuitry
About UsSourcesContactCorrectionsPrivacy
  • Today
  • Feed
  • Events
  • Saved
Scroll for more
Verification
VERIFIEDConfidence: HIGH
Source identified
Claims cross-referenced
No discrepancies found
Fact-check summary

Reported by Frandroid; we couldn't independently corroborate via other outlets yet — story is recent.

1 caveat
  • ▲Discord status page and Downdetector show no incidents or spikes for June 12; no corroborating coverage found from other sources.
Sourcing
1source

via Frandroid

Frandroid · track record
44Stories
100%Verified
1530d
All sources →
Markets
META···

Live quote · not investment advice

Home/Tech/WhatsApp, Discord and Messenger Report Outage Starting at 15:40 on June 12
VERIFIEDBy Xavier Rivera· ·1 min read

WhatsApp, Discord and Messenger Report Outage Starting at 15:40 on June 12

WhatsApp, Discord and Messenger have been reported down simultaneously starting at 15:40 on June 12 with connection failures and login issues according to Frandroid. The outage points to possible server-side problems for the Meta-owned apps while Discord's involvement remains unexplained. Discord status shows no incidents reported today.

Source:Frandroid
Post
WhatsApp, Discord and Messenger Report Outage Starting at 15:40 on June 12
TL;DRAI · 60 sec read

WhatsApp, Discord and Messenger have been reported down simultaneously since 15:40 on June 12, with users unable to send messages or log in on multiple platforms. The Meta services failing together often signals a server-side issue rather than a device problem, yet the independent Discord outage makes the cause more difficult to explain without updates.

✓ Resolved1 update

Meta's outage was resolved with services largely restored within hours.

Jun 12, 4:17 PM ET
WhatsApp, Discord and Messenger have been reported down simultaneously since 15:40 on June 12, with users unable to send messages or log in.

Outage begins mid-afternoon. The first reports of failing connections date back to 15:40 on June 12. Messages became stuck on sending across the three services.
When the two go down simultaneously it is often a sign of a server-side issue rather than a user device problem.

On Messenger, multiple users reported a complete inability to log in from 15:42 onward. The problems affected both Android and other platforms.

Meta-owned services affected together. WhatsApp and Messenger both belong to Meta. When the two go down simultaneously it is often a sign of a server-side issue rather than a user device problem.
From The CircuitryThe Feed — live briefs across tech, all day.See what’s happening →

Users who restarted their apps multiple times believing the fault lay with their Wi-Fi can stop troubleshooting their own connections. The source of the bug remains unknown as of the latest reports according to Frandroid.
Users who restarted their apps multiple times believing the fault lay with their Wi-Fi can stop troubleshooting their own connections.

Discord outage adds complexity. Discord is independent of Meta. This makes the simultaneous outage more difficult to explain in the current state.
None of the platforms involved has communicated on the origin of the bug. The first reports of errors date back to 15:40 on June 12. Discord's status page shows no incidents reported today.
Why this mattersAI · ~100 words

Tap a lens to see what this story means for you.

Reader-supported
DonateBuy me a coffee →Follow@thecircuitry_ →Follow@thecircuitry.to →

Reader-supported · The Brief

Liked this? The Brief brings you the whole day in tech, verified, every morning. Two minutes, free forever.

HELP US IMPROVE
From The Circuitry

See what’s happening right now

The Feed runs all day — short, verified briefs the moment they break.

Open the Feed →
From The Circuitry

Follow @thecircuitry_

Every story we publish, as it happens. No noise between.

Follow on X ↗On Bluesky ↗

Reader-supported

The Circuitry is a passion project I've always wanted to build, and I love the work behind it.

Running it costs real money. APIs, hosting, time. To keep improving the site and growing this into something useful for everyone, those costs have to be covered.

Any contribution is appreciated. If not, no pressure. Thanks for reading.

Buy me a coffee
outageMetamessaging
More fromFrandroid
  • Samsung Hosts Galaxy Unpacked Event July 22, 2026

    Tech · 4d
  • Microsoft Halts July 2026 Windows 11 Update Rollout on Select Dell Machines

    Tech · 11d
  • UN Adopts First Global Rules for Driverless Cars

    Tech · 11d
More inTech
  • Microsoft Edge CVE-2026-57990 Allows External File Access

    Tech · 8h
  • Microsoft Edge Origin Validation Flaw CVE-2026-57989 Rated High Severity

    Tech · 8h
  • SpaceX Targets Tower Catch for Starship on Next Flight

    Tech · 1d
SupportThe Work

The Circuitry is reader-supported. If you find the daily brief useful, you can buy me a coffee to keep it going.

Buy a coffee →
SubscribeCircuitry Brief

Liked this? The Brief brings you the whole day in tech, verified, every morning. Free forever.

MORE IN TECH

Microsoft Edge CVE-2026-57990 Allows External File Access

Microsoft disclosed CVE-2026-57990, a high-severity vulnerability in Chromium-based Edge that lets unauthorized attackers disclose information by accessing external files or directories over a network. The CVSS 7.4 flaw, published July 26 2026, underscores the need for prompt patching in widely deployed browsers.

Microsoft Edge Origin Validation Flaw CVE-2026-57989 Rated High Severity

Microsoft disclosed CVE-2026-57989, a high-severity origin validation error in Chromium-based Edge that lets an unauthorized attacker disclose information over a network. The flaw is rated CVSS 7.4 and affects versions before 150.0.4078.99.

SpaceX Targets Tower Catch for Starship on Next Flight

SpaceX plans to attempt catching its Starship spacecraft with mechanical tower arms on the next test flight following a successful ocean landing on Flight 13. The milestone would advance the vehicle's reusability after demonstrating satellite deployment and an in-flight engine restart.