- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 100
What to do
Check whether your product depends on BigCommerce. 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-07-08 05:27 UTC and 2026-07-08 05:27 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 1
- resolved
We identified an issue where a subset of stores may see unexpected Staff Action Log entries generated by an API-driven background process. These entries are display-only logging artifacts and do not reflect staff user activity or changes made to the store. Some entries may continue to appear while we complete remediation. Store functionality, data, and security are not impacted, and no action is required.
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-066893140f
Is BigCommerce still down?
No, this incident was resolved 2026-07-08 05:27 UTC. For BigCommerce's live state, see https://down.guide/bigcommerce.
How long did it last?
0m, from 2026-07-08 05:27 UTC to 2026-07-08 05:27 UTC, by the times BigCommerce posted.
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.