Skip to content
Back to BigCommerceIncident Postmortem
BigCommerce logo

BigCommerce

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

BigCommerce: vendor-reported major incident on September 23 (tracked 2h 59m)

Sep 23, 08:59 PM → Sep 23, 11:59 PM · 2h 59m · high

BigCommerce reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 2h 59m, from Wed, 23 Sep 2026 20:59:56 GMT to Wed, 23 Sep 2026 23:59:54 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
2h 59m
tracked by PulseWatch

Impact

During the 2-hour and 59-minute high-severity incident affecting BigCommerce, the service experienced a period of disruption. This incident was identified through automated signals, including the vendor's status page. No user-reported data, such as specific issue types or affected regions, was collected for this incident. Therefore, the precise user-visible impact beyond the service disruption itself cannot be detailed from user reports.

Incident timeline

  1. Sep 23, 08:59 PM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 23, 08:59 PM

    Status updated: possible issue

  3. Sep 23, 11:59 PM

    PulseWatch closed the incident

Official updates

  1. Sep 23, 08:59 PM

    BigCommerce reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash