You were printing money.

Four ROAS, two months straight, new customers all day. Then you opened Ads Manager on July 7th.

CPM had jumped from $6 to $12 overnight. Cost per click up nearly a dollar. New customer acquisition sitting at zero all morning, on an account that has never seen a zero.

Same ads. Same funnel. Same offer. Same tracking.

Your founder is in Slack asking what happened. Your CFO wants to know why spend is flat and revenue is halved.

So you check Meta’s status page.

Green. All systems operational.

That is the trap. The status page stays green while delivery burns, and in the silence you start doing the one thing that turns a bad week into a bad month: you panic and rebuild.

This is the triage guide. You’ll learn how to tell “Meta broke” from “my account broke,” what to freeze during a disruption, how to quarantine the bad dates so they don’t poison your optimisation, and how to find ground truth when the dashboard is lying to your face.

A calm performance marketer at a Meta ads control desk under a glowing green all-clear status lamp while the campaign panels behind quietly catch fire

Is it a Meta outage or is it your account?

Here’s the fastest way to tell them apart.

To separate a Meta outage from an account problem, check three things at once: did every campaign drop simultaneously, are other advertisers reporting it on the same day, and does your backend revenue still match the dashboard. Platform-wide and all at once means Meta. One lonely campaign means you.

That test matters because the two problems have opposite fixes. An account problem you fix by changing something. A platform event you fix by changing nothing and waiting.

Run the diagnosis in order:

  • Did everything drop at once? A real outage hits every campaign uniformly, CPMs spiking across the whole account in the same hour. One ad set tanking while the rest run fine is a you problem.
  • Are your peers screaming? The r/FacebookAds “Bug / Outage” flair is the fastest early-warning system in the industry. When a dozen brands post the same CPM spike on the same date, that is your peer signal.
  • Does the backend agree? Open Shopify or Stripe. If real revenue is stable but Meta’s ROAS “dropped,” you have a reporting break, not a delivery break.
  • What does the status history say? Meta’s own page rarely admits ad-delivery faults, so check a third-party tracker like the metastatus Ads Manager history for a delivery incident logged on your bad date.

And this is not a freak event you’ll never see again.

An analysis of platform status data counted more than 60 Meta Ads outages between October 2024 and March 2026, with delivery issues making up 53% of them and outage frequency up 316% from early to late 2025. Meta offers no public uptime guarantee, unlike Google’s 99.9%.

“Is it Meta or is it me” is now a permanent Q3 question, not a once-a-year scare.

Why the panic edit is the most expensive thing you can do

When your CPM doubles overnight, every instinct says do something.

Restructure. Consolidate. Kill the losers. Rebuild the account you spent six months teaching. That instinct is the villain of this whole story, and it costs more than the outage ever will.

Here’s why.

Meta’s delivery runs on a learning phase. Every time you make a meaningful edit, a budget change over 20%, an audience swap, a creative cull, a bid change, the ad set resets and relearns from scratch.

It needs roughly 50 conversions to stabilise again. Until it does, delivery is volatile and expensive.

So picture the sequence.

The platform glitches for 48 hours. You panic and restructure everything. The glitch resolves on its own by Thursday. But now your rebuilt account is stuck in a fresh learning phase, bleeding budget into junk inventory, and you’ve thrown away weeks of accumulated signal chasing a problem that fixed itself.

You didn’t recover faster. You reset the clock.

The outage ends. The reset doesn't.

Advertisers report that the delivery damage lingers for days, sometimes weeks, after an outage is technically over. Most of that lingering pain isn’t Meta. It’s the learning phase you triggered by panic-editing during the disruption.

The June 12th outage this year became the case study. One advertiser watched the platform make unauthorised changes during the fix.

A shop destination switched on. The website destination switched off. Promotions enabled on ads that never had them. A publish-loop bug on one ad triggered an extra reset on top of the platform-wide one.

The lesson isn’t “trust Meta.” It’s “when the platform is unstable, your edits are unstable too.”

What to freeze during a Meta disruption

Once you’ve confirmed a platform-level event, your job flips from operator to bodyguard. You are protecting the account from the thing most likely to damage it: you.

Freeze these until the dust settles:

  • Restructures. Do not consolidate campaigns or rebuild your account mid-outage. The structure was never the problem.
  • Budget changes over 20%. Big swings reset learning. If you must cut exposure, pause a whole campaign rather than yo-yo the daily budget.
  • Audience and creative edits. New ad sets, paused ads, swapped creative, every one throws the set back into learning at the worst possible time.
  • Bid and optimisation changes. Switching event or bid strategy during volatility layers a self-inflicted reset onto a platform one.

The hard part is doing nothing while a stakeholder watches spend flatline. So give them the plan instead of a knee-jerk.

Give the CFO a date, not a defence

Tell them plainly: this is a platform-level delivery event, the fix is to hold structure and let it stabilise, and you’ll reassess in 72 hours with backend revenue, not dashboard ROAS. A calm timeline beats a panicked rebuild every time.

There is one active move that helps rather than hurts: a cost cap.

Setting a hard cost control stops Meta from dumping your budget on the dirt-cheap, low-quality impressions it reaches for during a disruption. It introduces friction without resetting your learning.

