18 Commercetools incidents · marzec 2026 — official updates, affected components, duration and resolution details.
1 września 2026 14: 32 UTC Badanie - Na stronie GCP istniała globalna usługa zewnętrzna, Cloud NAT, która dotyczyła regionu USA i naszego Frontend Delivery. 1 września 2026 15: 50 UTC Resoluted - Resoluted on GCP side, nasze zespoły sprawdziły i monitorowały sytuację
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
August 13, 2026 18:43 UTC Monitoring - We are currently investigating reports of security warnings when accessing sites under *.frontend.site domains which only affects non-production projects. Visitors may experience interstitial browser warnings indicating potential security risks. Our engineering team is actively working with our third-party infrastructure partner to resolve the domain configuration and mitigate the warnings. August 13, 2026 19:44 UTC Monitoring - Our engineering team is co-ordinating with the infrastructure partner and we are awaiting a response from our partner to complete the remediation. We will provide further updates as soon as more information becomes available.
August 6, 2026 18:24 UTC Identified - We are experiencing issues with deployments. Our live services remain unaffected and not impacting active pages but is preventing new deployments from being pushed to production. Our team is investigating the cause and will provide updates as they become available. August 6, 2026 20:22 UTC Identified - We are experiencing issues with deployments. Our live services remain unaffected and active pages are not impacted, but this issue is preventing new deployments from being pushed to production. Our team is waiting for the resolution of the GitHub Actions incident and will provide updates as they become available. August 6, 2026 21:33 UTC Identified - We are experiencing issues with deployments. Our live services remain unaffected, and active pages are not impacted, but this issue is preventing new deployments from being pushed to production. The GitHub Actions incident is still ongoing, and we're continuing to monitor. We'll keep you posted. August 6, 2026 22:41 UTC Identified - We are experiencing issues with deployments. Our live services remain unaffected, and active pages are not impacted, but this issue is preventing new deployments from being pushed to production. The GitHub Actions incident is still ongoing, and we're continuing to monitor. August 6, 2026 23:44 UTC Identified - We are continuing to experience issues with our deployment pipeline, which is preventing new deployments from being pushed to production. Live services and active pages remain unaffected. We will provide further updates as soon as more information becomes available. August 7, 2026 00:49 UTC Identified - We are currently monitoring the situation alongside our deployment partner about the ongoing deployment pipeline issues. Live services and active storefront pages remain fully operational, but new deployments are temporarily prevented from being pushed to production. We will provide further updates as more information becomes available. August 7, 2026 02:41 UTC Resolved - The related Github incident has been marked as resolved. We have restarted our build queue and confirmed that new builds are running normally. Please note that the downtime caused by the Github incident may have caused some builds to fail. If a build is still missing from your CI, you may need to push an empty commit to force a new one.
30 lipca 2026 12: 03 UTC Badanie - Badamy obecnie wzrost błędów w wielu punktach końcowych, głównie wpływających na punkty końcowe związane z projekcją produktu. Nasz zespół inżynieryjny pracuje nad zidentyfikowaniem przyczyny. Dostarczymy aktualizacje, jak tylko pojawi się więcej informacji. 30 lipca 2026 12: 17 UTC Monitoring - Wszystkie systemy działają obecnie normalnie. Dokładnie monitorujemy wydajność i dostarczymy aktualizacje w przypadku wystąpienia jakichkolwiek zmian. 30 lipca 2026 12: 54 UTC Rozwiązanie - Zgłoszona kwestia została pomyślnie rozwiązana. Przepraszamy za wszelkie niedogodności, które mogły spowodować i doceniamy pana zrozumienie, ponieważ pracowaliśmy nad przywróceniem usług.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
30 lipca 2026 09: 19 UTC Badanie - Badamy obecnie wzrost błędów w wielu punktach końcowych. Nasz zespół inżynieryjny pracuje nad zidentyfikowaniem przyczyny. Dostarczymy aktualizacje, jak tylko pojawi się więcej informacji. 30 lipca 2026 09: 27 UTC Monitoring - Wszystkie systemy działają obecnie normalnie. Dokładnie monitorujemy wydajność i dostarczymy aktualizacje w przypadku wystąpienia jakichkolwiek zmian. 30 lipca 2026 10: 00 UTC Rozwiązanie - Zgłoszona kwestia została pomyślnie rozwiązana. Przepraszamy za wszelkie niedogodności, które mogły spowodować i doceniamy pana zrozumienie, ponieważ pracowaliśmy nad przywróceniem usług.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
July 10, 2026 00:49 UTC Investigating - We are experiencing elevated levels of 5xx errors across API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. We are committed to resolving this as swiftly as possible and will provide further updates shortly. July 10, 2026 01:29 UTC Investigating - 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 July 10, 2026 01:41 UTC Identified - 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. July 10, 2026 01:51 UTC Monitoring - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur. July 10, 2026 02:30 UTC Resolved - 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.
July 9, 2026 04:12 UTC Investigating - We are experiencing elevated levels of 5xx errors across carts API endpoints. Our teams are actively investigating the issue and working to mitigate the impact. We are committed to resolving this as swiftly as possible and will provide further updates shortly. July 9, 2026 04:19 UTC Identified - 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. July 9, 2026 04:45 UTC Identified - 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 July 9, 2026 05:14 UTC Identified - Our teams are actively continuing their investigation to troubleshoot the underlying infrastructure. We will continue to provide regular updates as the investigation progresses. July 9, 2026 05:44 UTC Identified - We are actively investigating the root cause of the behavior. We will continue to provide regular updates as we progress in the investigation. July 9, 2026 05:59 UTC Monitoring - 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. July 9, 2026 06:04 UTC Monitoring - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur. July 9, 2026 06:17 UTC Resolved - 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.
June 17, 2026 15:12 UTC Investigating - Subscription messages/change notifications are no longer being sent for: "PaymentTransactionAdded" "PaymentTransactionStateChanged" Affected projects may experience delays or gaps in asynchronous payment notifications. Our engineering team is actively taking mitigative actions to restore normal message processing as quickly as possible. June 17, 2026 15:36 UTC Monitoring - The team has successfully identified the cause of the missing messages. They have taken corrective actions and applied mitigative measures to resolve this. New messages are being sent again. While current messaging functionality is fully operational, messages that failed to trigger during the period of the issue are not being delivered now, we are checking this and will provide further updates on these messages. We understand this disruption is impactful to your operations, appreciate your patience, and are continuing to monitor the infrastructure closely. June 17, 2026 16:07 UTC Monitoring - We are actively investigating an appropriate resolution for the messages that failed to trigger during the period of the disruption. Here are the disruption period per region: GCP US: 12:00 UTC - 15:25 UTC GCP EU: 12:22 UTC - 15:27 UTC We appreciate your patience and will provide further updates once we have more information. June 17, 2026 16:51 UTC Monitoring - Our engineering team is currently executing a remediation process to send and deliver the missing messages. Because this recovery process requires manual intervention this will take time. Please make sure that your services can handle duplicate messages or make sure to check this after the messages have been sent. We appreciate your patience as we work through these steps diligently and will provide further updates as progress continues. June 17, 2026 17:10 UTC Monitoring - Our engineering team is has finished executing the remediation process for missing messages in the GCP US region. We are now working on sending message for projects in the GCP EU region and provide another update once that has been concluded. June 17, 2026 18:12 UTC Resolved - Our engineering team is has finished executing the remediation process for missing messages in the GCP EU region and all messaging are now operating as normal. Once again we thank you for your patience.
May 11, 2026 08:45 UTC Investigating - 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. May 11, 2026 09:02 UTC Monitoring - The errors have now been mitigated, and we are actively investigating the underlying cause of the behavior reported. We will continue to provide regular updates May 11, 2026 09:23 UTC Monitoring - We have identified the cause of the issue, and we have applied the necessary mitigation actions. We are monitoring progress closely, and we will provide updates as necessary. May 11, 2026 11:12 UTC Resolved - 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.
May 10, 2026 07:14 UTC Investigating - The external service is experiencing network issues affecting our Frontend Delivery. Our teams are closely monitoring the situation and working with our partners to ensure that our services are operating correctly. For more details, you can check the partner's status page: https://www.cloudflarestatus.com/ May 10, 2026 07:47 UTC Identified - We have identified that our services are currently being impacted by a widespread network incident involving our external Content Delivery Network (CDN). For more details, you can check the partner's status page: https://www.cloudflarestatus.com/ May 10, 2026 08:12 UTC Monitoring - We are seeing signs of recovery, and our services are beginning to stabilize. We are continuing to monitor the situation closely to ensure full stability before marking this incident as resolved. May 10, 2026 08:28 UTC Resolved - 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.
May 6, 2026 10:12 UTC Investigating - Our CI/CD pipeline is currently experiencing delays 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. May 6, 2026 10:41 UTC Identified - A customer's repository activity triggered a large number of CI builds, causing delays. Our platform is actively working on cleaning the queue. We are already seeing builds return to a green state for many customers. We are continuing to monitor the situation closely to ensure full stability across all accounts. May 6, 2026 11:00 UTC Monitoring - We are now seeing builds returning to green across the platform. While the system appears to be functioning normally, we have moved to the monitoring phase to ensure continued stability. May 6, 2026 11:48 UTC Resolved - 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.
March 30, 2026 13:15 UTC Monitoring - 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 March 30, 2026 13:41 UTC Resolved - 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.
March 24, 2026 10:00 UTC Investigating - GCP Europe 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. Affected endpoints include: - product-related endpoints We are committed to resolving this as swiftly as possible and will provide further updates shortly. March 24, 2026 10:15 UTC Identified - 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. March 24, 2026 10:18 UTC Monitoring - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur. March 24, 2026 10:55 UTC Resolved - 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.
March 19, 2026 15:42 UTC Investigating - 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. Affected endpoints include: -/orders -/in-store//orders We are committed to resolving this as swiftly as possible and will provide further updates shortly. March 19, 2026 16:08 UTC Identified - 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. March 19, 2026 16:21 UTC Monitoring - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur. March 19, 2026 17:08 UTC Resolved - 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.
March 16, 2026 12:34 UTC Investigating - 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. March 16, 2026 12:58 UTC Identified - 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. March 16, 2026 13:09 UTC Monitoring - 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. March 16, 2026 13:26 UTC Monitoring - 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. March 16, 2026 15:09 UTC Resolved - 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.
March 12, 2026 17:00 UTC Identified - 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. Affected endpoints include: - /products/search - /product-projections/search - /graphql We are committed to resolving this as swiftly as possible and will provide further updates shortly. March 12, 2026 17:25 UTC Investigating - 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. March 12, 2026 17:37 UTC Monitoring - We have identified the cause of the issue affecting Product Search in the GCP EU region and corrective actions have been applied. March 12, 2026 18:05 UTC Resolved - 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.
March 6, 2026 17:40 UTC Investigating - 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. We are committed to resolving this as swiftly as possible and will provide further updates shortly. March 6, 2026 17:50 UTC Monitoring - 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. We will continue to monitor the situation and provide updates as necessary. March 6, 2026 18:11 UTC Resolved - 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.
March 5, 2026 09:19 UTC Investigating - 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. March 5, 2026 09:23 UTC Monitoring - All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur. March 5, 2026 10:12 UTC Resolved - 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.