BigCommerce reported "Some products are not searchable in Storefront" on its status page at 2026-11-04 18:41 UTC. Some products do not appear in Storefront search results. BigCommerce has identified the cause and engineers are working on a fix.

BigCommerce lists these components: Storefront.

When did the incident start and end?

It started at 2026-11-04 18:41 UTC. This page shows the end time when BigCommerce marks it resolved.

How do I get alerts for BigCommerce?

Subscribe to the BigCommerce live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of BigCommerce. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

BigCommerceIncident ·

Some products are not searchable in Storefront

NoticeOfficial update

Some products do not appear in Storefront search results. BigCommerce has identified the cause and engineers are working on a fix.

State

Identified

Started

Ongoing for

1 h 16 min

Worst impact

Notice

Timeline

2 updates

18:4119:0019:1919:3819:57

NoticeUpdate postedTimes in UTC

Investigating

34 min 45%

Identified

42 min 55%

Updates

Times in UTC

As posted by BigCommerce

Identified

The cause of some storefront searches returning incorrect results, including missing products and unexpected in-stock filtering, has been identified. Our engineers are actively working on a resolution. We will post another update as soon as it is in place.

Investigating

The issue causing some storefront searches to return incorrect results, including missing products and unexpected in-stock filtering. Our engineers are investigating the cause.

Affected components

Storefront

BigCommerce in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 10 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

43 h 18 min

median 1 h 10 min

90 days agoToday

Other BigCommerce incidents

All incidents

BigCommerce·High Rate of Cloudflare Challenge Pages

This incident has been resolved.

Resolved

BigCommerce·Degraded search availability across the platform

This incident has been resolved. All services are operational.

Resolved

BigCommerce·Bolt payments are currently failing

This incident has been resolved.

Resolved

BigCommerce·Some Android shoppers on headless storefronts may be unable to reach checkout

This incident has been resolved.

Resolved

BigCommerce·Search availability reduced and latency increased

This incident has been resolved.

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.

Prompt

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.

RSS

https://outages.cc/feed.xml?providers=bigcommerce

Slack

/feed subscribe https://outages.cc/feed.xml?providers=bigcommerce

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane