Commercetools Status

<small>March 30, 2026 13:15 UTC</small><br /><b>Monitoring</b> - API hub had degraded performance on a restricted group of customers. All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur. Our platform mitigation actions addressed the previously identified degraded performance issues and we are verifying that all health checks are now passing. We appreciate your patience as we ensure the continued stability of the infrastructure<br /><br /><small>March 30, 2026 13:41 UTC</small><br /><b>Resolved</b> - The reported issues affecting part of GCP EU region have been successfully resolved. Our engineering team has verified that all health checks are passing and API performance has returned to optimal levels across all affected projects. We understand this was disruptive and appreciate your patience as we worked to restore service. All systems are currently operating normally.<br /><br />

<small>March 24, 2026 10:00 UTC</small><br /><b>Investigating</b> - GCP Europe<br /><br />We are experiencing elevated levels of 5xx errors across certain API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br />Affected endpoints include: <br />- product-related endpoints<br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>March 24, 2026 10:15 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>March 24, 2026 10:18 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>March 24, 2026 10:55 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>March 19, 2026 15:42 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 5xx errors across certain API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br />Affected endpoints include: <br />-/orders<br />-/in-store/<store-key>/orders<br /><br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>March 19, 2026 16:08 UTC</small><br /><b>Identified</b> - We are currently seeing an increase in latency and 503 errors affecting Composable Commerce APIs in the GCP EU region. Projects may experience slow response times and elevated error rates, particularly on order-related endpoints. Our engineering team has applied mitigative measures, and we are seeing a gradual recovery in performance. We are closely monitoring the situation and will provide further updates as more information becomes available.<br /><br /><small>March 19, 2026 16:21 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>March 19, 2026 17:08 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>March 16, 2026 12:34 UTC</small><br /><b>Investigating</b> - We are currently investigating reports of high external response times across multiple infrastructure components in these regions. This behavior may result in slow loading times for web shops and delayed processing within affected projects. Our engineering teams are taking mitigative actions to restore optimal performance as quickly as possible. We will provide further updates.<br /><br /><small>March 16, 2026 12:58 UTC</small><br /><b>Identified</b> - We have successfully identified the cause of the increased response times across the affected infrastructure. Our engineering teams are currently applying mitigative actions to restore optimal performance. We are closely monitoring the impact and will provide further updates in 30 minutes.<br /><br /><small>March 16, 2026 13:09 UTC</small><br /><b>Monitoring</b> - We have applied mitigative measures to address the increased response times and are currently seeing signs of recovery across the affected infrastructure. Our engineering teams are closely monitoring the stability of the environment. We will continue to monitor performance. Thank you for your patience.<br /><br /><small>March 16, 2026 13:26 UTC</small><br /><b>Monitoring</b> - While the infrastructure is stable, we recommend avoiding new production deployments within Frontend until further notice as we finalize background processes. Staging deployments may have issues. We are working to restore full deployment functionality as quickly as possible and appreciate your patience.<br /><br /><br /><small>March 16, 2026 15:09 UTC</small><br /><b>Resolved</b> - We have closely monitored the systems and verified that all services are now operating at optimal levels. We appreciate your patience while we worked to ensure a stable resolution.<br /><br />

<small>March 12, 2026 17:00 UTC</small><br /><b>Identified</b> - We are experiencing elevated levels of 5xx errors across certain API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br />Affected endpoints include: <br />- /products/search<br />- /product-projections/search<br />- /graphql<br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>March 12, 2026 17:25 UTC</small><br /><b>Investigating</b> - We are currently investigating a service disruption affecting product search endpoints in the GCP EU region, where requests are returning 503 errors. Affected projects may experience a complete loss of product search functionality. Our engineering team is actively reviewing system logs and diagnostic traces to identify the cause and restore service. We are working to resolve this as quickly as possible.<br /><br /><small>March 12, 2026 17:37 UTC</small><br /><b>Monitoring</b> - We have identified the cause of the issue affecting Product Search in the GCP EU region and corrective actions have been applied.<br /><br /><small>March 12, 2026 18:05 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>March 6, 2026 17:40 UTC</small><br /><b>Investigating</b> - We are experiencing a service disruption for accessing Merchant Center and Frontend Studio. Our teams are actively investigating the issue and working to mitigate the impact. <br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>March 6, 2026 17:50 UTC</small><br /><b>Monitoring</b> - We have successfully identified the cause of the issue and operations have returned to normal. Merchant Center and Studio are now accessible in the US region.<br /><br />We will continue to monitor the situation and provide updates as necessary. <br /><br /><small>March 6, 2026 18:11 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>March 5, 2026 09:19 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in latency. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>March 5, 2026 09:23 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>March 5, 2026 10:12 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>March 2, 2026 16:34 UTC</small><br /><b>Investigating</b> - We are experiencing a service disruption for accessing Merchant Center. Our teams are actively investigating the issue and working to mitigate the impact. <br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>March 2, 2026 16:44 UTC</small><br /><b>Investigating</b> - We are currently experiencing a service disruption for Merchant Center in AWS US as well. <br /><br />Our team is working with the highest priority to restore services.<br /><br />We will provide updates as soon as more information becomes available.<br /><br /><small>March 2, 2026 16:54 UTC</small><br /><b>Investigating</b> - We are currently investigating an issue with our underlying identity provider service that is causing service disruptions for the Merchant Center. <br /><br />Affected projects in the AWS US and GCP North America region may experience difficulties logging in or accessing administrative features. <br /><br />Our engineering team is working closely with our service partners to restore normal functionality as quickly as possible.<br /><br /><small>March 2, 2026 17:13 UTC</small><br /><b>Identified</b> - We have successfully identified the cause of the issue and operations have returned to normal. Merchant Center and Studio are now accessible in the US region.<br /><br />We will continue to monitor the situation and provide updates as necessary. <br /><br /><small>March 2, 2026 18:02 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service. <br /><br />

