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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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

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

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.

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

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

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

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.

1. resolved 2026-06-16 15:21 UTC

   A fix has been deployed and exports are now completing normally.

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

1. resolved 2026-06-12 15:35 UTC

   This incident has been resolved.

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

1. resolved 2026-06-11 20:30 UTC

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

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

1. resolved 2026-06-11 01:59 UTC

   This incident has been resolved.

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

1. resolved 2026-06-10 18:30 UTC

   Between 18:30 UTC and 18:41 UTC, some stores experienced elevated HTTP 500 errors on the storefront and API.

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

1. resolved 2026-06-08 03:05 UTC

   This incident has been resolved

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

1. resolved 2026-06-05 13:30 UTC

   Between 2:37p-3:25p UTC a subset of stores may have experienced errors, delays, or missing options when using product filters and category navigation. Commerce Engineers deployed a fix and all storefront navigation and filtering systems were fully operational as of 3:25p UTC. We...

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

1. resolved 2026-06-02 13:00 UTC

   At 13:13 UTC Commerce Engineers received reports of product details not rendering properly on some product pages. After investigation the problematic release was identified and reverted, restoring functionality at 13:57 UTC. All affected storefronts should now be properly...

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

1. resolved 2026-05-28 19:38 UTC

   This incident has been resolved.

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

1. resolved 2026-05-28 08:00 UTC

   Between 08:12 UTC and 08:19 UTC, some stores experienced elevated HTTP 500 errors on the storefront and API.

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

1. resolved 2026-05-28 07:20 UTC

   This incident has been resolved.

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

1. resolved 2026-05-28 01:17 UTC

   This issue has been resolved.

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

1. resolved 2026-05-23 16:00 UTC

   At 16:10 UTC on May 23, for a period of 30 seconds, there was an elevated error rate for a subset of stores in the US region. Storefront, Control Panel, and API traffic were affected.

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

1. resolved 2026-05-22 14:04 UTC

   This incident has been resolved.

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

1. resolved 2026-05-21 18:18 UTC

   This incident has been resolved.

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

1. resolved 2026-05-19 08:00 UTC

   This incident has been resolved.

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

1. resolved 2026-05-18 04:26 UTC

   This incident has been resolved.

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

1. resolved 2026-05-14 19:00 UTC

   This incident is resolved.

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

1. resolved 2026-05-14 19:08 UTC

   This incident has been resolved.

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

1. resolved 2026-05-14 10:00 UTC

   A subset of payment capture events were failing for a subset of stores from May 14 @ 10:00 UTC until May 17 @ 14:00 UTC. The root cause has been found and fixed.

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

1. resolved 2026-05-04 17:09 UTC

   Commerce engineers observed an availability issue with a subset of stores beginning at approximately 17:43 UTC, which caused some storefront requests to fail. The issue was resolved at 17:45 AM UTC and all services are fully operational.

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

1. resolved 2026-05-04 15:15 UTC

   Commerce engineers observed an availability issue with a subset of stores beginning at approximately 4:06 PM UTC, which caused some storefront requests to fail. The issue was resolved at 4:08 PM UTC and all services are fully operational.

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

1. resolved 2026-05-03 22:35 UTC

   A fix for price modifier rules not applying as expected has been implemented. If you continue to see modifier rules not applying correctly on your store, please contact BigCommerce Support so we can take a closer look.

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

1. resolved 2026-05-01 03:18 UTC

   This incident has been resolved.

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

1. resolved 2026-04-28 23:44 UTC

   Commerce engineers observed an availability issue with a subset of stores beginning at approximately 00:19 UTC, which caused some storefront requests to fail. The issue was resolved at 00:25 UTC and all services are fully operational.

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

1. resolved 2026-04-24 15:14 UTC

   This incident has been resolved.

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

1. resolved 2026-04-24 15:07 UTC

   This incident has been resolved.

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

1. resolved 2026-04-23 15:48 UTC

   This incident has been resolved.

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

1. resolved 2026-04-22 20:38 UTC

   This incident has been resolved.

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

1. resolved 2026-04-22 01:39 UTC

   This incident has been resolved.

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

1. resolved 2026-04-21 14:30 UTC

   On April 21, 2026 at 14:37 UTC, Commerce engineers were alerted to an issue with Stencil storefronts. After investigation it was determined that a small number of Stencil storefronts using a custom layout template for their homepage experienced an issue where the homepage...

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

