BigCommerce

Affected: Control Panel, Storefront

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 09:23 UTC

   Commerce Engineering is investigating an issue causing delays in product search indexing for a subset of US stores. Our team is working to identify the root cause and restore normal indexing performance.

2. identified 2026-10-20 09:53 UTC

   Commerce Engineering has identified the cause of the search indexing delays affecting a subset of stores. As part of the mitigation, the affected functionality has been temporarily disabled for affected stores.

3. monitoring 2026-10-20 09:53 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-20 10:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-15 22:14 UTC

   Commerce engineers identified and mitigated an issue where a backlog of CRUD operations in entities delayed changes from appearing in storefront for up to 32 minutes . Between approximately 4:15 PM and 5:00 PM CT, merchants may have seen a delay in catalog updates. The backlog...

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Reporting & Analytics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-14 19:21 UTC

   BigCommerce Engineers are investigating an issue where analytics data is delayed in the Control Panel Analytics Reports for a subset of stores.

2. resolved 2026-10-14 20:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-14 18:32 UTC

   Some stores are seeing storefront searches return no results or miss products they should include. We've found the cause and are rolling out a fix.

2. monitoring 2026-10-14 19:53 UTC

   A fix has been deployed and search results are returning normally for affected stores. We're completing the rollout to the remaining regions and continuing to monitor.

3. resolved 2026-10-14 20:02 UTC

   A fix has been deployed and storefront search results are back to normal.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-14 09:08 UTC

   Commerce Engineers are investigating an issue impacting latency and availability of storefront search requests for a subset of US stores.

2. investigating 2026-10-14 09:09 UTC

   We are currently investigating this issue.

3. monitoring 2026-10-14 09:15 UTC

   A fix has been implemented and we are continuing to actively monitor search stability.

4. resolved 2026-10-14 09:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 00:25 UTC

   Commerce Engineers are investigating an issue impacting latency and availability of storefront search requests for a subset of US stores.

2. monitoring 2026-10-14 00:40 UTC

   A fix has been implemented and we are continuing to actively monitor search stability.

3. resolved 2026-10-14 00:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: API & Webhooks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 11:14 UTC

   BigCommerce engineers are investigating an issue with Management API requests to add products to carts. We'll share updates as more information becomes available.

2. identified 2026-10-12 11:21 UTC

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

3. monitoring 2026-10-12 12:00 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-12 12:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: API & Webhooks, Control Panel, Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 01:58 UTC

   Commerce engineers are investigating slow response times on some requests around product images.

2. monitoring 2026-10-12 02:34 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-10-12 02:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-10-08 17:34 UTC

   BigCommerce Engineers are investigating an issue impacting latency of storefront search requests for a subset of stores.

2. resolved 2026-10-08 17:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Checkout & Payment Processing

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-05 18:45 UTC

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

2. investigating 2026-10-05 18:50 UTC

   We are currently investigating this issue.

3. identified 2026-10-05 20:02 UTC

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

4. identified 2026-10-05 21:34 UTC

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

5. monitoring 2026-10-05 22:16 UTC

   we have deployed a fix and are monitoring the issue.

6. resolved 2026-10-05 22:24 UTC

   incident resolved, merchants can disconnect and reconnect their quickbooks now

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-05 16:40 UTC

   We are currently investigating this issue.

2. identified 2026-10-05 16:45 UTC

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

3. monitoring 2026-10-05 16:47 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-10-05 17:50 UTC

   Search errors are resolved, but we are addressing an indexing delay stemming from this incident. Recent changes for affected stores may take longer to appear in search.

5. resolved 2026-10-05 19:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 02:29 UTC

   BigCommerce engineers are currently investigating intermittent availability and degraded performance for Australian hosted stores. We will provide an update shortly.

2. monitoring 2026-10-02 03:23 UTC

   Engineers have deployed additionally capacity in this region and aren't continuing to monitor the availability and performance.

3. resolved 2026-10-02 05:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-01 21:00 UTC

   Commerce engineers identified the cause of search degradation on a subset or stores and have mitigated the issue.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-27 17:19 UTC

   Certain storefronts may be experiencing timeout errors for searches. We are currently investigating this issue.

2. investigating 2026-09-27 17:48 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-09-27 17:49 UTC

   Search availability has returned to normal availability. We are continuing to monitor this issue.

