Searchspring had 8 outages in the last 2 years totaling 56h 11m of downtime — averaging 0.3 incidents per month.
There were 8 Searchspring outages since July 23, 2025 totaling 56h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
We are seeing intermittent issue in some region, where PLP page render gets error out due to JSX syntax error
This incident has been resolved.
We are seeing a high indexing queue in multiple regions
We are curently investigating the problem
The issue has been identified, we are currently working on fixing the issue
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We experienced elevated error rates and intermittent performance degradation affecting search traffic due to a combination of infrastructure strain and unexpected automated traffic patterns. The issue primarily impacted search functionality and resulted in multiple brief spikes in server errors.
Systems are currently stable. Error rates have returned to normal levels, and search performance is operating within expected thresholds. We are continuing to monitor closely and further analyze traffic patterns to prevent recurrence.
This issue has been resolved. All systems are operating normally, and error rates and performance have returned to expected levels.
Were seeing an increased error rate on search api requests in the Australia region.
Operations have returned to normal, we are continuing to monitor the situation.
This incident has been resolved.
A subset of BigCommerce customers experienced product listing pages failing to load results due to a template change on the BigCommerce platform (we estimate). The change caused Searchspring’s Snap integration to misinterpret the “Search Results” page as a category, applying an invalid background filter that returned no products. The issue was intermittent and did not affect Searchspring’s core search service. Functionality was restored within minutes, likely following a rollback of the update by BigCommerce.
AWS is currently having a major outage, this is impacting our indexing services https://health.aws.amazon.com/health/status
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing a high volume of 503 Service Unavailable errors impacting the search experience across a small subset of sites. This may result in degraded performance or temporary unavailability of search functionality for some users. Our team has identified the root cause and are working to resolve this issue. We will provide another update in 30 minutes or sooner.
A fix has been implemented, and we are currently monitoring system performance to ensure the issue has been fully resolved.
The issue has been fully resolved, and all affected services are now operating as expected.