Morpho Outage History
14 incidents recorded over the last 365 days, 14 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 Morpho Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Partner API Response is degraded | 15h 12m | Resolved |
| Sep 26, 2026 | Public API Health is down; Public API Response is degraded | 963h 51m | Resolved |
| Sep 23, 2026 | Public API Response is degraded | 1023h 33m | Resolved |
| Sep 16, 2026 | Public API Response is degraded | 1198h 10m | Resolved |
| Aug 20, 2026 | Public API Response is degraded | 1734h 33m | Resolved |
| Aug 18, 2026 | Public API Response is degraded | 1791h 0m | Resolved |
| Aug 17, 2026 | Public API Response is degraded | 1808h 0m | Resolved |
| Aug 11, 2026 | Public API Response is degraded | 1958h 35m | Resolved |
| Aug 7, 2026 | Public API Response is degraded | 2063h 13m | Resolved |
| Aug 2, 2026 | Public API Response is degraded | 2168h 43m | Resolved |
| Aug 1, 2026 | Public API Response is degraded | 2189h 13m | Resolved |
| Jul 20, 2026 | Morpho API degraded due to CDN config propagation | 1743h 6m | Resolved |
| Jul 16, 2026 | Morpho API downtime due to AWS CloudFront outage | 1839h 48m | Resolved |
| Jun 1, 2026 | Public API Response, Partner API Health, and 1 other service are down | 2202h 33m | 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 Morpho 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 Morpho 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 Morpho 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 Morpho outage in this window ran 91d 18h, against a mean recovery of 67d 13h. If you depend on Morpho 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.