Live / BigCommerce / Incident
BigCommerce: Search is returning server errors for a subset of stores
BigCommerce · bigcommerce.comMinor incidentResolved2026-10-05 19:11 UTC
Public — what happened
Summary
BigCommerce reported that search was producing server errors for some of its stores beginning on October 5, 2026 at 16:40 UTC, and rated the problem as minor. Within minutes the company said it had found the problem and put a fix in place, though it did not describe a cause. At 17:50 UTC BigCommerce said the search errors had stopped but that affected stores could see a lag before recent updates showed up in search results. The incident was marked resolved at 19:11.
Affected
Storefront
Timeline
- Started — 2026-10-05 16:40 UTC
- Investigating — 2026-10-05 16:45 UTC
- Identified — 2026-10-05 16:46 UTC
- Monitoring — 2026-10-05 16:47 UTC (2 updates)
- Resolved — 2026-10-05 19:11 UTC · 2h 30m 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 42, 2026, our weekly internet health report.