Live / BigCommerce / Incident
BigCommerce: High Rate of Cloudflare Challenge Pages
BigCommerce · bigcommerce.comMinor incidentResolved2026-10-29 22:29 UTC
Public — what happened
Summary
BigCommerce said that starting at 03:11 UTC on 2026-10-28, its platform was receiving an unusually large amount of automated traffic aimed at stores. It reported that merchants and shoppers might see a Cloudflare page asking them to confirm they are human, after the engineering team put security rules in place to protect reliability and performance. The company said it was adjusting those rules to cut down on the interruptions and working with its vendor to better identify this kind of traffic, and it told merchants having trouble with the Control Panel or API to contact Support. BigCommerce marked the incident resolved at 22:29 on 2026-10-29.
Affected
Storefront
Timeline
- Started — 2026-10-28 03:11 UTC
- Monitoring — 2026-10-28 03:11 UTC
- Resolved — 2026-10-29 22:29 UTC · 43h 18m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach BigCommerce against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for BigCommerce: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the BigCommerce report →
More from BigCommerce
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.