outages.live
Live
BigCommerceIncident · 2026-10-27 05:29 UTC

Bolt payments are currently failing

ResolvedOfficial update

This incident has been resolved.

The latest update from BigCommerce.

State

Resolved

Started

6 d ago

2026-10-27 05:29 UTC

Lasted

2 h 12 min

until 2026-10-27 07:41 UTC

Worst impact

Partial outage

Timeline

2 updates
05:2906:0206:3507:0807:41
Partial outageUpdate postedTimes in UTC

Identified

2 h 12 min 100%

Updates

Times in UTC

As posted by BigCommerce

Resolved2026-10-27 07:41 UTC

This incident has been resolved.

Identified2026-10-27 05:29 UTC

Bolt payments are currently failing. The failure started when Bolt changed their domain from bolt.com to boltapp.com. Our team is working with Bolt to restore service. We will post an update as soon as we have more information.

Affected components

1
Checkout & Payment Processing

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

1.7× 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·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