4. resolved 2026-09-27 18:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-26 18:30 UTC

   Certain storefronts may be experiencing errors for searches. We are currently investigating this issue

2. monitoring 2026-09-26 18:54 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-26 20:04 UTC

   Search availability is back to expected thresholds

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 20:16 UTC

   We have received reports of products appearing as "out of stock" on category pages. Commerce engineers are investigating this issue.

2. investigating 2026-09-23 21:32 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-23 22:30 UTC

   We are continuing to investigate this issue.

4. investigating 2026-09-23 23:13 UTC

   This issue has resolved.

5. resolved 2026-09-23 23:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: API & Webhooks

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-20 07:55 UTC

   BigCommerce engineers are currently investigating intermittent delays with webhooks delivery to a subset of stores. We will keep you informed with updates as they become available.

2. resolved 2026-09-20 09:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Client Portal, Support Center

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-16 09:15 UTC

   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.

2. investigating 2026-09-16 10:28 UTC

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

3. identified 2026-09-16 12:27 UTC

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

4. monitoring 2026-09-16 14:17 UTC

   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.

5. resolved 2026-09-16 15:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Control Panel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-14 22:09 UTC

   We are currently investigating this issue.

2. identified 2026-09-14 22:27 UTC

   Commerce engineers are continuing to work on a fix for this issue.

3. resolved 2026-09-14 23:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-04 09:19 UTC

   We are investigating delayed email delivery for some transactional emails, such as order confirmations and notifications. The delay affects recipients with Microsoft-hosted inboxes (Outlook.com, Microsoft 365). Other email providers are not affected. We will post an update as we...

2. monitoring 2026-09-04 11:59 UTC

   Commerce engineers have applied mitigations to improve email delivery to Microsoft-hosted inboxes (Outlook.com, Microsoft 365). Delivery rates are improving and we are continuing to monitor them.

3. resolved 2026-09-04 12:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Control Panel

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-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.

2. monitoring 2026-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.

3. resolved 2026-09-02 02:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Control Panel

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 12:16 UTC

   European merchants may experience minor delays in search document updates during Control Panel interaction.

2. monitoring 2026-08-27 12:20 UTC

   We identified the root cause, mitigated the issue, and will continue to monitor the situation.

3. resolved 2026-08-27 12:44 UTC

   The issue has been fully mitigated, and users should no longer be affected.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 12:38 UTC

   We are currently investigating this issue.

2. investigating 2026-08-26 14:07 UTC

   We are continuing to investigate this issue.

3. investigating 2026-08-26 15:29 UTC

   We are continuing to investigate this issue.

4. resolved 2026-08-26 18:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 10:14 UTC

   We are currently investigating an issue affecting stores using B2B Ninja, where users are unable to add products to a quote from the storefront.

2. investigating 2026-08-26 11:08 UTC

   We are continuing to investigate this issue.

3. resolved 2026-08-26 11:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Control Panel

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-08-25 06:56 UTC

   We are currently investigating an issue with Single Sign-On (SSO) login through Microsoft Azure AD. We will post an update when we have more information available.

2. identified 2026-08-25 07:23 UTC

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

3. resolved 2026-08-25 07:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: API & Webhooks, Control Panel, Storefront

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-21 00:35 UTC

   BigCommerce engineers are currently investigating intermittent availability issues with a subset of stores. We will provide an update shortly.

2. monitoring 2026-08-21 00:40 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-21 01:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: API & Webhooks, Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-13 10:01 UTC

   BigCommerce engineers are currently investigating an issue with elevated response times for Australia-hosted stores. We will provide an update shortly.

2. identified 2026-08-13 10:17 UTC

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

3. monitoring 2026-08-13 10:24 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-13 10:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: API & Webhooks, Control Panel, Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-07 17:11 UTC

   Commerce engineers are currently investigating intermittent availability issues with a subset of stores. We will provide an update shortly.

2. monitoring 2026-08-07 17:15 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-07 17:24 UTC

   Commerce engineers were alerted to an increase in error rates for a subset of stores starting at 17:49 UTC. Action was taken and error rates returned to normal at 18:05 UTC. All systems are fully operational.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-04 15:32 UTC

   Commerce Engineers are investigating an issue impacting PayPal Account Vaulted instrument creation when the Credit Cards feature is disabled in the PayPal Commerce and BigCommerce Payments integrations.

