Meta API Latency Causing Delayed Meta CAPI Event Delivery

What to do

• Check whether you use BigCommerce Reporting & Analytics. 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 39m it lasted.

  Anything that failed between 2026-06-23 15:29 UTC and 2026-06-23 16:08 UTC may need a replay.

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

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

Updates from BigCommerce 3

1. investigatingJun 23, 2026, 3:29 PM UTC

   Commerce Engineers are actively monitoring increased latency from the Meta API affecting Meta CAPI (Conversions API) integrations. Meta CAPI events may be delivered later than usual while the backlog clears. Events are continuing to process and we are not seeing data loss at this time.

   provider

2. monitoringJun 23, 2026, 3:52 PM UTC

   Commerce Engineers continue to monitor increased latency from the Meta API affecting Meta CAPI (Conversions API) integrations. Event delivery remains delayed for some customers, but events are continuing to process and we are not seeing data loss. Processing capacity has been increased and the backlog is being monitored as it clears.

   provider

3. resolvedJun 23, 2026, 4:08 PM UTC

   Meta CAPI event delivery has caught up and is no longer delayed. Commerce Engineers will continue monitoring Meta API latency, which remains higher than normal, but event delivery has returned to normal and we are not seeing data loss.

   provider

Corrections

None so far.

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