Contact Center System Outage
This incident has been resolved.
The latest update from BigCommerce.
State
Resolved
Started
47 d ago
2026-09-16 09:15 UTC
Lasted
6 h 27 min
until 2026-09-16 15:42 UTC
Worst impact
Major outage
Timeline
5 updatesInvestigating
3 h 12 min 50%
Identified
1 h 49 min 28%
Monitoring
1 h 25 min 22%
Updates
Times in UTCAs posted by BigCommerce
This incident has been resolved.
Our third party service provider has indicated the incident is resolved. While the Support Center appears operational, we will continue to monitor. Users should be able to contact our Support team through Phone, Chat, or Web.
The fix being rolled out by our service provider is progressing region by region. Customers may experience delays or intermittent errors when contacting us via Phone, Chat, or Web. If your issue is not urgent, we continue to encourage you to submit a web case at support.bigcommerce.com and we will respond as soon as possible. Thank you for your patience.
Our contact center continues to experience technical difficulties. Our service provider is working on a fix to resolve this issue and restore services. You may experience delays or intermittent errors when contacting us via Phone, Chat, or Web. If your issue is not urgent, we encourage you to submit a web case at support.bigcommerce.com and we will respond as soon as possible.
Our contact center is experiencing technical difficulties due to issues with our service provider. Phone, Chat, and Web cases are temporarily unavailable. We will resume operations as soon as possible.
Affected components
4BigCommerce in the last 90 days
Full historyIncidents in 90 days
36
Days with an incident
30
Median duration
1 h 20 min
This incident
4.9× 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