Archive by Author

“This site can’t be reached” Errors

10:35 UTC - We can report that this issue is resolved. If you run into any issues, please reach out to us via support[@]commercebuild.com. Thank you! 10:15 UTC - We are aware of "This site can't be re...

Connection Timeout Issues Affecting Stores in North America

November 8, 19:44 UTC - The issue occurred due to a large influx of traffic from crawlers (similar to Googlebot and other services that may index pages) across multiple sites. commercebuild utilizes r...

Intercom Latency

15:50 UTC - Intercom has confirmed that the fix for this issue is in place, and they are seeing systems return to normal. We're seeing the same. Thanks again for your patience. 14:50 UTC - Intercom, o...

Release 4.69

August 9, 10:30 UTC - In the evening of August 7, commercebuild upgraded web stores in North America and Europe to 4.69. The 4.69 release will be available in our Australia region as soon as possible....

Paya Issues

21:35 UTC, August 10 - We received a report from one of our customers in communication with Paya that the issue had been caused by something on their end. They had rolled out an enhancement of some ki...

URGENT: Issues with “Copying Pages from Dealer to Public”

00:00 UTC - A hot fix was released for this to all environments and this should no longer be an issue. 16:47 UTC - If you experience this issue, one way to resolve it is to copy each page individually...

500 Errors

23:32 UTC - The issue was related to the number of connections to one subset of our databases reaching its maximum limit. We have temporarily increased the limit to resolve the problem, and now we wil...

500 Errors Affecting Subset of Sites in North America Region

23:50 UTC - We're now seeing functionality return to affected sites. We are assessing the cause of this issue and hope to provide more information, if possible. 23:33 UTC - Our systems team continues ...

Product Information Not Displayed after 4.61 Release

May 8 - After additional fixes, we now believe this issue to be resolved. The reason this issue occurred was due to a bug fix that had a work-around in place to get around it. As a result of the bug f...