1. resolved 2026-04-13 16:27 UTC

   Commerce engineers were alerted to an increase in error rates B2B customer logins and API calls. Action was taken and error rates have returned to normal at 15:51 UTC. All systems are fully operational.

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

1. resolved 2026-04-09 17:24 UTC

   External PayPal team identified an issue and fixed on their side, so PPCP 3DS authentication flow should work as expected on the UK stores

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

1. resolved 2026-04-03 16:20 UTC

   This incident has been resolved.

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

1. resolved 2026-03-25 20:02 UTC

   This issue has been resolved and all systems are fully operational.

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

1. resolved 2026-03-17 12:01 UTC

   This issue has been resolved.

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

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

   Commerce engineers observed an availability issue with a subset of stores beginning at approximately 10:30 AM UTC, which caused some storefront requests to fail. The issue was resolved at 11:15 AM UTC and all services are fully operational.

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

1. resolved 2026-03-05 18:24 UTC

   Commerce Engineers have resolved the delay with Meta CAPI event delivery caused by the Meta Marketing API incident. Event processing has returned to normal rates, and backlog for affected stores has been cleared.

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

1. resolved 2026-03-04 20:31 UTC

   This incident has been resolved.

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

1. resolved 2026-02-27 01:38 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 00:29 UTC, which caused some storefront and API requests to fail. Storefront errors were mitigated at 00:32 UTC. The issue was resolved for API requests at 01:00 UTC and all...

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

1. resolved 2026-02-25 01:05 UTC

   This incident has been resolved.

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

1. resolved 2026-02-13 12:31 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 4:42 UTC, which caused some storefront and API requests to fail. The issue was resolved at 5:26 UTC and all services are fully operational.

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

1. resolved 2026-02-10 11:55 UTC

   This incident has been resolved.

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

1. resolved 2026-02-08 16:00 UTC

   Commerce engineers were alerted to an increase in error rates for a subset of stores on both storefronts and control panels starting at 16:18 UTC. Action was taken and error rates returned to normal at 16:22 UTC. All systems are fully operational.

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

1. resolved 2026-02-03 16:30 UTC

   Commerce engineers were alerted to an increase in error rates for a subset of stores on both storefronts and control panels starting at 16:25 UTC. Action was taken and error rates returned to normal at 16:41 UTC. All systems are fully operational.

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

1. resolved 2026-01-31 16:20 UTC

   This incident has been resolved.

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

1. resolved 2026-01-30 04:27 UTC

   The issue with our support center has been resolved.

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

1. resolved 2026-01-29 22:27 UTC

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

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

1. resolved 2026-01-29 11:30 UTC

   Commerce engineers identified substantially slower checkout page response times for a subset of stores from approximately 11:30 to 16:00 UTC. The issue has been resolved and all systems are fully operational.

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

1. resolved 2026-01-22 20:04 UTC

   This issue has been resolved.

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

1. resolved 2026-01-22 13:34 UTC

   This incident has been resolved.

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

1. resolved 2026-01-12 23:17 UTC

   This has been resolved.

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

1. resolved 2026-01-08 16:49 UTC

   Commerce engineers were alerted to an issue with Catalyst checkouts at 15:14 UTC. The issue was resolved at 16:20 UTC and all systems are fully operational.

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

1. resolved 2026-01-06 18:00 UTC

   This incident has been resolved.

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

1. resolved 2025-12-30 14:18 UTC

   This incident has been resolved.

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

1. resolved 2025-12-29 03:21 UTC

   Commerce engineers have identified the issue and rolled out a fix for it, we have verified the functionality has been restored.

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

1. resolved 2025-12-25 19:00 UTC

   This incident has been resolved.

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

1. resolved 2025-12-22 15:55 UTC

   This incident has been resolved.

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

1. resolved 2025-12-05 09:21 UTC

   This incident has been resolved.

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

1. resolved 2025-11-28 23:24 UTC

   This incident has been resolved.

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

1. resolved 2025-11-28 19:41 UTC

   This incident has been resolved.

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

1. resolved 2025-11-18 15:33 UTC

   This incident has been resolved.

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

