Skip to main content
BigCommerce

Elevated Response Times

Degraded Lasted 33m · started · BigCommerce's page

Level
confirmed
Worst impact
Degraded
Components
API & Webhooks, Storefront
Down Index
27of 100

What to do

  • Check whether you use BigCommerce API & Webhooks, Storefront. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 33m it lasted.

    Anything that failed between 2026-04-24 14:41 UTC and 2026-04-24 15:14 UTC may need a replay.
  • Subscribe to BigCommerce's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=bigcommerce works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from BigCommerce 3

  1. investigating

    Commerce engineers are currently investigating an issue with elevated response times. We will provide an update shortly.

    provider

  2. monitoring

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

    provider

  3. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-7cf1eea033

Is BigCommerce still down?

No, this incident was resolved 2026-04-24 15:14 UTC. For BigCommerce's live state, see https://down.guide/bigcommerce.

How long did it last?

33m, from 2026-04-24 14:41 UTC to 2026-04-24 15:14 UTC, by the times BigCommerce posted.

What was affected?

BigCommerce named API & Webhooks, Storefront.

What caused it?

BigCommerce hasn't published a root cause. If it does, it shows here.

Where does this come from?

BigCommerce's official status page, https://status.bigcommerce.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.