Skip to main content
BigCommerce

Increase in 401 status responses to Storefront GraphQL API

Degraded Lasted 25m · started · BigCommerce's page

Level
confirmed
Worst impact
Degraded
Components
API & Webhooks
Down Index
24of 100

What to do

  • Check whether you use BigCommerce API & Webhooks. 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 25m it lasted.

    Anything that failed between 2026-04-03 15:55 UTC and 2026-04-03 16:20 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. identified

    Starting at 12:30PM UTC, there is an increase of 401 responses to the Storefront GraphQL API. This issue is intermittent and impacts Stencil storefronts utilizing GraphQL

    provider

  2. investigating

    We are currently investigating this issue.

    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-734cbb3e97

Is BigCommerce still down?

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

How long did it last?

25m, from 2026-04-03 15:55 UTC to 2026-04-03 16:20 UTC, by the times BigCommerce posted.

What was affected?

BigCommerce named API & Webhooks.

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.