1. resolved 2025-11-13 17:24 UTC

   BigCommerce engineers were alerted to elevated storefront errors starting around 15:35 UTC. The issue was resolved at 17:05 UTC and all systems are fully operational.

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

1. resolved 2025-11-11 19:28 UTC

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

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

1. resolved 2025-11-11 17:59 UTC

   BigCommerce engineers were notified of an issue causing HTTP 503 errors over the API at approximately 11:57 UTC. A fix completed rolling out at 17:27 UTC and we no longer observed HTTP 503 errors over the API and all systems are fully operational.

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

1. resolved 2025-11-03 16:11 UTC

   BigCommerce engineers were notified of an issue where a subset of webhooks were not being delivered to APAC region stores at approximately 13:00 UTC. A fix was implemented at 15:45 UTC and webhooks delivery was restored. Any webhooks that were not delivered during this time are...

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

1. resolved 2025-10-30 19:40 UTC

   Commerce engineers were alerted to an issue with logging into store's control panel starting at 16:34. This was resolved at 17:31 UTC. All systems are currently operational.

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

1. resolved 2025-10-24 18:59 UTC

   This incident has been resolved.

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

1. resolved 2025-10-20 22:25 UTC

   Commerce engineers observed an elevated error rate affecting a subset of stores beginning at 21:40 UTC. Action was taken and at 21:55 error rates have returned to normal.

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

Names an upstream provider: AWS.

1. resolved 2025-10-21 02:52 UTC

   All Twilio services impacted by the AWS outage affecting the US-1 Region have recovered and are operating as intended.

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

1. resolved 2025-10-14 12:55 UTC

   This incident has been resolved.

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

1. resolved 2025-10-13 15:40 UTC

   This incident has been resolved.

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

1. resolved 2025-10-12 15:41 UTC

   This incident has been resolved.

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

1. resolved 2025-10-07 23:59 UTC

   This incident has been resolved.

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

1. resolved 2025-09-19 19:36 UTC

   This incident has been resolved

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

1. resolved 2025-09-21 00:02 UTC

   This incident has been resolved.

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

1. resolved 2025-09-12 22:50 UTC

   Commerce engineers have resolved the issue with Required Form Fields impacting B2B Custom Checkout.

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

1. resolved 2025-08-19 23:41 UTC

   This incident has been resolved.

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

1. resolved 2025-08-20 01:50 UTC

   This incident has been resolved.

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

1. resolved 2025-08-06 22:15 UTC

   This incident has been resolved.

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

1. resolved 2025-07-18 21:41 UTC

   BigCommerce engineers observed an availability issue affecting both storefront and API calls beginning at approximately 21:45 UTC. The issue was resolved at 22:09 UTC and all services are fully operational.

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

1. resolved 2025-07-11 14:11 UTC

   This incident has been resolved.

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

1. resolved 2025-07-08 03:19 UTC

   This incident has been resolved.

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

1. resolved 2025-07-03 16:16 UTC

   The incident has been resolved.

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

1. resolved 2025-07-01 18:59 UTC

   This incident has been resolved.

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

1. resolved 2025-06-24 18:01 UTC

   BigCommerce engineers observed an issue with authorized payments being delayed when captured starting around 14:30 UTC. The issue was resolved at 17:30 UTC and all systems are fully operational.

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

1. resolved 2025-06-24 15:50 UTC

   BigCommerce engineers observed an availability issue with a subset of stores in the EU region beginning at approximately 15:01 UTC, which caused some storefront requests to fail. The issue was resolved at 15:26 UTC and all services are fully operational.

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

1. resolved 2025-06-23 12:43 UTC

   This incident has been resolved.

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

1. resolved 2025-06-17 19:30 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 19:45PM UTC, which caused some storefront requests to fail. The issue was resolved at 21:00PM UTC and all services are fully operational.

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

1. resolved 2025-06-12 22:25 UTC

   BigCommerce engineers were alerted to certain CDN assets failing to load intermittently on storefronts as a result of our cloud provider outage. Engineers have implemented a fix and all services are now operational.

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

1. resolved 2025-06-12 20:46 UTC

   This incident has been resolved.

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

1. resolved 2025-06-12 08:11 UTC

   BigCommerce engineers have fixed the stores identified, and we receive no more new reports.

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

