Platform Outage vs. Account-Specific Ad Problem: How to Tell the Difference, Diagnose, and Respond

The difference between a platform outage and an account problem

A **platform outage** is a failure on the platform's side that hits many advertisers at once. Meta's official post-mortem of the October 4, 2021 incident describes a maintenance command that "unintentionally took down all the connections in our backbone network, effectively disconnecting Facebook data centers from the Internet globally." No advertiser caused it, and no advertiser could fix it.

An **account-specific problem** is scoped to your account: a billing failure, a policy flag, a permissions gap, an ad stuck in review, an exhausted budget, or broken tracking. From inside Ads Manager both look identical—delivery slows or stops—but the correct responses are opposites. Practitioner guidance puts it bluntly: an account problem is fixed by changing something; a platform event is fixed by changing nothing and waiting.

The platforms themselves treat the two checks as a pair. Meta's troubleshooting for Ads Manager errors starts with checking account status on Business Support Home *and* checking for platform outages. Meta's status-page documentation states the logic directly: check the status page first to determine whether the problem is on the platform's end or in your own implementation, hardware, or network.

Most account-specific problems live at layers you own or control:

- **Billing**: the payment method, balance, or spending limit attached to the account. - **Access**: who holds admin or partner access to the ad account, Page, and Business Portfolio. - **Policy and review**: ad rejections, account flags, verification requirements. - **Setup**: budgets, schedules, targeting, and tracking configuration.

Knowing which layer you own—and which layer the platform owns—is the foundation of every diagnosis that follows.

Signs of a platform-wide outage

Platform-wide outages have a recognizable signature. Treat the following as strong indicators:

- **Everything drops at once.** All campaigns are affected simultaneously, and the drop starts at a specific hour rather than declining gradually. One failing ad set next to healthy ones is not an outage pattern. - **Spend continues but conversions flatline.** When delivery and spend pace normally while reported conversions hit zero, practitioners read that as an attribution or reporting failure on the platform side—not a demand collapse. The cross-check: if actual revenue (Shopify, Stripe, your CRM) is normal while the platform shows zero conversions, it is a tracking/reporting issue on their end. - **The interface itself degrades.** Ads Manager loads slowly, reports fail, edits don't save, or dashboards show stale data. - **Other advertisers report the same symptoms.** Community sources frequently surface outages before official acknowledgment—practitioner monitoring notes community reports often precede status-page updates by one to two hours. Corroboration across many advertisers is the strongest single signal. - **Official status confirms it.** Meta maintains a Platform Status Dashboard and a Facebook for Business Status page covering Ads and other business products. Large outages do happen: Meta's own account of the October 4, 2021 incident confirms a global disconnection of its data centers.

Practitioners who track Meta disruptions distinguish four outage types—delivery, attribution, reporting lag, and partial pixel loss—because each demands a different response. A delivery outage (spend stops) is not the same event as an attribution outage (spend continues, conversions vanish from reports), and confusing them leads to exactly the wrong action.

Signs of an account-specific problem

Account-specific problems have the opposite signature: the blast radius is you.

- **Only your account is affected.** Competitor ads in your vertical are still running and no one else is reporting issues. Practitioner diagnostics treat active competitor delivery as near-proof the problem is account-level—a billing issue, a policy flag, or a review failure. - **You received a platform notification.** Google states that suspensions trigger an in-account alert and an email, and that suspensions or billing issues stop ads from running until resolved. Meta surfaces account flags in Business Support Home and error icons in the Ads Manager Delivery column. - **The decline is gradual or matches your own changes.** Performance that eroded over days, or that broke right after an edit you made, points inward. - **A named blocker appears.** On TikTok, a red Not Delivering status carries a secondary reason—out of budget, payment unsuccessful, account not approved, review not approved—each pointing at a specific owner.

Distinguish the restriction level before acting, especially on Meta:

- **Person/profile**: your individual login or identity is restricted. - **Ad account**: the account itself is flagged or suspended. - **Page**: the Page is unpublished, deactivated, or you lack Page permissions—Meta requires permissions to both the Page and the ad account to advertise. - **Business Portfolio**: the container holding your assets is restricted, which can cascade to everything inside it.

Practitioner analysis describes Meta enforcement at three distinct levels—ad-level disapprovals, ad account restrictions, and Business Manager suspensions—each with a different recovery path. Finally, check ownership basics: who owns the ad account, who holds admin/partner access, and whose payment method is attached. A removed admin or a failed card on file can look exactly like a platform problem until you check.

How to diagnose where the issue is

Work this sequence in order. It takes minutes and prevents hours of misdirected fixing.

