Operational BigCommerce status
bigcommerce.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread BigCommerce problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Google Cloud: no issues
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Storefront
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 23 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “High Rate of Cloudflare Challenge Pages”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside BigCommerce's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
BigCommerce may run on Google Cloud (inferred). We don't map other services that depend on BigCommerce. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on BigCommerce or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers BigCommerce may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with BigCommerce. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
High Rate of Cloudflare Challenge Pages
minor resolved · started · resolved
2 updates
- monitoring
The BigCommerce platform is currently experiencing an abnormally high volume of automated traffic being directed at stores. The engineering team has deployed a number of security rules to mitigate this traffic and to ensure reliability and performance of the platform is maintained. During this time merchants and shoppers may be presented with a Cloudflare challenge page as they navigate the store, which verifies they are a human user. The engineering team is continuing to refine the rules and and working to reduce frequency of these interruptions. We are also working closely with our vendor to further mitigate and improve the automatic classification of traffic. If you are experiencing issues managing your store through the Control Panel or API, we advise you to reach out the BigCommerce Support team for further assistance.
- resolved
This incident has been resolved.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.