<small>February 15, 2026 10:29 UTC</small><br /><b>Investigating</b> - Subscription change notifications to GCP PubSubs are delayed.<br />This may result in inaccuracies or out-of-date information in downstream systems that rely on these messages<br /><br />No data loss occurred.<br /><br /><small>February 15, 2026 10:31 UTC</small><br /><b>Investigating</b> - We initially marked all regions as affected by the incident. However, the issue is limited to Google Cloud Australia.<br />We apologize for the confusion.<br /><br /><small>February 15, 2026 10:53 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>February 15, 2026 10:56 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>February 15, 2026 11:20 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>February 10, 2026 23:30 UTC</small><br /><b>Investigating</b> - GCP Europe<br /><br />We are currently investigating an increase in latency. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>February 11, 2026 00:35 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely, and we will provide updates as necessary.<br /><br /><small>February 11, 2026 01:03 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>February 11, 2026 01:28 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>January 29, 2026 16:41 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 5xx errors across certain API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>January 29, 2026 17:13 UTC</small><br /><b>Identified</b> - We have successfully identified the cause of the issue and are currently taking corrective actions to resolve it. We will continue to monitor progress and provide updates as necessary.<br /><br /><small>January 29, 2026 17:31 UTC</small><br /><b>Identified</b> - The team is currently working on applying corrective actions to resolve the issue. We will provide updates as necessary. <br /><br /><small>January 29, 2026 17:55 UTC</small><br /><b>Monitoring</b> - The team has applied corrective measures. Operations are returning to normal. We are closely monitoring performance and will provide updates if any changes occur. <br /><br /><small>January 29, 2026 19:06 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>January 9, 2026 09:20 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in 500 errors. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>January 9, 2026 09:45 UTC</small><br /><b>Identified</b> - We are currently investigating an increase in 500/503/504 errors across the Composable Commerce APIs in all AWS and GCP regions. Affected projects may experience failures when processing cart-related requests, which could impact checkout and web shop functionality. Our engineering teams have been notified and are actively working to mitigate the impact across the affected infrastructure. We are committed to restoring normal functionality as quickly as possible.<br /><br /><small>January 9, 2026 10:06 UTC</small><br /><b>Identified</b> - Our engineering teams are actively performing recovery work on the underlying database services to mitigate the impact across the affected infrastructure. We are committed to resolving this as swiftly as possible.<br /><br /><small>January 9, 2026 10:17 UTC</small><br /><b>Identified</b> - We have now restored services for projects in AWS EU, we are actively applying these corrective actions to all remaining AWS and GCP regions. Affected projects in other regions may still experience disruptions to cart-related services and web shop functionality until the fix will be rolled out there. We are monitoring the recovery progress closely.<br /><br /><small>January 9, 2026 10:21 UTC</small><br /><b>Monitoring</b> - We have successfully deployed the fix to all remaining AWS and GCP regions and are observing recovery across the global infrastructure. Service has returned to normal for affected projects, and we are closely monitoring the stability of the underlying database services. We will continue to track performance to ensure full restoration of cart-related services and web shop functionality. A final update will be provided once we have confirmed the issue is fully resolved.<br /><br /><small>January 9, 2026 11:28 UTC</small><br /><b>Monitoring</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br /><small>January 9, 2026 17:15 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>January 2, 2026 20:34 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in errors. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>January 2, 2026 20:52 UTC</small><br /><b>Investigating</b> - Our engineering team is still working to identify the root cause and restore optimal performance. <br /><br />We will provide updates as soon as more information becomes available. <br /><br /><small>January 2, 2026 21:08 UTC</small><br /><b>Identified</b> - We have successfully identified the cause of the issue and are currently taking corrective actions to resolve it. We will continue to monitor progress and provide updates as necessary. <br /><br /><small>January 2, 2026 21:12 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur. <br /><br /><small>January 2, 2026 21:44 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service. <br /><br />

