outages.live
Live
BigCommerceIncident · 2026-10-28 03:11 UTC

High Rate of Cloudflare Challenge Pages

ResolvedOfficial update

This incident has been resolved.

The latest update from BigCommerce.

State

Resolved

Started

5 d ago

2026-10-28 03:11 UTC

Lasted

43 h 18 min

until 2026-10-29 22:29 UTC

Worst impact

Degraded

Timeline

2 updates
Oct 28Oct 28Oct 29Oct 29Oct 29
DegradedUpdate postedDates in UTC

Monitoring

43 h 18 min 100%

Updates

Times in UTC

As posted by BigCommerce

Resolved2026-10-29 22:29 UTC

This incident has been resolved.

Monitoring2026-10-28 03:11 UTC

The BigCommerce platform is currently experiencing an abnormally high volume of automated traffic being directed at stores. The engineering team has deployed a number of security rules to mitigate this traffic and to ensure reliability and performance of the platform is maintained. During this time merchants and shoppers may be presented with a Cloudflare challenge page as they navigate the store, which verifies they are a human user. The engineering team is continuing to refine the rules and and working to reduce frequency of these interruptions. We are also working closely with our vendor to further mitigate and improve the automatic classification of traffic. If you are experiencing issues managing your store through the Control Panel or API, we advise you to reach out the BigCommerce Support team for further assistance.

Affected components

1
Storefront

BigCommerce in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

36

Days with an incident

31

Median duration

1 h 20 min

This incident

33× 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 20 min
90 days agoToday

Other BigCommerce incidents

All incidents

BigCommerce·Degraded search availability across the platform

This incident has been resolved. All services are operational.

Resolvedresolved 5 d ago

BigCommerce·Bolt payments are currently failing

This incident has been resolved.

Resolvedresolved 5 d ago

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

This incident has been resolved.

Resolvedresolved 6 d ago

BigCommerce·Search availability reduced and latency increased

This incident has been resolved.

Resolvedresolved 8 d ago

BigCommerce·Delays in Real-Time Event Processing

This incident has been resolved.

Resolvedresolved 8 d ago

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