Rewindex

CompaniesBigCommerceIncidents

BigCommerce: Inaccurate Analytics

MinorStatus: resolvedStarted Resolved (0 min)1 updatestatus.bigcommerce.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Dec 7, 2021 · 71 vendors, 77 incidents

BigCommerce’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +3 h 10 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher, Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerBigCommerce (this incident)posted +3 h 10 min
same windowAWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher,Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerBigCommerce (this incident)posted +3 h 10 min
BigCommerce is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>11 vendors, 9 blamed AWS<br/>Aptible, Firebolt, Honeycomb +8"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>16 vendors, 12 blamed AWS<br/>Maven Central, Pusher, Confluent +13"]:::blames
  root --> h4
  later["Later<br/>3 vendors, 2 blamed AWS<br/>Segment, Confluent, Doppler"]:::blames
  root --> later
  me["BigCommerce (this incident)<br/>posted +3 h 10 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    From 11:00 to 14:00 CST on December 7 an issue with an upstream vendor impacted the collection of visitor and product page view metrics. Analytics reports during this period will show inaccurate data. Order, revenue and all other metrics were unaffected. Following resolution of the upstream issue, metrics and analytics are now reporting as expected.

From BigCommerce’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.bigcommerce.com (opens in new tab).

BigCommerce profileRecent BigCommerce incidentsMarkdownJSON