Elastic Path Outage History
7 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 Elastic Path Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 13, 2026 | Database maintenance NAThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Oct 1, 2026 | Degraded Performance — Commerce ManagerBetween 12:50 and 12:55 UTC, Commerce Manager experienced degraded performance and users may not have been able unable to access Commerce Manager during this time. We have identified the root cause and the issue has… | -35 min | Resolved |
| Sep 21, 2026 | Degraded Performance — US Elevated ErrorsBetween 11:45 and 11:49 UTC, a proportion of requests to the API in the US Region experienced elevated error rates. The affected requests in flight during this window either timed out or returned 5xx responses. The EU… | -41 min | Resolved |
| May 4, 2026 | Degraded Performance Publications - US onlyThis incident has been resolved. | 23h 32m | Resolved |
| Mar 19, 2026 | Degraded performance - Elevated ErrorsThe incident has been resolved. | 14 min | Resolved |
| Feb 26, 2026 | NA Search Infrastructure MaintenanceThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Feb 25, 2026 | EU Search Infrastructure MaintenanceThe scheduled maintenance has been completed | 4h 0m | Scheduled |
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 Elastic Path 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 Elastic Path 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 Elastic Path 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 Elastic Path outage in this window ran 23h 32m, against a mean recovery of 6h 57m. If you depend on Elastic Path 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.