Nosto had 11 outages in the last 2 years totaling 48h 26m of downtime — averaging 0.5 incidents per month.
There were 11 Nosto outages since September 12, 2024 totaling 48h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.
https://www.shopifystatus.com/ Issues with Shopify are also impacting Nosto customers using the Shopify platform. We are monitoring the situation.
Shopify has resolved the issue
Problems with our upstream partner service are affecting Search product updates. Updates to products in Search and Category Merchandising have not been processed since 07:18 UTC. We are working on getting the missing updates processed.
Resolved — We have fully recovered from the issues caused by earlier operational problems with Amazon Web Services (AWS). End-customer–facing services remained unaffected throughout the incident. However, product updates that relied on our automated provisioning systems were temporarily impacted due to our inability to create new resources via AWS. Normal operation has now been restored.
We are currently experiencing an issue where some products in API responses are missing custom fields (returned as null). The source of the issue has been identified, and our team is actively working on restoring the service to ensure all product data is returned as expected. Further updates will be provided as we make progress.
We have identified that SKU-level custom fields are impacted when products are updated. Our team is applying temporary fixes to address parts of the issue in the short term. In parallel, we are preparing longer-term solutions that will fully clean and restore the affected data. We will continue to work on these fixes and keep this incident updated as progress is made.
We have identified the root cause of the issue affecting SKU-level custom fields in our Search product and have implemented a fix. Our team is now addressing any product data for all merchants using Search to ensure consistency across datasets. This process will be completed within the next few hours. Impact: * Only updated products were affected. * Missing data was limited primarily to SKU-level custom fields. * The total number of impacted products is relatively small, but we recognize that this may have caused undesired side effects in some cases. We appreciate your patience and understanding as we work to finalize data consistency across all merchants.
The product data has been restored to current up-to-date state
We’ve identified what is causing the issue and are working on a to resolve the issue. An update will be provided once the issue has been resolved. Your patience is appreciated.
We have identified an issue that is affecting some customers using parameterless attribution
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
There was a software upgrade that lead to the A/B test results page to give out an error when being opened. The actually A/B tests were not impacted and there was also no impact to customer web sites. The issues has been identified and resolved
Our Search and Category Merchandising (Universal) APIs were experiencing increased latencies and timed-out requests due to a misconfigured merchant. The degradation lasted for about 49 minutes. We have resolved the issue and added additional checks to prevent such misconfigured merchants from affecting the performance of our APIs in the future.
All merchants using Search and Category Merchandising features were affected. Services started recovering automatically, for most merchants within minutes, but for some merchants the outage lasted for 14 minutes. All services have now recovered. We will follow up with more details.
We’ve identified what is causing the issue and are working on a to resolve the issue. An update will be provided once the issue has been resolved. Your patience is appreciated.
The cause of the outage was a failure of one of database servers, which caused problems in other parts of the system before the load was moved elsewhere and everything stabilised. We are investigating the exact cause of this.
We experienced issues while showing recommendations and in debug tool set.
Few of our API's are exposing to the huge and unexpected user traffic and this is exceeding our capacity limits. We already increases our resources in relevant integrations.
Issues was caused by a sudden increase of traffic and complex usage from a 3rd party that cause strain the platform resources. The issue was resolved by 3rd party and we took also action to mitigate by temporarily adding resources ensure smooth operations on the platform.