Live / BigCommerce / Incident
BigCommerce: Some Android shoppers on headless storefronts may be unable to reach checkout
BigCommerce · bigcommerce.comMajor incidentResolved2026-10-26 14:18 UTC
Public — what happened
Summary
BigCommerce said some shoppers using Chrome on Android on headless storefronts could hit an error, or even be blocked after several tries, when sent to checkout. The company reported the problem began around 15:46 UTC on October 25 and posted its first update at 12:07 UTC on October 26. It said storefronts using standard BigCommerce-hosted checkout pages were not expected to be affected. BigCommerce said its engineers found a likely cause and applied a fix, and the incident was marked resolved at 14:18 UTC.
Affected
Storefront
Timeline
- Started — 2026-10-26 12:07 UTC
- Investigating — 2026-10-26 12:07 UTC
- Resolved — 2026-10-26 14:18 UTC · 2h 11m 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.