Commercetools Outage History
5 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Commercetools Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Deployments issuesOur CI/CD pipeline is currently experiencing delays and is temporarily unavailable due to an issue with a third-party service provider. This is preventing new builds and deployments, though previously successful builds… | 43 min | Resolved |
| Oct 13, 2026 | Elevated API Error Rates - GCP North AmericaWe 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… | 5 min | Resolved |
| Sep 24, 2026 | Merchant Center - issue with navigation and discoverability of custom apps and custom viewsWe are currently investigating an issue affecting the Composable Commerce Merchant Center. Affected projects may observe that custom apps and Custom Views are not displayed within the left-hand navigation menu or on… | 2h 45m | Resolved |
| Aug 24, 2026 | One year of Identity: time to check your Enterprise SSO credential expiryScheduled Maintenance | 2h 0m | Scheduled |
| Aug 13, 2026 | Security Warnings on Frontend DomainsWe 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… | 32 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Commercetools incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Commercetools Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Commercetools acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Commercetools outage in this window ran 2h 45m, against a mean recovery of 1h 13m. If you depend on Commercetools in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.