1. resolved 2025-06-06 15:34 UTC

   Increased crawler traffic was causing intermittent slowness and errors on merchant stores. BigCommerce engineers blocked some of the traffic and deployed a fix to resolve the performance problems

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

1. resolved 2025-05-22 17:15 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 4:10 PM UTC, which caused some storefront and API requests to fail. The issue was resolved at 4:26 PM UTC and all services are fully operational.

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

1. resolved 2025-05-22 15:49 UTC

   This incident has been resolved.

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

1. resolved 2025-05-22 15:13 UTC

   This incident has been resolved.

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

1. resolved 2025-05-22 14:53 UTC

   This incident has been resolved.

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

1. resolved 2025-05-22 13:30 UTC

   This incident has been resolved.

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

1. resolved 2025-05-22 00:44 UTC

   This incident has been resolved.

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

1. resolved 2025-05-21 04:00 UTC

   Some UPS Ready customers have had their UPS Ready credentials invalidated and will need to Disconnect and re-Connect their account to enable UPS rates to continue showing in Checkout. Engineers are working on a control panel and email notification message for affected customers.

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

1. resolved 2025-05-19 21:50 UTC

   This incident has been resolved.

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

1. resolved 2025-05-14 23:05 UTC

   This incident has been resolved.

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

1. resolved 2025-05-12 11:20 UTC

   This incident has been resolved.

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

1. resolved 2025-05-08 16:19 UTC

   This incident has been resolved.

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

1. resolved 2025-05-07 00:19 UTC

   BigCommerce engineers have identified the issue to be custom form field, and verified that configuring custom form field as "optional" instead of "required" should solve the issue and allow payment proceed.

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

1. resolved 2025-05-06 18:32 UTC

   This incident has been resolved.

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

1. resolved 2025-05-05 17:51 UTC

   This incident has been resolved.

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

1. resolved 2025-04-10 21:00 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 21:05 UTC, which caused some storefront and API requests to fail. The issue was resolved at 21:11 UTC and all services are fully operational.

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

1. resolved 2025-04-05 00:26 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 23:55 UTC affecting API, storefront, and control panel requests. The issue was resolved at 00:18 UTC and all services are fully operational.

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

1. resolved 2025-03-25 17:57 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 17:27 UTC affecting API, storefront, and control panel requests. The issue was resolved at 17:46 UTC and all services are fully operational.

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

1. resolved 2025-03-25 16:55 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 15:58 UTC affecting API, storefront, and control panel requests. The issue was resolved at 16:44 UTC and all services are fully operational.

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

1. resolved 2025-03-22 15:59 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 15:35 UTC, which caused some storefront requests to fail. The issue was resolved at 15:45 UTC and all services are fully operational.

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

1. resolved 2025-03-20 14:52 UTC

   BigCommerce engineers observed an issue with B2B Edition Buyer Portal starting around 13:00 UTC which caused certain assets to fail. The issue was resolved at 14:37 UTC and the B2B Edition Buyer Portal is fully operational.

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

1. resolved 2025-03-13 15:32 UTC

   This incident has been resolved.

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

1. resolved 2025-03-06 23:20 UTC

   Between 22:36 and 22:48 UTC (16:36 and 16:48 Central Time) a subset of stores experienced up to 4 minutes of elevated HTTP 500 errors and slow response times. BigCommerce engineers have resolved the issue.

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

1. resolved 2025-03-05 22:26 UTC

   This incident has been resolved.

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

1. resolved 2025-03-05 18:52 UTC

   BigCommerce engineers observed an issue beginning at approximately 18:27 UTC, which caused intermittent availability issues for a subset of stores. The problem was resolved at 18:37 UTC and all services are fully operational.

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

1. resolved 2025-03-05 14:38 UTC

   This incident has been resolved.

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

1. resolved 2025-03-04 16:11 UTC

   BigCommerce engineers observed an availability issue with a subset of store checkouts at approximately 11:35 AM UTC, which caused some checkout requests to fail. The issue was resolved at 3:55 PM UTC and all services are fully operational.

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

1. resolved 2025-02-27 19:03 UTC

   This incident has been resolved.

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

1. resolved 2025-02-25 17:09 UTC

   BigCommerce engineers observed an issue beginning at approximately 15:24 UTC, which delayed webhooks delivery for a subset of stores. The issue was resolved at 17:01 UTC and all services are fully operational.

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