<small>December 26, 2025 19:22 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 5xx errors across most API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>December 26, 2025 19:29 UTC</small><br /><b>Monitoring</b> - We can now confirm that after a short spike of mostly 503 errors all systems are currently operating normally again. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>December 26, 2025 20:35 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved and we have applied mitigative steps to prevent re-occurrence. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br /><br />

<small>December 19, 2025 04:00 UTC</small><br /><b>Investigating</b> - Subscription change notifications to GCP PubSub are delayed.<br />This may result in inaccuracies or out-of-date information in downstream systems that rely on these messages. No data loss occurred.<br /><br /><small>December 19, 2025 04:10 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>December 19, 2025 04:13 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>December 19, 2025 04:30 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>December 15, 2025 04:17 UTC</small><br /><b>Investigating</b> - Our CI/CD pipeline is currently experiencing delays and is temporarily unavailable, which is preventing new builds and deployments. Deployments of previously successful builds are still functional. Our engineering team is investigating the cause of the issue and is working diligently to restore full service. <br /><br /><small>December 15, 2025 05:19 UTC</small><br /><b>Investigating</b> - We are actively investigating the underlying cause of the behavior reported. Our team is working to resolve the issue and we will continue to provide regular updates<br /><br /><small>December 15, 2025 05:49 UTC</small><br /><b>Investigating</b> - We continue to actively investigate the underlying cause of the behavior reported. Our team is working to resolve the issue and we will continue to provide regular updates<br /><br /><small>December 15, 2025 06:29 UTC</small><br /><b>Investigating</b> - We continue to investigate the underlying cause. We will continue to provide regular updates as our team works to resolve the issue.<br /><br /><small>December 15, 2025 06:43 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>December 15, 2025 07:00 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>December 15, 2025 07:33 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>December 8, 2025 12:15 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in errors and latency. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>December 8, 2025 12:45 UTC</small><br /><b>Monitoring</b> - We have observed that error rates and delays have returned to normal levels over the past 10 minutes. However, our engineering team is continuing to investigate the underlying cause to ensure full service stability. We will continue to monitor the situation closely and provide further updates as necessary.<br /><br /><small>December 8, 2025 13:02 UTC</small><br /><b>Resolved</b> - The issue affecting Composable Commerce APIs in the AWS EU region has been successfully resolved. The elevated 500 errors and latency, caused by load on underlying database services, have been mitigated and service levels have returned to normal. All systems are currently operating normally. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>November 28, 2025 12:45 UTC</small><br /><b>Resolved</b> - External service Netlify experienced issues that affected some Frontend customers. This only affected customers using Netlify High Powered Edge Network. Netlify has now applied mitigation and is monitoring the situation. For more details, please check the partner's status page: https://www.netlifystatus.com<br />Starting time was at 12:05 UTC<br /><br />

<small>November 18, 2025 11:40 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in errors in the Merchant Center and Frontend Studio. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>November 18, 2025 12:01 UTC</small><br /><b>Identified</b> - The current issue is preventing users from logging into the Composable Commerce Merchant Center and Frontend Studio across all regions. This issue is due to the underlying authentication services failing. We understand this is disruptive and appreciate your patience as we await further developments.<br /><br /><small>November 18, 2025 12:26 UTC</small><br /><b>Identified</b> - While some users might be able to log in and navigate in Merchant Center and Frontend Studio successfully, most will encounter access issues.<br />We are actively coordinating with our infrastructure partners to monitor the resolution of the underlying network disruption. We will continue to provide regular updates as the situation evolves.<br /><br /><small>November 18, 2025 12:34 UTC</small><br /><b>Identified</b> - We are currently observing a partial recovery of the authentication services affecting the Composable Commerce Merchant Center and Frontend Studio. While some users are now able to log in successfully, others may still encounter intermittent access issues. We are continuing to monitor the situation alongside our infrastructure partners to ensure full service availability is restored. We will provide further updates as soon as more information becomes available.<br /><br /><small>November 18, 2025 13:01 UTC</small><br /><b>Identified</b> - The current status remains a state of partial service recovery for the Composable Commerce Merchant Center and Frontend Studio. While some projects may be able to successfully access the services, others continue to face intermittent access issues due to the instability of the underlying authentication services. Our teams are actively engaged and continuing to work with our infrastructure partners to fully stabilize the service.<br /><br /><small>November 18, 2025 13:16 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>November 18, 2025 13:44 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>November 6, 2025 15:55 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 5xx errors across certain API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br />Affected endpoints include: <br />- product/search<br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>November 6, 2025 16:01 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>November 6, 2025 16:17 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>November 4, 2025 14:33 UTC</small><br /><b>Investigating</b> - We are currently investigating an issue affecting the Studio. Some users may experience errors, degraded performance, or be unable to load the interface.<br /><br />Our engineering team is actively working to identify the root cause and restore normal functionality as soon as possible.<br /><br /><br /><br /><small>November 4, 2025 14:54 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br />

