BigCommerce Status · History · Incident #4094
RESOLVEDElevated errors for a subset of stores
Minor · Started May 28, 2026 · 3:00 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
BigCommerce Status · History · Incident #4094
RESOLVEDMinor · Started May 28, 2026 · 3:00 AM
Duration
< 1m
Severity
Minor
Detection lead
—
User reports
—
Summary
Between 08:12 UTC and 08:19 UTC, some stores experienced elevated HTTP 500 errors on the storefront and API.
Started
May 28, 2026 · 3:00 AM
Resolved
May 28, 2026 · 3:00 AM
Duration
< 1m
Severity
None
Event timeline
Resolved
May 28 · 4:16 AM BigCommerceBetween 08:12 UTC and 08:19 UTC, some stores experienced elevated HTTP 500 errors on the storefront and API.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT