On August 22–23, 2026, multiple signals emerged indicating intermittent disruptions in the Meta Ads Creation and Editing API. While the official Meta status dashboard [https://metastatus.com/] reported the service as operational, community feedback across StatusGator, Reddit, and STM Forum highlighted recurring anomalies in ad delivery and API connectivity.

Technical Manifestations

Reports from advertisers and developers described failures in campaign creation, delayed synchronization with Shopify listings, and login errors affecting Business Manager accounts. Outage clusters were logged in the United States, United Kingdom, Brazil, Greece, and the Philippines, with users noting that ads were “not working as usual” and API connections were intermittently blocked.

Operational Impact

For traffic arbitrage teams, the disruptions translated into stalled campaign launches and unreliable reporting pipelines. Several affiliates noted that automated scripts relying on the Ads Creation API failed to push updates, resulting in delivery gaps of up to several hours. Media buyers operating in high-frequency verticals such as iGaming and Nutra reported measurable ROAS volatility during the downtime window.

Community Signals

• — StatusGator logged 33 user-submitted outage reports within 24h ending August 22.
• — Reddit threads in r/facebookads documented login failures and ad creation errors.
• — STM Forum members flagged anomalies in API-driven campaign automation tools.
• — Partnerkin discussions referenced Shopify sync failures tied to API instability.

Root Cause and Disclosure

Meta has not issued an official incident report, and the root cause remains undisclosed. The absence of acknowledgment on the official dashboard suggests either localized routing issues or transient API instability not classified as a global outage. Without confirmation, operators must treat the event as unverified but operationally relevant.

Practical Considerations for Media Buyers

Teams relying on automated campaign deployment should implement fallback mechanisms, including manual upload protocols and monitoring scripts to detect silent API failures. Given the frequency of unacknowledged anomalies, maintaining redundancy in reporting pipelines is critical for CPA-driven operations.

Sources

[https://metastatus.com/] [https://ads.google.com/status/publisher/] [https://www.tiktok.com/business/en-US/blog] [https://affiliateworldforum.com/v2/] [https://afflift.com/] [https://partnerkin.com/] [https://statusgator.com/]