Facebook Marketing Connections failures - "Error code 100: Unsupported request - method type: post"

What to do

• Check whether you use Airbyte Facebook Marketing Source. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-06-23 09:37 UTC and 2026-06-23 09:37 UTC may need a replay.

• Subscribe to Airbyte's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=airbyte works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Airbyte 1

1. resolvedJun 23, 2026, 9:37 AM UTC

   Type: Incident Duration: 7 hours and 11 minutes Affected Components: Facebook Marketing Source Jun 23, 16:49:25 GMT+0 - Resolved - **Summary:** Meta deprecated the `breakdowns=dma` (Nielsen DMA) parameter across all Facebook Marketing API versions effective June 22, 2026\. This caused failures in the `ads_insights_dma` and `ads_insights_demographics_dma_region` streams for the Facebook Marketing source connector. **Resolution:** The connector has been upgraded to v6.0.0, replacing the deprecated DMA streams with Meta’s recommended Comscore Market equivalents. This is a breaking change. **Affected streams:** * `ads_insights_dma`→ replaced by`ads_insights_comscore_market` * `ads_insights_demographics_dma_region`→ replaced by`ads_insights_demographics_comscore_market_region` **Customer action required to resolve:** 1. Upgrade the Facebook Marketing source connector to v6.0.0 2. Refresh the source schema to discover the new streams 3. Enable the new Comscore Market streams and reset them to backfill data 4. If using Custom Insights with the`dma`breakdown: update the configuration to use`comscore_market` instead. For more information, please see [Facebook Marketing Migration Guide](https://docs.airbyte.com/integrations/sources/facebook-marketing-migrations#upgrading-to-600). Jun 23, 11:32:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 23, 09:37:57 GMT+0 - Investigating - We are currently investigating this incident.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.