<small>November 4, 2025 13:42 UTC</small><br /><b>Investigating</b> - The Merchant Center in the GCP-AU region is currently unavailable, and users may be experiencing issues with login functionality. We have identified that the core issue is a login failure within the service. Our engineering team is actively investigating the root cause and is working diligently to restore full service as quickly as possible. This issue began at approximately 13:42 UTC. We will provide a further update within the next 30 minutes.<br /><br /><small>November 4, 2025 14:15 UTC</small><br /><b>Investigating</b> - We are actively investigating the underlying cause of the current degraded performance affecting the Merchant Center in the GCP-AU region. Users continue to experience issues with login functionality. Our team is working to resolve the issue and we will provide another update in 30 minutes.<br /><br />

<small>October 20, 2025 17:32 UTC</small><br /><b>Investigating</b> - We’re currently investigating an increase in connection errors on Netlify. Our engineering team is actively working to identify the root cause and restore full functionality. We’ll share updates on the status page as soon as more information becomes available.<br /><br /><br />

<small>October 20, 2025 07:59 UTC</small><br /><b>Identified</b> - AWS North America<br /><br />The background data processing infrastructure is delayed due to an incident in AWS Services<br /><br />Subscription messages/change notifications to are delayed<br />This may result in inaccuracies or out-of-date information in downstream systems that rely on these messages'<br /><br />No data loss occurred.<br /><br /><br />

<small>October 9, 2025 07:53 UTC</small><br /><b>Investigating</b> - A recent deployment introduced unexpected behavior on the graphQL, resulting in the following issue: <br />products may appear to be out of stock<br /><br />We have initiated a rollback of the deployment to resolve the problem. Our team is actively working to resolve this. <br /><br />

<small>October 5, 2025 01:46 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in latency, mainly impacting graphQL endpoints. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>October 5, 2025 01:58 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br />

<small>September 30, 2025 03:54 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in latency in cart endpoints. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>September 30, 2025 04:01 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>September 30, 2025 04:04 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>September 30, 2025 04:15 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>September 25, 2025 08:51 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 5xx errors and latency across certain API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br />

<small>September 24, 2025 17:46 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 500 and 503 errors across multiple API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br />

<small>September 24, 2025 14:37 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 500 and 503 errors across multiple API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br />

<small>September 23, 2025 03:22 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in latency in cart related endpoints. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>September 23, 2025 03:29 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>September 23, 2025 03:30 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>September 23, 2025 03:41 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>September 12, 2025 03:21 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in latency on carts endpoints. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>September 12, 2025 03:59 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>September 12, 2025 04:24 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>September 12, 2025 04:34 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>September 8, 2025 14:47 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 5xx errors across certain API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>September 8, 2025 14:56 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in errors and latency. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>September 8, 2025 15:00 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br />

<small>September 4, 2025 01:14 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in errors. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>September 4, 2025 01:19 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>September 4, 2025 01:33 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br />

<small>September 3, 2025 22:08 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in errors. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>September 3, 2025 22:13 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>September 3, 2025 22:45 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>September 3, 2025 22:50 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>August 30, 2025 05:21 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in latency on POST and GET requests to products related endpoints. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br />

<small>August 21, 2025 15:31 UTC</small><br /><b>Identified</b> - We are currently investigating an increase in errors. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br />This is affecting Product Projections search the most.<br /><br /><small>August 21, 2025 15:41 UTC</small><br /><b>Identified</b> - We have identified the cause of the elevated error rate on GET and POST requests to product-projections/search and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><br /><small>August 21, 2025 15:47 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>August 21, 2025 15:59 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>August 15, 2025 18:18 UTC</small><br /><b>Investigating</b> - We are currently having an outage affecting most endpoints in AWS North America. <br /><br />The team is investigating this with high priority.<br /><br />

