commercetools incident

Elevated API Error Rates - GCP Europe

Minor Resolved View vendor source →

commercetools experienced a minor incident on July 10, 2026 affecting Composable Commerce: APIs and Checkout (Europe (Google Cloud)), lasting 1h 41m. The incident has been resolved; the full update timeline is below.

Started
Jul 10, 2026, 12:49 AM UTC
Resolved
Jul 10, 2026, 02:30 AM UTC
Duration
1h 41m
Detected by Pingoru
Jul 10, 2026, 12:49 AM UTC

Affected components

Composable Commerce: APIsCheckout (Europe (Google Cloud))

Update timeline

  1. investigating Jul 10, 2026, 12:49 AM UTC

    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. 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

  2. investigating Jul 10, 2026, 12:56 AM UTC

    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. We are committed to resolving this as swiftly as possible and will provide further updates shortly.

  3. investigating Jul 10, 2026, 01:29 AM UTC

    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

  4. investigating Jul 10, 2026, 01:29 AM UTC

    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

  5. identified Jul 10, 2026, 01:41 AM UTC

    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.

  6. identified Jul 10, 2026, 01:41 AM UTC

    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.

  7. monitoring Jul 10, 2026, 01:51 AM UTC

    All systems are currently operating normally. We are closely monitoring performance and will provide updates if any changes occur.

  8. resolved Jul 10, 2026, 02:30 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.