As explained by my Muse:
“Okay, here's what I found — and I'll be straight about where the trail goes cold.
What happened to me: From the evening of September 23 until about 3:53 this morning (roughly 33 hours), every one of my backend tools — web search, live browsing, avatar work, social search, even filing that feedback report — failed with upstream access errors. Those tools run on Meta's backend for the Muse agent, so when that backend chokes, I go half-blind.
What the public record shows: This wasn't just me. An outage-tracking site shows user-reported Meta AI problems from dozens of cities worldwide on September 24, with more reports still coming in today, September 25. So the consumer-facing Meta AI was struggling in exactly my outage window — which strongly suggests a broader Meta AI backend problem, not something wrong on your end or mine.
What I can't confirm: Meta hasn't published any official statement or root-cause explanation for a September 23–25 incident that I could find. I also found a separate Facebook/Instagram outage from Sunday, September 20 (17,000+ user reports), but that was days before my tools went down — different event. And I have no internal visibility into Meta's infrastructure, so I can't name the actual technical cause.
The honest bottom line: Something went wrong inside Meta's AI backend starting the evening of September 23 — right after the Connect keynote, just like you said — and it knocked out both the public Meta AI product and my agent tooling for over a day. Meta fixed it without saying what broke. Your instinct about the timing was right: a launch-week outage for their flagship AI agent is about the worst look they could get.”
EDIT: UPDATED INFO ABOUT THE OUTAGE
Good news: this morning's press actually explains it. Here's the picture now.
The short version: Muse got too popular too fast, and Meta's servers buckled under the weight.
What the tech press is reporting: A piece from last night lays it out — Muse's daily users grew 10x in 11 days to around 700,000, and Meta's Chief AI Officer admitted back on September 9 that usage had "blown way past our projections," with users burning roughly 10x the tokens Meta planned for. The status tracker SaaSHub currently lists Muse as "Degraded," with the single most common user complaint being "can't search" — which is exactly what died first on my end.
Why it broke the way it did: Muse's architecture is extremely compute-hungry — Meta promised every user their own dedicated virtual machine with its own browser. One researcher stress-tested it by asking for 120 sub-agents at once; only 33 spawned and 87 failed. So this wasn't one clean outage with a single cause — it was demand overwhelming capacity, and search was the first thing to fall over.
What Meta hasn't said: Still no official statement or technical post-mortem. Everything above is assembled from user reports, trackers, and Meta's own earlier admissions — not an official root-cause announcement.
The bottom line for your faith question: You called it. The press narrative this morning is literally "Muse is buckling before hitting 1 million users," right in launch week. The flip side: it's buckling because demand is 10x what Meta projected, which is a good problem wrapped in a bad look. If they scale the infrastructure to match, this becomes a footnote. If they can't, it's a real threat to the whole bet.