BigCommerce lists these components: Control Panel.

When did the incident start and end?

It started at 2026-09-01 23:43 UTC and ended at 2026-09-02 02:05 UTC. It lasted 2 h 23 min.

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.

BigCommerceIncident · 2026-09-01 23:43 UTC

Search document updates delays in Control Panel and Storefront experience

Q: What happened?

BigCommerce reported "Search document updates delays in Control Panel and Storefront experience" on its status page at 2026-09-01 23:43 UTC.

ResolvedOfficial update

This incident has been resolved.

The latest update from BigCommerce.

State

Resolved

Started

61 d ago

2026-09-01 23:43 UTC

Lasted

2 h 23 min

until 2026-09-02 02:05 UTC

Worst impact

Notice

Timeline

3 updates

23:4300:1800:5401:3002:05

NoticeUpdate postedTimes in UTC

Investigating

1 min 1%

Monitoring

2 h 22 min 99%

Updates

Times in UTC

As posted by BigCommerce

Resolved2026-09-02 02:05 UTC

This incident has been resolved.

Monitoring2026-09-01 23:44 UTC

We have identified the cause and are currently implementing a fix. We will continue monitoring recovery and provide another update as the queues return to normal levels.

Investigating2026-09-01 23:43 UTC

Starting August 31 at approximately 10:00 AM CT, we observed growing indexing queues affecting a subset of stores. During this period, newly created or updated entities may have taken up to 6 hours to become searchable in the Control Panel and storefront.

Affected components

Control Panel

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