2. identified 2026-08-04 15:56 UTC

   Commerce Engineers have found the root cause of this issue for both the PayPal Commerce and BigCommerce Payments integrations, and are developing a fix.

3. identified 2026-08-04 18:21 UTC

   Commerce engineers are continuing to work on a fix for this issue.

4. identified 2026-08-04 20:19 UTC

   Commerce engineers have identified a fix for this issue.

5. resolved 2026-08-04 21:28 UTC

   The fix for this issue has been deployed to production and PayPal vaulting is working as expected.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-28 20:11 UTC

   Commerce Engineers are investigating an issue that is preventing merchants from submitting quotes on B2B Ninja.

2. monitoring 2026-07-28 20:43 UTC

   A fix has been implemented and we are continuing to monitor.

3. resolved 2026-07-28 20:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Control Panel

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-23 23:02 UTC

   Investigating - Commerce Engineers are currently investigating an issue around out of memory error for catalog import/export impacting a subset of stores.

2. monitoring 2026-07-23 23:57 UTC

   Monitoring – Commerce Engineers have mitigated an out-of-memory issue impacting Catalog Import/Export for a subset of stores. We are currently observing system stability before marking the incident as resolved.

3. resolved 2026-07-24 10:32 UTC

   Commerce Engineers identified that additional remediation was required during the monitoring period. The issue affecting Catalog Import/Export for a subset of stores has now been fully resolved, and the system is operating normally.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Control Panel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-21 20:20 UTC

   Commerce Engineers are currently investigating an issue causing intermittent errors in PageBuilder and some other aspects of the control panel. Storefronts and the checkout experience are not affected.

2. resolved 2026-07-21 23:09 UTC

   Commerce Engineers identified and fixed the root cause of the intermittent errors affecting the control panel. This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Checkout & Payment Processing

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-16 17:25 UTC

   Commerce Engineers have identified an issue with Paypal payment gateways reenabling themselves on some stores checkouts, and are actively working on a fix.

2. identified 2026-07-16 17:26 UTC

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

3. resolved 2026-07-16 21:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Checkout & Payment Processing

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-16 00:39 UTC

   Commerce engineers are aware of an issue causing transaction processing errors for merchants using the Cybersource V2 payment provider. The issue has been identified as an outage with the provider. You can follow the provider's status here:...

2. monitoring 2026-07-16 05:43 UTC

   Cybersource have added mitigation in place and transactions have started to process as expected. Our team is actively monitoring the provider's progress and will provider updates as they are available.

3. resolved 2026-07-16 10:33 UTC

   Cybersource has mitigated the issue on their end, but monitoring. We are no longer seeing any issues with payment processing

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-10 21:11 UTC

   BigCommerce engineers are currently investigating availability issues with a subset of stores. We will provide an update shortly.

2. resolved 2026-07-11 00:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Checkout & Payment Processing

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-09 22:54 UTC

   Commerce Engineers are investigating an issue affecting some stores using shipping zones configured for a selection of states/provinces, which may cause errors on the checkout page. Our team is actively investigating and working on a fix.

2. investigating 2026-07-09 22:56 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-10 01:14 UTC

   Commerce engineers identified the cause of checkout errors affecting some stores using state/province shipping zones. We'll confirm once fully resolved.

4. monitoring 2026-07-10 02:51 UTC

   A fix has been implemented and we are monitoring the result.

5. resolved 2026-07-10 03:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-07-08 05:27 UTC

   We identified an issue where a subset of stores may see unexpected Staff Action Log entries generated by an API-driven background process. These entries are display-only logging artifacts and do not reflect staff user activity or changes made to the store. Some entries may...

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: B2B Edition - API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-06 18:01 UTC

   Commerce engineers were alerted to an issue with B2B Edition from 17:41 to 17:49 UTC. Commerce engineers are investigating the root cause but for now the issue has been resolved.

2. resolved 2026-07-06 22:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: B2B Edition - Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-06 16:08 UTC

   Commerce engineers were alerted to an issue with B2B Edition and are currently investigating. We will provide updates as they become available.

2. resolved 2026-07-06 16:23 UTC

   Commerce engineers have resolved the issue impacting B2B Edition from 4:25 pm UTC to 5:05 pm UTC and all services are fully operational.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-06 10:00 UTC

   Between 10:02 and 10:17 UTC on July 6, there were short periods of increased HTTP 500 errors affecting storefront and API requests.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-03 03:14 UTC

   Commerce engineers were alerted into increased error rate for subset of stores in US from 2:00 AM UTC to 3:08 AM UTC. The issue has now been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-03 00:33 UTC

   Commerce engineers are looking into increased error rate for subset of stores in AU.

