Incidents reported on status page for AI Commerce Cloud https://status.aicommerce.fi/ https://d1lppblt9t2x15.cloudfront.net/logos/fbee3581b4549c47b0350956d2059476.png https://status.aicommerce.fi/ en https://status.aicommerce.fi/incident/866422 Tue, 07 Apr 2026 16:35:12 -0000 https://status.aicommerce.fi/incident/866422#e45ca071978b60e3bc3ced75516a47af5927eccc369d9046010701dedf5f57c1 Support recovered. https://status.aicommerce.fi/incident/866422 Tue, 07 Apr 2026 16:29:50 -0000 https://status.aicommerce.fi/incident/866422#1e5c09b70efe2ee175bc595098c249716f30c39adadc76267e40115241a786e4 Support went down. https://status.aicommerce.fi/incident/845408 Mon, 09 Mar 2026 16:50:00 -0000 https://status.aicommerce.fi/incident/845408#bf898a5e1e4b4fcc9c24532504842bedf02837f4679896feaec521c8d2774b0c Status: Resolved Time window: approximately 04:30–10:00 Finnish time, with some store-specific variation During the early morning AWS ElastiCache Redis maintenance window, some stores temporarily had few products missing from category and listing pages even though the products still existed correctly in the database. The issue was caused by an edge case in recently added Redis product cache logic that coincided with an AWS ElastiCache maintenance window. In certain situations, some Redis hash entries were missing, which caused partially incomplete cached listing data. Because no application exception occurred and the cache structure itself remained technically valid, the issue was not visible in automated tests or standard error monitoring. The main symptom was only that some products were missing from listings when they should have been visible. Some tenants recovered automatically as caches reloaded, while others were restored after manual Redis reload or flush actions. The technical team began investigating the issue around 09:30 Finnish time. All products were fully visible around 10:00 Finnish time. We have now improved the cache handling logic so that if a required product key is missing from Redis, the application will use the database as the backup source instead of assuming the product is missing. We also streamlined product cache invalidation and reload logic so that updates now target only the products that have changed, which improves both reliability and reload speed. The incident is resolved. We have not been able to reproduce the original failure exactly because it appears to have started during the AWS Redis maintenance window in combination with the previous cache logic. If any product visibility issues are still noticed, please submit a support ticket with example URLs or screenshots and, if available in your environment, perform a manual Redis reload or flush. We apologize for the disruption. https://status.aicommerce.fi/incident/790796 Fri, 19 Dec 2025 11:55:39 -0000 https://status.aicommerce.fi/incident/790796#e3eeaeb8dca12509b6ea2a7ceafe1c29d0d0e5db77404fa3274d6d515b868020 Backend API recovered. https://status.aicommerce.fi/incident/790796 Fri, 19 Dec 2025 11:40:27 -0000 https://status.aicommerce.fi/incident/790796#6869df6770b84e0b941c862e4a8bc1d9f478111430a1b80b62ad9364e392dd0e Backend API went down. https://status.aicommerce.fi/incident/785073 Fri, 12 Dec 2025 12:04:42 -0000 https://status.aicommerce.fi/incident/785073#a6e7abb21f268405b346e85335326b91a27b261f909ffdc779c890a65ae3efbf Backend API recovered. https://status.aicommerce.fi/incident/785073 Fri, 12 Dec 2025 11:34:25 -0000 https://status.aicommerce.fi/incident/785073#2074fc9a5e2b68d5bb810e21c86d1ec7c099b3c56dcf9ce02220f7f449782742 Backend API went down. https://status.aicommerce.fi/incident/780257 Fri, 05 Dec 2025 09:18:32 -0000 https://status.aicommerce.fi/incident/780257#78c37b8fc22931a42481f14dc7dfd990e6b8b7f156f8d4c91e6a01d23e65c7bd Support recovered. https://status.aicommerce.fi/incident/780257 Fri, 05 Dec 2025 08:52:52 -0000 https://status.aicommerce.fi/incident/780257#cc79cc5b387b6d648ef4b259df6c1b9baac1cc9f754233bc98714255731bc9ea Support went down. https://status.aicommerce.fi/incident/739889 Thu, 02 Oct 2025 19:15:00 -0000 https://status.aicommerce.fi/incident/739889#9ea9c84d88193304aabde1873d141b799645b3cca68771511d2ce4ac1c4a95db Issue was resolved right after the incident. https://status.aicommerce.fi/incident/739889 Thu, 02 Oct 2025 12:13:00 -0000 https://status.aicommerce.fi/incident/739889#c6e1f3e4af399d61608a0b30dd966fe66b3668878480abde3a8475574b4a6941 AWS EFS -verkkolevyssä ilmeni häiriö 1.10.2010 aamulla, josta järjestelmäylläpitäjät havahtuivat välittömästi. He aloittivat korjaustoimet ennen kuin tilanne eskaloitui laajemmaksi, ja ennen kuin kauppiaat ilmoittivat ongelmasta. Yritimme ensin hallitumpaa kiertoratkaisua, mutta sen epäonnistuttua jouduimme hetkellisesti estämään verkkoliikenteen ja vaihtamaan levyresurssin tyypin (burstable → elastic), jotta AWS:n resurssipolitiikat eivät pullonkauloittaisi suorituskykyä. Varsinainen korjaus valmistui alle tunnissa; merkitsimme tapauksen ratkaistuksi hieman myöhemmin, kun vakaus oli varmistettu.