BigCommerce: RESOLVED: Increased error rate for api.bigcommerce.com
Timeline of updates
- resolved
From approximately 12:30 pm PST until 13:09 PST, there was an intermittent increase in errors for a small percentage of total API requests. The percentage was so small overall that the incident team managing the fix did not report status. Given some of the issues regarding API errors, we felt it important to document. We apologize for the lack of a status post and for the incident itself.
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).
Cite this
Status incident (vendor impact label: none) posted by BigCommerce, started 2019-02-06 18:30 UTC, resolved after 0 min, 1 update(s).
- Title
- RESOLVED: Increased error rate for api.bigcommerce.com
- Vendor
- BigCommerce
- Date
- URL
- https://rewindex.com/company/bigcommerce/incidents/sqjc3xkszczt
BigCommerce profileRecent BigCommerce incidentsAll outages on February 6, 2019BigCommerce in February 2019MarkdownJSON