That is exactly what you want when the algorithm is drunk. For the deeper version of this playbook, see our guide to regaining control of your Facebook ads.

How to quarantine the bad dates so they don’t poison optimisation

An outage doesn’t just cost you the two bad days. It teaches Meta the wrong lesson.

Every garbage impression, every trash click, every bounced visitor from the disruption becomes a signal the algorithm optimises against going forward. If you let the bad dates sit inside your reporting and your learning window, you’re training delivery on noise.

So quarantine them.

  • Exclude the outage window from analysis. When you judge performance, cut the disruption dates out of your date range so a two-day spike doesn’t drag your averages and trigger a bad decision.
  • Break performance down by day, not by lump sum. A seven-day view hides the story. Day-by-day, the outage shows up as two ugly dates surrounded by normal ones, which is exactly how you confirm it was an event, not a trend.
  • Read the right attribution. Meta’s compare attribution settings panel lets you view conversions across windows side by side, so you can see whether results actually vanished or just moved buckets.
  • Don’t feed the reset. Resist re-optimising toward whatever the outage made “cheap.” Those dirt-cheap CPMs are Meta finding dirt-cheap impressions by dumping your budget, not a new audience you should chase.

Then let the account recover on the signal it had before the mess. Untouched structure plus quarantined bad dates is how you come out the other side in days instead of weeks.

How to find ground truth when the dashboard is lying

Here’s the uncomfortable part. During a disruption, Ads Manager is the least trustworthy screen you own.

The platform is incentivised to show numbers that keep you spending, its reporting lags reality by hours, and an outage scrambles attribution on top of all that. So you need signal from outside the black box.

A panicked media buyer dismantling a perfectly good campaign engine into scattered parts with a wrench while a storm cloud rains overhead, the engine was never the problem

Start with the metrics Meta can’t fudge.

  • Outbound clicks. If outbound clicks hold steady but reported conversions crater, you know it’s an attribution artefact, not a creative or delivery collapse. One agency notes that stable outbound clicks against a dropped conversion count is proof the problem is measurement, not your ads.
  • Backend revenue. Shopify and Stripe deposits are the only ROAS that pays the bills. If the bank is unchanged, your ads are probably fine and Meta just lost sight of them. This is the same trap we cover in the ROAS mirage that wastes ad spend.
  • Blended MER. Total revenue over total spend, across every channel, is your calmest signal during a platform event. The dashboard swings; MER barely moves.

That covers the numbers. But numbers only tell you that something changed, never why buyers went quiet.

For the why, there’s one source Meta can’t glitch: your customers.

When platform data goes dark, first-party customer conversations are the signal that keeps reporting.

hollie goes and has real conversations with the people who bought, browsed, or bounced this week, and brings back their exact words on what stopped them, ranked. So while your dashboard is scrambled, you’re still hearing straight from the market.

You can have hollie talk to your customers and get answers a status page never will. That’s the difference between panicking at a red screen and knowing what’s actually true.

For the platform-side version of ground truth, our Meta GEM update guide covers server-side tracking and why the dashboard stopped being reliable.

A marketer trusting a giant smiling dashboard face that is secretly crossing its fingers behind its back while a small honest customer beside them holds up the real number

Frequently asked questions

How do I know if it’s a Meta outage or my account?

Check three signals together: did every campaign drop at the same time, are other advertisers reporting it on r/FacebookAds on the same date, and does your Shopify or Stripe revenue still match the dashboard. Platform-wide, simultaneous, and peer-confirmed points to Meta. An isolated dip points to your account.

Should I pause my ads during a Meta outage?

Usually no. Pausing and unpausing resets the learning phase and can make recovery slower once the platform stabilises. Hold your structure, freeze big edits, and consider a cost cap to stop budget bleeding into junk inventory. Reassess in 72 hours using backend revenue, not dashboard ROAS.

Why did my CPM double overnight in July 2026?

Advertisers widely reported CPMs jumping from around $6 to $12 during the early-July delivery disruptions, with cost per click up nearly a dollar. During an outage, Meta often floods you with cheap, low-quality impressions, so your budget spends but delivery quality collapses. The status page frequently stays green through it.

How long does Meta outage damage last?

The outage itself may resolve in hours, but the impact on delivery, optimisation, and data can linger for days or even weeks. Most of that tail is self-inflicted: edits made in panic during the disruption trigger fresh learning phases. Leave your structure alone and recovery is measured in days.

Does the Meta status page show ad delivery outages?

Often not. Advertisers repeatedly find the status page showing all systems operational while delivery is clearly broken. That is why peer signal on r/FacebookAds and third-party status trackers, cross-checked against your own backend revenue, are more reliable than Meta’s own dashboard during a disruption.

Confirm it. Freeze it. Wait it out.

The Bottom Line

When your CPM doubles overnight, the outage isn’t your biggest risk. The panic edit is. Confirm it’s platform-wide, freeze your structure, quarantine the bad dates, and judge recovery on backend revenue, not a dashboard built to lie.

When the numbers go dark, get ground truth from the one source Meta can’t glitch: let hollie talk to your customers and bring back the why.