commercetools experienced a minor incident on May 11, 2026 affecting Composable Commerce: APIs and Checkout (Europe (Google Cloud)), lasting 2h 27m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 11, 2026, 08:45 AM UTC
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. Back to current status SUBSCRIBE Status 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
- investigating May 11, 2026, 08:56 AM UTC
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.
- monitoring May 11, 2026, 09:02 AM UTC
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
- monitoring May 11, 2026, 09:14 AM UTC
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
- monitoring May 11, 2026, 09:23 AM UTC
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.
- resolved May 11, 2026, 11:12 AM UTC
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.