BigCommerce reported "QuickBooks Payments stores cannot transact" on its status page at 2026-10-05 18:45 UTC.

BigCommerce lists these components: Checkout & Payment Processing.

When did the incident start and end?

It started at 2026-10-05 18:45 UTC and ended at 2026-10-05 22:24 UTC. It lasted 3 h 40 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-10-05 18:45 UTC

QuickBooks Payments stores cannot transact

ResolvedOfficial update

incident resolved, merchants can disconnect and reconnect their quickbooks now

The latest update from BigCommerce.

State

Resolved

Started

27 d ago

2026-10-05 18:45 UTC

Lasted

3 h 40 min

until 2026-10-05 22:24 UTC

Worst impact

Partial outage

Timeline

6 updates

18:4519:4020:3521:3022:24

Partial outageUpdate postedTimes in UTC

Identified

2 h 20 min 63%

Investigating

1 h 12 min 33%

Monitoring

8 min 4%

Updates

Times in UTC

As posted by BigCommerce

Resolved2026-10-05 22:24 UTC

incident resolved, merchants can disconnect and reconnect their quickbooks now

Monitoring2026-10-05 22:16 UTC

we have deployed a fix and are monitoring the issue.

Identified2026-10-05 21:34 UTC

We are continuing to work on a fix for this issue.

Identified2026-10-05 20:02 UTC

The issue has been identified and a fix is being implemented.

Investigating2026-10-05 18:50 UTC

We are currently investigating this issue.

Identified2026-10-05 18:45 UTC

The issue has been identified and a fix is being implemented.

Affected components

Checkout & Payment Processing

BigCommerce in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 20 min

This incident

2.8× 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·High Rate of Cloudflare Challenge Pages

This incident has been resolved.

Resolvedresolved 3 d ago

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 6 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

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