- Level
- confirmed
- Worst impact
- Degraded
- Components
- Reporting & Analytics
- Down Index
- 28of 100
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 1h 42m it lasted.
Anything that failed between 2026-03-05 16:42 UTC and 2026-03-05 18:24 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 2
- monitoring
Commerce Engineers are investigating a delay with Meta CAPI event delivery caused by an active Meta Marketing API incident. Events continue processing at a reduced rate, which has created backlog for a subset of stores. We will continue monitoring and provide updates as they are available.
provider
- resolved
Commerce Engineers have resolved the delay with Meta CAPI event delivery caused by the Meta Marketing API incident. Event processing has returned to normal rates, and backlog for affected stores has been cleared.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d1b6d1177c
Is BigCommerce still down?
No, this incident was resolved 2026-03-05 18:24 UTC. For BigCommerce's live state, see https://down.guide/bigcommerce.
How long did it last?
1h 42m, from 2026-03-05 16:42 UTC to 2026-03-05 18:24 UTC, by the times BigCommerce posted.
What was affected?
BigCommerce named Reporting & Analytics.
What caused it?
BigCommerce hasn't published a root cause. If it does, it shows here.
Where does this come from?
BigCommerce's official status page, https://status.bigcommerce.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.