Intermittent Availability Issues
BigCommerce reported intermittent product availability issues for a subset of stores on the Storefront component. The fix was implemented and BigCommerce monitored the results. The incident is resolved and lasted 62 minutes.
State
Resolved
Started
Lasted
1 h 2 min
Worst impact
Partial outage
Timeline
4 updatesInvestigating
31 min 51%
Identified
3 min 5%
Monitoring
27 min 44%
Updates
Times in UTCAs posted by BigCommerce
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
BigCommerce engineers are currently investigating intermittent product availability issues with a subset of stores. We will provide an update shortly.
Affected components
1BigCommerce in the last 90 days
Full historyIncidents in 90 days
34
Days with an incident
29
Median duration
1 h 29 min
This incident
31% shorter than the median
Other BigCommerce incidents
All incidentsBigCommerce·Some products are not searchable in Storefront
BigCommerce storefront search did not work correctly in some cases. Search results missed products and showed unexpected in-stock filtering. BigCommerce reports that the incident is resolved. The outage lasted 1 hour and 52 minutes.
BigCommerce·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.
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.live/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.live/feed.xml?providers=bigcommerce/feed subscribe https://outages.live/feed.xml?providers=bigcommerceFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane