Table of Contents

  1. What Happened on November 6
  2. Why Outages Cause Self-Inflicted Damage
  3. The First Hour: A Triage Order That Works
  4. After Resolution: Verify, Do Not Assume
  5. The Merchant API Angle
  6. Build an Outage Playbook Before Black Friday
  7. When It Is Not the Outage
  8. A Worked Example: Reading Your Numbers After an Incident
  9. Communicating With Your Team and Customers
  10. Frequently Asked Questions

What Happened on November 6

Google posted on the Merchant Center Status Dashboard at 5:26 AM Eastern on November 6, 2026 that it was investigating reports of an issue with Merchant API, Merchant Center and Feeds. Search Engine Roundtable reported the confirmation that morning. The dashboard's incident record lists the incident as beginning at 04:30 UTC and ending at 13:00 UTC the same day, around eight and a half hours, and it has since been marked resolved.

Google did not publish a detailed explanation in what we reviewed. The practical effect for merchants was the usual mix of symptoms: feed fetches that did not complete, products that appeared delayed or stuck, and dashboards that did not load or update. If your account looked odd that morning, the likely culprit is the platform and not you.

Source note

Times and affected services come from the public Merchant Center Status Dashboard incident page and Search Engine Roundtable coverage dated November 6, 2026. We do not know the root cause and do not speculate on it here.

Why Outages Cause Self-Inflicted Damage

An outage itself rarely suspends an account. The damage comes from what merchants do next. People re-upload feeds repeatedly, delete and re-create data sources, change settings to see if anything responds, or submit appeals for disapprovals that are only a processing delay. Each action can introduce a real problem on top of a temporary one.

The danger is highest in November. Prices change, promotions go live, stock moves quickly, and a delay in processing feed updates can cause temporary price and availability mismatches. Google has said that mismatches between your feed and your landing page can lead to disapproval. We cover that mechanism in our automatic item updates guide and in the price accuracy violations article.

The First Hour: A Triage Order That Works

  1. Check the status dashboard first. If an incident is listed, note the start and end times. That timestamp range is your evidence window.
  2. Do not edit anything yet. Take screenshots of Diagnostics, your data source processing status, and the account issues page.
  3. Compare product counts. Note total, approved, pending and disapproved counts. These are the baseline numbers you will compare against after recovery.
  4. Pause non-critical feed pushes. If your tooling pushes updates on a schedule, consider pausing frequent jobs until the incident clears, to avoid piling up failed or partial updates.
  5. Hold appeals and manual reviews. Disapprovals tied to the window may clear by themselves once processing resumes.

Treat the first hour as read-only. Observation costs nothing, while action during an incident has a real chance of making your picture murky.

After Resolution: Verify, Do Not Assume

Once the dashboard marks the incident resolved, wait for a couple of normal processing cycles before drawing conclusions. Then work through a verification routine.

If you use third-party tools, read their status page too. Many feed apps queue failed jobs and retry them later, which can lead to a burst of updates at an unexpected time.

The Merchant API Angle

The incident listed Merchant API alongside Merchant Center and Feeds. That matters because Google shut down the Content API for Shopping on August 18, 2026, which means most programmatic feed integrations are now running on the Merchant API. If you maintain a custom integration, your retry logic and error handling matter more than ever. Our guide to migrating from the Content API and feed methods covers the move, and the feed management API article explains the mechanics.

Good retry logic backs off exponentially, caps attempts, logs every failure, and avoids resubmitting the entire catalog when only some items failed. A naive loop that hammers the API during an incident can leave you with partial updates that take hours to reconcile.

Build an Outage Playbook Before Black Friday

With the holiday peak approaching, write down the decisions you do not want to make under pressure. A one-page playbook should name an owner, define what counts as an incident, and state which actions are allowed during one.

Peak-season outage playbook

Bookmark the Merchant Center Status Dashboard and subscribe your team to its updates where possible.

Record baseline counts for total, approved and disapproved products every morning during peak.

Define a freeze rule: no bulk feed changes while an incident is open.

Keep a list of your top 100 revenue products so you can spot check them quickly.

Make sure sale prices have start and end dates that match your site, so late processing does not strand stale prices.

Agree with your agency or developer who can pause scheduled feed jobs.

Write a template note for your team explaining that an incident is not an account suspension.

Our BFCM account safety plan and feed monitoring and alerting guide pair well with this playbook.

When It Is Not the Outage

Be honest about whether the outage explains your problem. If your account was suspended or you see misrepresentation or policy warnings, an eight-hour platform incident is not the cause. Suspensions result from account-level evaluations and are not a side effect of status incidents. If you got a suspension notice, start with our suspended account guide and run a free scan to find the root cause before you appeal.

A Worked Example: Reading Your Numbers After an Incident

Suppose your store has 4,000 products. On the morning of the incident you recorded 3,920 approved, 60 pending and 20 disapproved. By evening, approved is 3,610 and pending is 360. Nothing in your feed changed. That pattern, a jump in pending with no matching jump in disapproved, is what a processing delay looks like. The right move is to wait and observe.

Now suppose approved dropped by 300 and disapproved rose by 300, with a new reason such as price mismatch. That is not a delay. During the window, a sale price may have gone live on the site while the feed was stale. This is a real issue, and the fix is to resubmit current prices once processing is healthy and verify the page and feed agree.

A third pattern: counts are stable but impressions fell sharply. Compare against the previous same weekday. If the drop is limited to the incident window and recovers afterwards, it was likely delivery disruption. If it continues, investigate bids, budgets and competitive changes before blaming the platform. Our auction insights guide is useful for the competitive side.

Communicating With Your Team and Customers

Incidents create confusion internally. Marketing sees a spend dip, a developer sees API errors, and the owner sees a dashboard warning. Appoint one person to publish a short internal note with the facts: what Google reported, the time window, what you verified, and what you are doing. Avoid speculation about causes.

Customers rarely notice a feed delay, but if a sale price was missing or a product showed as out of stock on Google while available on your site, some shoppers may see a mismatch. Make sure your support team knows how to explain it: the site is the source of truth, and the price on the product page is the price that applies, subject to your published terms.

Finally, store a post-incident note with the dashboard link, your before and after counts, and any actions you took. Over a year you will build a record that helps you distinguish your own problems from platform problems, and gives you something concrete to share if an agency or client asks what happened.

Frequently Asked Questions

Will the outage hurt my Shopping ad performance? Possibly in the short term if products were delayed or temporarily unavailable. Check impressions and spend for the incident window before changing bids, and compare against a normal day.

Should I resubmit my feed after an incident? Only if your data source shows a failed or stale fetch. A normal scheduled fetch after resolution is usually enough. Repeated manual uploads add noise.

Can Google suspend my account because of an outage? We found no source suggesting that. Suspensions come from policy evaluations. Outage-related disapprovals typically clear as processing resumes.

How do I know if my third-party feed app was affected? Check the app's status page and logs for failed jobs around 04:30 to 13:00 UTC on November 6, 2026, and replay any failed updates.

Where can I see past incidents? The Merchant Center Status Dashboard lists current and recent incidents, and Google publishes announcements in its Merchant Center help center.

Know What Is Broken Before You Fix It

Separating platform incidents from real policy problems saves hours. A free scan at gmcunbanned.com checks your store for the policy and landing page issues that most often trigger suspensions.

Run Free GMC Scan →