Nosto Outage History
Nosto is up right nowPingoru has recorded 50 incidents for Nosto: 2 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 1 | 5 of 720 (1%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 520 (0%) |
Incidents, newest first
Major June 3, 2026 Shopify issues impacting Nosto 4h 29m Integrations
Started Jun 03, 2026, 03:10 PM UTC· resolved Jun 03, 2026, 07:39 PM UTC
- monitoring Jun 03, 2026, 03:10 PM UTC
https://www.shopifystatus.com/ Issues with Shopify are also impacting Nosto customers using the Shopify platform. We are monitoring the situation.
- resolved Jun 03, 2026, 07:39 PM UTC
Shopify has resolved the issue
Major February 18, 2026 We are investigating issues causing degraded functionality 1h 27m API, Search & Categories
Started Feb 18, 2026, 02:54 AM UTC· resolved Feb 18, 2026, 04:21 AM UTC
- investigating Feb 18, 2026, 02:54 AM UTC
We are currently investigating this issue.
- identified Feb 18, 2026, 04:17 AM UTC
We observed intermittent timeouts affecting client requests to https://connect.nosto.com . Timeout rates increased for a few hours, but we are no longer seeing new timeouts.
- resolved Feb 18, 2026, 04:21 AM UTC
No new health check failures have been observed on our side, and we are no longer seeing new timeouts. We will continue our postmortem investigation. At this time, we have not identified a clear internal cause and are investigating the possibility that a third-party issue, potentially related to AWS CloudFront, impacted our infrastructure.
- postmortem Feb 20, 2026, 11:31 AM UTC
## **Post-incident summary** During the incident, Nosto Core Personalisation \(including on-site product recommendations and email widgets\) was intermittently slow or unavailable. A sudden traffic spike, largely originating from a single external source, triggered unexpected behavior in the Nosto script’s client-side error reporting. This resulted in a very high volume of error-reporting requests with unusually large payloads being sent to our backend services. The increased load slowed request processing, which then caused additional timeouts and connection errors. Those errors generated further reports, creating a cascading effect where auto-scaling could not keep up with demand. On average, approximately 60–80% of requests \(depending on component\) were impacted during the incident. ### **Impact to other services** Search and Category Merchandising infrastructure remained operational. However, because the Nosto script uses personalisation signals to boost Search and Category Merchandising, some customers experienced failures on category page loads when personalisation calls failed. This affected approximately 24% of Search traffic. Direct GraphQL API calls continued to operate normally. ### **Fixes and prevention** We have completed the post-mortem and implemented the following mitigations: * Updated the Nosto script to handle similar client-side error-reporting scenarios safely and prevent excessive request volume. * Extended rate limiting on the error-reporting endpoint to protect backend services from overload. ### **Ongoing improvements** Work is underway to further reduce risk and improve resilience: * Isolating the logging/error-reporting service from core personalisation services. * Improving alerting and on-call triage processes to detect and mitigate similar patterns faster.
Minor October 20, 2025 Missing product updates in Search & Category Merchandising 17h 55m Search & Categories
Started Oct 20, 2025, 12:22 PM UTC· resolved Oct 21, 2025, 06:18 AM UTC
- identified Oct 20, 2025, 12:22 PM UTC
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 Oct 21, 2025, 06:18 AM UTC
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.
Minor September 22, 2025 CustomFields in Search and CM temporarily unavailable 19h 20m Search & Categories
Started Sep 22, 2025, 07:05 PM UTC· resolved Sep 23, 2025, 02:26 PM UTC
- monitoring Sep 22, 2025, 07:05 PM UTC
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.
- monitoring Sep 22, 2025, 10:17 PM UTC
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.
- monitoring Sep 23, 2025, 08:25 AM UTC
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.
- resolved Sep 23, 2025, 02:26 PM UTC
The product data has been restored to current up-to-date state
Major July 30, 2025 We have identified issue causing degraded functionality in the Nosto Commerce Experience Platform 26m Onsite products
Started Jul 30, 2025, 08:36 AM UTC· resolved Jul 30, 2025, 09:03 AM UTC
- identified Jul 30, 2025, 08:36 AM UTC
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.
- identified Jul 30, 2025, 08:42 AM UTC
We have identified an issue that is affecting some customers using parameterless attribution
- monitoring Jul 30, 2025, 08:48 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 30, 2025, 09:03 AM UTC
This incident has been resolved.
Notice May 27, 2025 A/B test results showing an error in the Admin tool – Admin panel
Started May 27, 2025, 09:21 PM UTC· resolved May 27, 2025, 09:21 PM UTC
- resolved May 27, 2025, 09:21 PM UTC
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
Major March 29, 2025 Increased latency / partial outage in Search & Category Merchandising (Universal) 49m
Started Mar 29, 2025, 03:03 PM UTC· resolved Mar 29, 2025, 03:52 PM UTC
- resolved Apr 07, 2025, 03:14 PM UTC
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.