**1. Check official status first.** Meta provides a Platform Status Dashboard and Facebook for Business Status for ads and business products. Meta's own status guidance is explicit: check the status page first to determine whether the problem is on their end or yours—and if the platform reports no known issues while you still have problems, the next step is direct support, because the cause is likely in your implementation.

**2. Corroborate externally.** Look for concurrent reports from other advertisers and check whether competitor ads are still delivering. Multiple advertisers reporting identical symptoms in the same window points platform-wide; silence points at your account.

**3. Rule out local causes.** TikTok's official troubleshooting lists the basics: disable content-blocker extensions, try incognito mode, test a different browser, clear cache and cookies, and confirm your account has the right permissions. Meta's error guidance similarly includes clearing cache and updating the browser. A problem that only exists in one browser was never an outage.

**4. Use in-account diagnostics.** Google Ads offers Recommendations, diagnostic insights that highlight issues limiting serving, and Explanations that identify reasons for performance changes in one click. Meta surfaces delivery errors in the Delivery column. TikTok exposes secondary statuses per ad.

**5. Cross-reference against ground truth.** Compare platform reporting with backend revenue. If sales are stable while the dashboard shows zero, suspect measurement, not delivery.

**6. Change nothing until the diagnosis is complete.** Every edit made mid-diagnosis destroys evidence and, on Meta, can reset learning. Confirm what you're dealing with; then act once.

What to do during a platform outage

Once you've confirmed a platform-wide event, your job shifts from operator to guardrail.

- **Identify the outage type before touching anything.** Delivery outage (spend stops), attribution outage (spend normal, conversions invisible), reporting lag (data delayed), or partial signal loss. During a confirmed attribution outage, practitioners are explicit: do not pause—delivery is working, and pausing a healthy campaign imposes a real learning-phase cost. - **Freeze changes.** Don't edit creative, budgets, bids, or structure mid-outage; changes made now corrupt your data and can trigger learning resets when the platform recovers. In a severe, confirmed delivery outage, a budget-protection pause can be defensible—document the timestamp. - **Document everything.** Screenshot the status page, your dashboards, and spend during the window. This evidence is the foundation of any later credit request. - **Communicate early and factually.** Tell clients or executives what type of event it is, that it's platform-wide, what you've decided, and when the next update lands. Don't quote revenue losses from mid-outage dashboard data—those numbers often correct themselves. - **Set expectations honestly.** Practitioner reporting notes Meta provides advertisers no SLA, no automatic credits, and no public restoration timeline; credit requests are reviewed case by case with no guarantee. Meta does not document a restoration timeline or outcome in advance, so plan around that uncertainty rather than promising results. - **After restoration, wait.** Attribution typically back-fills over 24–72 hours. Withhold performance judgments and budget decisions until the data normalizes.

What to do for an account-specific problem

Account-specific problems are fixed by changing the right thing once—not everything at once.

**Google Ads** - Resolve account-level blocks first: suspensions and billing issues stop serving until fixed, and Google notifies you by in-account alert and email. - Work the documented checklist: campaign dates, active ad groups and ads, disapprovals (visible in the Status column), bids, budgets, targeting, conversion tracking. - Use Recommendations and diagnostic insights rather than guessing. - Respect review timelines: most ads are reviewed within 24–48 hours, but new accounts or certain formats can take up to 5 business days. Don't mistake a normal review window for a malfunction.

**Meta** - Check Business Support Home for account flags and resolve them before anything else. - Fix payment failures—an invalid or underfunded payment method stops delivery. - For rejected ads, request another review through Business Support Home rather than duplicating blindly. - Verify permissions on both the Page and the ad account, especially after team or agency changes.

**TikTok** - Read the secondary status and fix the named blocker: top up the budget layer that ran dry (campaign daily budgets start at $50, ad group daily at $20), clear outstanding balances (TikTok pauses campaigns and can suspend accounts over unpaid balances), complete account approval, or fix and resubmit rejected ads. - If local troubleshooting is exhausted, contact support.

**Tracking and access hygiene** - Isolate variables before escalating. Meta's own troubleshooting suggests turning the ad off and on and waiting 5–15 minutes, duplicating the ad, or creating it fresh; TikTok directs advertisers to support after local steps are exhausted. If the problem persists after local fixes, treat it as platform-side and escalate instead of rebuilding. - Confirm ownership structure: who owns the account, who holds admin/partner access, where billing lives, and—if you run on agency infrastructure—what the portability and offboarding path looks like so a partner change never strands a live account. - Never open a replacement account to route around a suspension; practitioners warn this triggers permanent bans on Meta and Google. Appeal through official channels instead.