Store hosting platform BigCommerce has acknowledged the outage that hit its platform on March 17, 2023. In short, the post on Twitter says: only instead of that ingredient.’
A retailer that hosts their store on BigCommerce has released advises its customers on Twitter at 12:12. “Our e-commerce platform,
@BigCommerce is currently down, so you may not be able to visit our site right now. We apologize for the inconvenience and are in the process of fixing the issue as soon as possible.”
BigCommerce responded to the tweet at 2:51 p.m.
“Exchanging updates for you and your customers. This issue has now been resolved by our engineering team.
“Thanks to everyone for putting up with us while we worked this out.”
Separately, BigCommerce tweeted an explanation for the technical issues plaguing its platform:
“This morning’s incident was due to a race condition in the global component of the platform responsible for resolving incoming request currencies. In particular, under increased load, the component degraded non-linearly, resulting in significantly duplicated queries.
“BigCommerce engineers are immediately fixing the underlying issue and are in the process of adding a caching layer to reduce the overall volume of requests. We will perform a full cross-functional post-mortem and expect additional remediation steps to be implemented.
“In short, there was an unexpected load on a globally used component that results in degraded platform performance instead of that component alone.”
According to its status page, on March 16th it was experiencing “Intermittent Availability Issues”. It reported Friday’s “Availability Issue” as “an issue affecting the availability of a subset of stores. We are currently fixing the issue and will provide an update soon.”
At least one seller reported that BigCommerce’s customer service was down during part of the outage. asks the tweet why his servers, phones and chat were down; “How is a business supposed to operate without support or a way to communicate,” the seller tweeted.
BigCommerce said on its status page that the issue was noticed at 10:40 a.m. and was considered resolved by 12:30 p.m.