1. resolved 2025-02-14 17:12 UTC

   BigCommerce engineers observed an issue beginning at approximately 12:47 UTC, which impacted product images on the store Control Panel for a subset of stores. The issue was resolved at 17:10 UTC and all services are fully operational.

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

1. resolved 2025-02-13 06:31 UTC

   BigCommerce engineers have confirmed the issue has resolved

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

1. resolved 2025-02-13 19:32 UTC

   BigCommerce engineers observed an issue beginning at approximately 17:10 UTC, which impacted cart redirect urls on a small subset of stores using GraphQL. The issue was resolved at 23:20 UTC that day and all services are fully operational.

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

1. resolved 2025-02-11 23:02 UTC

   BigCommerce engineers observed an issue with a subset of stores beginning at approximately 4:05 AM UTC, which prevented the creation of Endicia shipping labels. The issue was resolved at 10:48PM UTC and all services are fully operational.

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

1. resolved 2025-02-07 03:20 UTC

   This incident has been resolved.

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

1. resolved 2025-01-31 15:00 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 3:25 PM UTC, which caused some storefront requests to fail. The issue was resolved at 3:33PM UTC and all services are fully operational.

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

1. resolved 2025-01-30 13:20 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 12:16PM UTC, which caused some storefront requests to fail. The issue was resolved at 13:07PM UTC and all services are fully operational.

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

1. resolved 2025-01-30 09:31 UTC

   This incident has been resolved.

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

1. resolved 2025-01-21 22:32 UTC

   This incident has been resolved.

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

1. resolved 2025-01-15 17:36 UTC

   BigCommerce engineers observed an availability issue with a subset of stores beginning at approximately 12:16PM UTC, which caused some storefront and API requests to fail. The issue was resolved at 12:27PM UTC and all services are fully operational.

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

1. resolved 2025-01-13 19:31 UTC

   This incident has been resolved.

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

1. resolved 2025-01-02 17:30 UTC

   BigCommerce engineers observed an availability issue with a subset of stores starting at approxiumately 17:40 UTC, which caused some storefront and API requests to fail. The issue was resolved at 17:45 UTC and all services are fully operational.

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

1. resolved 2024-12-20 20:11 UTC

   This incident has been resolved.

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

1. resolved 2024-12-20 00:00 UTC

   A subset of stores experience elevated HTTP 500 error rates between 00:01 and 00:48 UTC. BigCommerce engineers have fixed the cause of these errors.

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

1. resolved 2024-12-19 14:48 UTC

   This incident has been resolved.

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

1. resolved 2024-12-18 21:49 UTC

   Beginning 13:50 CST BigCommerce engineers were alerted to degraded storefront and control panel search performance for a subset of stores. The root cause has been identified and resolved at 15:26 CT. All services are now operational.

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

1. resolved 2024-12-16 09:31 UTC

   This incident has been resolved.

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

1. resolved 2024-12-12 03:37 UTC

   The Meta outage has been resolved. BC Engineering will now work to re-send the failed events.

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

1. resolved 2024-12-11 05:40 UTC

   This incident has been resolved.

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

1. resolved 2024-12-10 22:51 UTC

   BigCommerce Engineers identified an issue affecting storefront and API services for a subset of stores beginning at 22:29 UTC and ending at 22:34 UTC. BigCommerce Engineers have resolved the issue and all services are now available.

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

1. resolved 2024-12-04 13:26 UTC

   This incident has been resolved.

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

1. resolved 2024-11-28 10:38 UTC

   This incident has been resolved.

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

1. resolved 2024-11-26 20:02 UTC

   Our Knowledge Base articles are accessible once again.

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

1. resolved 2024-11-18 13:46 UTC

   This incident has been resolved.

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

1. resolved 2024-11-13 17:42 UTC

   BigCommerce Engineers identified an issue affecting storefront and API services for a subset of stores beginning at 16:30 UTC and ending at 17:20 UTC. BigCommerce Engineers have resolved the issue and all services are now available.

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

1. resolved 2024-11-12 18:23 UTC

   This incident has been resolved.

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

1. resolved 2024-11-12 11:08 UTC

   The issue has been resolved

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

1. resolved 2024-11-05 12:35 UTC

   This incident has been resolved.

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