Skip to main content

Is BigCommerce Down?

No — BigCommerce is up

Reachable from all 8 checked regions

Average response time: 340ms

Last checked · checks run every 6 hours

Official status page: https://status.bigcommerce.com

BigCommerce uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
353ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 24 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

24-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: 100.00% uptime, 16 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 31 checks
Aug 3: 100.00% uptime, 24 checks
Aug 4: 100.00% uptime, 48 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 31 checks
Aug 7: 100.00% uptime, 31 checks
Aug 8: 100.00% uptime, 24 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 31 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 23 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
232ms
DNS 37ms TCP 2ms TLS 7ms TTFB 208ms
arn
276ms
DNS 71ms TCP 1ms TLS 6ms TTFB 247ms
bom
360ms
DNS 179ms TCP 3ms TLS 7ms TTFB 335ms
nrt
378ms
DNS 148ms TCP 1ms TLS 6ms TTFB 366ms
ord
431ms
DNS 4ms TCP 3ms TLS 13ms TTFB 412ms
sin
495ms
DNS 321ms TCP 1ms TLS 8ms TTFB 479ms
sjc
226ms
DNS 2ms TCP 4ms TLS 10ms TTFB 198ms
syd
431ms
DNS 43ms TCP 1ms TLS 5ms TTFB 414ms
yyz
271ms
DNS 89ms TCP 1ms TLS 11ms TTFB 257ms

What BigCommerce does

BigCommerce hosts online stores, running the storefront customers browse, the checkout that takes their money and the control panel merchants work in. Larger retailers also use it headlessly, serving a custom front end from the BigCommerce API. When it is unavailable the shop is unreachable, so for a merchant this is revenue rather than inconvenience.

What an outage looks like

The storefront loads slowly or returns an error page for shoppers, and checkout fails at the payment step while the rest of the catalogue browses normally. The control panel will not load, so staff cannot edit products or view orders. API and webhook consumers stop receiving order events, leaving fulfilment systems idle. Headless stores can go blank even though the admin side is reachable.

What to do about it

Check status.bigcommerce.com, which separates Storefront, Checkout & Payment Processing, Control Panel, API & Webhooks, Email and Reporting, and also tracks the third party services embedded in checkout, including Stripe, Braintree and Avalara. Note BigCommerce states it may not post notices for short-duration issues or ones affecting only a small number of stores, so a green page does not rule out a problem with your store.

Is it down for everyone, or just you?

If this page says BigCommerce is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Shopify
Shopify
Stripe
Stripe
Square
Square
W
WP Engine

BigCommerce outage FAQ

My store is broken but the status page is green. Is that possible?
Yes, and BigCommerce says so directly. Its status page states that notices may not be posted for short-duration issues or for issues that only impact a small number of stores. A green page means no broad incident has been declared, not that every store is healthy. Independent measurement of your own storefront is what closes that gap.
Is checkout affected if the storefront is working?
It can be, because they are separate components. Checkout and payment processing is tracked apart from the storefront, so shoppers can browse the catalogue normally and then fail at the moment of payment. That combination is worse than a full outage commercially, since traffic keeps arriving and converting to nothing. Test an actual checkout rather than only loading the home page.
Could the problem be a third party rather than BigCommerce?
Often it is, and the status page reflects that by listing Stripe, Braintree, Braintree PayPal processing and Avalara as tracked third party services. A payment failure at checkout may be the processor rather than the platform, and a tax calculation error may be Avalara. Checking which of those is degraded points at the right vendor faster than opening a support ticket.
Do orders placed during an outage get lost?
Orders that completed are stored and appear in the control panel once it is reachable. The larger risk is orders that never completed, and fulfilment systems that missed their webhook. After recovery, reconcile recent orders against your downstream systems rather than assuming events replayed, because a missed webhook can leave a paid order sitting unfulfilled.
Does a control panel outage stop customers buying?
Not by itself. The control panel is the merchant admin interface and is tracked separately from the storefront, so shoppers can continue browsing and checking out while staff cannot log in to manage the store. The reverse is also true, which is why reading the individual components matters more than the overall banner.

How we measure this

  • We request BigCommerce's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where BigCommerce publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when BigCommerce goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required