Skip to content

Outage tracker / BigCommerce

Is BigCommerce down?

Short linkrlup.io/down/bigcommerce

I'm having a problem

Operationalchecked 2 minutes ago

We reached BigCommerce from all 4 regions we check.

Reachability verified

No outage recorded in the 12 days we have measured BigCommerce (since Aug 22, 2026).

our independent probeslive · checked Sep 3, 2026, 2:24 AM UTC
US-East977 msOperational
US-West912 msOperational
Europe298 msOperational
Asia-Pacific1120 msOperational
their status pagetheir claim, not our reading

BigCommerce reports: All systems operational (“All Systems Operational”)

from BigCommerce's own status page, checked Sep 3, 2026, 2:09 AM UTC
Our probes and BigCommerce's own status page agree: both show BigCommerce as reachable right now.

BigCommerce's own component breakdown, as they publish it

  • API & WebhooksOperational
  • AvalaraOperational
  • B2B Edition - APIOperational
  • Client PortalOperational
  • B2B Edition - DashboardOperational
  • BraintreeOperational
  • Checkout & Payment ProcessingOperational
  • Support CenterOperational
  • B2B Edition - Buyers PortalOperational
  • Braintree PayPal ProcessingOperational
  • Control PanelOperational
  • EmailOperational
  • Reporting & AnalyticsOperational
  • StorefrontOperational
  • StripeOperational

These are BigCommerce's components, named and scored by BigCommerce. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is BigCommerce's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

BigCommerce response time, by region

US-East
1.5sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.2s2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 1.3s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.5s2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.3s2026-09-02 UTC: p95 1.4s2026-09-03 UTC: p95 1.5s
Aug 5Aug 19Sep 3
US-West
864msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 558ms2026-08-23 UTC: p95 742ms2026-08-24 UTC: p95 586ms2026-08-25 UTC: p95 539ms2026-08-26 UTC: p95 543ms2026-08-27 UTC: p95 876ms2026-08-28 UTC: p95 958ms2026-08-29 UTC: p95 717ms2026-08-30 UTC: p95 651ms2026-08-31 UTC: p95 968ms2026-09-01 UTC: p95 763ms2026-09-02 UTC: p95 680ms2026-09-03 UTC: p95 864ms
Aug 5Aug 19Sep 3
Europe
335msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 341ms2026-08-23 UTC: p95 619ms2026-08-24 UTC: p95 699ms2026-08-25 UTC: p95 889ms2026-08-26 UTC: p95 713ms2026-08-27 UTC: p95 655ms2026-08-28 UTC: p95 586ms2026-08-29 UTC: p95 555ms2026-08-30 UTC: p95 516ms2026-08-31 UTC: p95 721ms2026-09-01 UTC: p95 551ms2026-09-02 UTC: p95 777ms2026-09-03 UTC: p95 335ms
Aug 5Aug 19Sep 3
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 494ms2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 926ms2026-08-25 UTC: p95 977ms2026-08-26 UTC: p95 874ms2026-08-27 UTC: p95 843ms2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 816ms2026-08-30 UTC: p95 893ms2026-08-31 UTC: p95 906ms2026-09-01 UTC: p95 1.0s2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 1.1s
Aug 5Aug 19Sep 3

Is it BigCommerce, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not BigCommerce -- it cannot diagnose BigCommerce's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 977msstatus code: 200checked: Sep 3, 2026, 2:00 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach BigCommerce normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 912msstatus code: 200checked: Sep 3, 2026, 2:02 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach BigCommerce normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 298msstatus code: 200checked: Sep 3, 2026, 2:24 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach BigCommerce normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 1120msstatus code: 200checked: Sep 3, 2026, 2:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach BigCommerce normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionBigCommerce is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionBigCommerce is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionBigCommerce is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionBigCommerce is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionBigCommerce is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionBigCommerce is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using BigCommerce, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for BigCommerce yet, which is not evidence that nothing is wrong.

Recent outages

Search document updates delays in Control Panel and Storefront experience, 2h 23mdeclared on their status page2026-09-01
Search document updates delays in Control Panel experience., 29mdeclared on their status page2026-08-27
B2B Ninja experiencing degradation in quote functionality, 5h 47mdeclared on their status page2026-08-26
B2B Ninja Add-To-Quote On Storefront Product Page timeouts, 1h 36mdeclared on their status page2026-08-26
Single Sign-On (Microsoft) login issue for subset of stores, 29mdeclared on their status page2026-08-25
Intermittent Availability Issues for Australian-hosted stores, 25mdeclared on their status page2026-08-21
Elevated Response Times for Australia-hosted stores, 30mdeclared on their status page2026-08-13
Intermittent Availability Issues, 13mdeclared on their status page2026-08-07

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring BigCommerce since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for BigCommerce covering any window you pick, with our measurements and BigCommerce's own claim at the time, side by side.

Full availability history for BigCommerce: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching BigCommerce, and again when they can reach it again. That is our own measurement from ten regions, not BigCommerce's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

BigCommerce uptime measured by RealUptimeLive, from this page's own readings.
[![BigCommerce uptime measured by RealUptime](https://realuptime.io/outages/bigcommerce/badge.svg?days=30)](https://realuptime.io/outages/bigcommerce)
<a href="https://realuptime.io/outages/bigcommerce"><img src="https://realuptime.io/outages/bigcommerce/badge.svg?days=30" alt="BigCommerce uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What BigCommerce's SLA implies, from our measurement

At or above your target

We measured none of downtime for BigCommerce over the 290h 26m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 17 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from BigCommerce's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primary
https://www.bigcommerce.com/
secondary
https://status.bigcommerce.com/api/v2/status.json
RealUptime is not affiliated with BigCommerce; the name identifies what we measured, and nothing here speaks for BigCommerce's own team. We send a single web request to BigCommerce from 4 regions on our own schedule and time the response. We do not see inside BigCommerce's systems, do not use an account or real transaction, and are not the same signal BigCommerce's own team has access to. Treat this as one external data point, not a verdict. What we check for BigCommerce proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. BigCommerce operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on August 22, 2026 (12 of 14 days so far, 4138 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

Adobe Creative CloudAirtableAsanaBingCanva