<small>July 31, 2025 16:24 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 5xx errors across certain API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br />Affected endpoints include: <br />product-projections/search<br />Product projections using graphql endpoint<br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>July 31, 2025 16:43 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>July 31, 2025 16:53 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br />

<small>July 29, 2025 08:15 UTC</small><br /><b>Investigating</b> - Our CI/CD pipeline is currently experiencing delays due to an underlying issue with our cloud provider. Our engineering team is investigating the cause of the issue and is working diligently to restore full service. <br /><br /><small>July 29, 2025 08:21 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>July 29, 2025 08:30 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>July 29, 2025 09:20 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>July 28, 2025 07:21 UTC</small><br /><b>Investigating</b> - Netlify has identified increased errors on sites using their Standard Edge Network.<br /><br />

<small>July 25, 2025 03:55 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 503 errors across product related API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>July 25, 2025 04:09 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br /><small>July 25, 2025 04:23 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br />

<small>July 24, 2025 07:00 UTC</small><br /><b>Investigating</b> - We are experiencing elevated levels of 5xx errors across certain API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. <br />Affected endpoints include: <br />-GET and POST on product related endpoints<br /><br />We are committed to resolving this as swiftly as possible and will provide further updates shortly.<br /><br /><small>July 24, 2025 07:05 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br />

<small>July 18, 2025 10:20 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in errors. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available. <br />Impacted endpoints: product-projections/search<br /><br /><small>July 18, 2025 10:25 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>July 18, 2025 10:26 UTC</small><br /><b>Monitoring</b> - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br />

<small>July 15, 2025 07:24 UTC</small><br /><b>Investigating</b> - We are currently investigating an increase in errors impacting GraphQL product projections search requests. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br />

<small>July 2, 2025 16:20 UTC</small><br /><b>Investigating</b> - Our CI/CD pipeline is experiencing delays, preventing new builds and deployments. Deployments of previously successful builds are still functional. Our engineering team is investigating the cause of the issue and working diligently to restore full service. <br /><br /><small>July 2, 2025 16:22 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br />

<small>July 1, 2025 16:07 UTC</small><br /><b>Investigating</b> - The background data processing infrastructure is delayed by approximately 1 hour.<br /><br />This is causing inaccuracies in:<br />- product search results<br />- category search results<br />- order search results<br /><br />And delay on:<br />- Subscription messages/change notifications to queues hosted in AWS<br />- This may result in inaccuracies or out-of-date information in downstream systems that rely on these messages<br /><br /><small>July 1, 2025 16:22 UTC</small><br /><b>Identified</b> - We have identified the cause of the issue and are currently taking corrective actions to resolve it. We are monitoring progress closely and we will provide updates as necessary.<br /><br />

<small>July 1, 2025 12:25 UTC</small><br /><b>Investigating</b> - The background data processing infrastructure is delayed by approximately 1 hour.<br /><br />This is causing inaccuracies in:<br />- product search results<br />- category search results<br /><br />And delay on:<br />- Subscription messages/change notifications to queues hosted in AWS<br />- This may result in inaccuracies or out-of-date information in downstream systems that rely on these messages<br /><br /><br />

<small>June 14, 2025 06:23 UTC</small><br /><b>Identified</b> - We are currently investigating an increase in errors on GET and POST requests for endpoints related to carts, payments, customers, shopping lists since about 5:57am UTC. Our engineering team is working to identify the root cause and restore optimal performance. We will provide updates as soon as more information becomes available.<br /><br /><small>June 14, 2025 06:27 UTC</small><br /><b>Monitoring</b> - We can see that the errors have subsided. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>June 14, 2025 05:57 UTC</small><br /><b>Resolved</b> - The reported issue has been successfully resolved. We apologize for any inconvenience this may have caused and appreciate your understanding as we worked to restore service.<br /><br />

<small>June 12, 2025 18:47 UTC</small><br /><b>Investigating</b> - Investigating, actions and BFF failing intermittently <br /><br /><small>June 12, 2025 18:51 UTC</small><br /><b>Investigating</b> - GCP US Experiencing an outage, actions/extension runner failing intermittently<br /><br /><small>June 12, 2025 19:00 UTC</small><br /><b>Identified</b> - GCP US outage ongoing, actions/extension runner failing intermittently<br /><br /><small>June 12, 2025 20:55 UTC</small><br /><b>Monitoring</b> - After restoring we can see that all systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.<br /><br /><small>June 12, 2025 20:56 UTC</small><br /><b>Monitoring</b> - We keep monitoring our services and will provide additional updates in case of any changes.<br /><br />