Google confirms a Merchant Center, Merchant API and feeds incident

What changed

The latest incident update shown was dated 10:26 UTC. A later dashboard refresh timestamp is not a separate incident-resolution announcement. Teams should consult the linked live status page for changes after this article’s check rather than treating this snapshot as a permanent statement of service health.

Emmanuel Flossie separately reported internal errors affecting product processing. His account observation is useful context, while Google’s status record supplies the official confirmation and product scope. The existence of a service incident does not establish that every account or every feed was affected in the same way.

For an affected account, preserve the error message, processing time and relevant feed or API request identifiers in the team’s normal troubleshooting record. Compare those observations with Google’s incident timeline. Avoid attributing every product rejection or policy issue on the same day to this incident without checking the actual error.

This report corrects the newsletter draft’s statement that no incident appeared on the dashboard. That statement is no longer accurate against the official record inspected for publication. It also does not adopt a practitioner’s proposed waiting period as an official recovery instruction.

No resolution time or confirmed root cause is asserted here. The incident’s effect on a particular campaign’s eligibility or spend should be checked in that account. A product-processing disruption and an advertising-performance decline can coincide without the status page establishing a direct causal link for every campaign.