Search Indexing Delays Affecting a Subset of US Stores
This incident has been resolved.
The latest update from BigCommerce.
State
Resolved
Started
12 d ago
2026-10-20 09:23 UTC
Lasted
1 h 10 min
until 2026-10-20 10:33 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
30 min 43%
Identified
1 min 0%
Monitoring
40 min 57%
Updates
Times in UTCAs posted by BigCommerce
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Commerce Engineering has identified the cause of the search indexing delays affecting a subset of stores. As part of the mitigation, the affected functionality has been temporarily disabled for affected stores.
Commerce Engineering is investigating an issue causing delays in product search indexing for a subset of US stores. Our team is working to identify the root cause and restore normal indexing performance.
Affected components
2BigCommerce in the last 90 days
Full historyIncidents in 90 days
36
Days with an incident
31
Median duration
1 h 20 min
This incident
About the median
Other BigCommerce incidents
All incidentsBigCommerce·High Rate of Cloudflare Challenge Pages
This incident has been resolved.
BigCommerce·Degraded search availability across the platform
This incident has been resolved. All services are operational.
BigCommerce·Bolt payments are currently failing
This incident has been resolved.
BigCommerce·Some Android shoppers on headless storefronts may be unable to reach checkout
This incident has been resolved.
BigCommerce·Search availability reduced and latency increased
This incident has been resolved.
Follow BigCommerce
Your coding agent knows when BigCommerce is down, and tells you when a failure is theirs, not yours. You can also get BigCommerce incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "bigcommerce" and tell me if BigCommerce has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=bigcommerce/feed subscribe https://outages.cc/feed.xml?providers=bigcommerceFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane