commercetools experienced a minor incident on June 17, 2026 affecting Composable Commerce: APIs and Composable Commerce: Merchant Center (North America (AWS)) and 1 more component, lasting 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 17, 2026, 03:12 PM UTC
Subscription messages/change notifications are no longer being sent for PaymentTransactionAdded and OrderPaymentAdded. Affected projects may experience delays or gaps in asynchronous order and payment notifications. Our engineering team is actively taking mitigative actions to restore normal message processing as quickly as possible.
- investigating Jun 17, 2026, 03:12 PM UTC
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. Back to current status SUBSCRIBE Status History Report Issue Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription
- monitoring Jun 17, 2026, 03:36 PM UTC
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.
- monitoring Jun 17, 2026, 03:36 PM UTC
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.
- monitoring Jun 17, 2026, 04:07 PM UTC
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.
- monitoring Jun 17, 2026, 04:07 PM UTC
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.
- monitoring Jun 17, 2026, 04:51 PM UTC
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.
- monitoring Jun 17, 2026, 04:51 PM UTC
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.
- monitoring Jun 17, 2026, 05:10 PM UTC
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.
- monitoring Jun 17, 2026, 05:10 PM UTC
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.
- resolved Jun 17, 2026, 06:12 PM UTC
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.