2. monitoring 2026-07-03 00:45 UTC

   Commerce engineers have applied a fix and are monitoring the error rates

3. resolved 2026-07-03 00:56 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Email

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-29 10:00 UTC

   We are currently investigating this issue.

2. identified 2026-06-30 16:11 UTC

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

3. identified 2026-06-30 17:50 UTC

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

4. identified 2026-06-30 18:24 UTC

   We've escalated the issue to our third party email service. We're working with them to get this resolved.

5. identified 2026-06-30 22:59 UTC

   We are continuing to work with the third party email service to get this resolved. The escalation is still ongoing.

6. identified 2026-07-01 01:36 UTC

   The issue is still under active escalation with the third-party email service provider. We continue to work closely with their team and will share updates as they become available.

7. identified 2026-07-01 05:15 UTC

   The issue remains under active escalation with the third-party email provider. We're working with their team and will provide updates as soon as they are available.

8. monitoring 2026-07-01 06:00 UTC

   The issue has been identified and resolved by the third party email service and functionality is restored. We're working on re-triggering the emails that were not sent during this outage.

9. resolved 2026-07-01 16:00 UTC

   The email issue affecting B2B Ninja is resolved and quotes are sending normally again. Quotes sent during the outage (June 29, 2026, 10:00 PM UTC – July 1, 2026, 6:00 AM UTC) may not have gone out. They appear in the dashboard, but the customer may see them stuck as "pending" on...

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-24 19:50 UTC

   Commerce Engineers have identified an issue impacting a small subset of merchants using custom search integrations like Klevu.

2. resolved 2026-06-24 20:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-23 15:50 UTC

   Commerce Engineers are investigating an issue impacting latency of storefront search requests for a subset of US stores.

2. monitoring 2026-06-23 16:33 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-23 16:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Reporting & Analytics

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-23 15:29 UTC

   Commerce Engineers are actively monitoring increased latency from the Meta API affecting Meta CAPI (Conversions API) integrations. Meta CAPI events may be delivered later than usual while the backlog clears. Events are continuing to process and we are not seeing data loss at...

2. monitoring 2026-06-23 15:52 UTC

   Commerce Engineers continue to monitor increased latency from the Meta API affecting Meta CAPI (Conversions API) integrations. Event delivery remains delayed for some customers, but events are continuing to process and we are not seeing data loss. Processing capacity has been...

3. resolved 2026-06-23 16:08 UTC

   Meta CAPI event delivery has caught up and is no longer delayed. Commerce Engineers will continue monitoring Meta API latency, which remains higher than normal, but event delivery has returned to normal and we are not seeing data loss.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-23 03:57 UTC

   Commerce Engineers have identified and resolved an issue that prevented shopper events from being captured between 8:38 PM and 10:20 PM CT. Systems are now functioning normally, and current events are processing correctly. Please note that Control Panel Analytics Reports and the...

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-18 22:20 UTC

   BigCommerce Engineers are investigating an issue impacting availability and latency of storefront search requests for a subset of stores in Australia.

2. resolved 2026-06-18 22:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Checkout & Payment Processing

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-17 06:25 UTC

   BigCommerce engineers are currently investigating an issue affecting credit card payments for cardholders using Bank of New Zealand (BNZ) provider, particularly during 3D Secure (3DS) authentication. Affected shoppers may be unable to complete checkout on impacted stores.

2. identified 2026-06-17 06:42 UTC

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

3. resolved 2026-06-17 06:47 UTC

   This issue has now been resolved.

Excerpts are shortened. Read the full incident on BigCommerce's status page.

Affected: Storefront

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-16 18:57 UTC

   BigCommerce engineers are investigating reports of issues with currency changes on storefronts.

2. identified 2026-06-16 19:32 UTC

   BigCommerce engineers have identified the issue and are working to resolve it.

3. investigating 2026-06-16 20:02 UTC

   BigCommerce engineers are investigating this issue.

4. resolved 2026-06-16 20:12 UTC

   A fix for this issue has been rolled out to all stores.

Excerpts are shortened. Read the full incident on BigCommerce's status page.