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

Morpho incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Partner API Response is degraded15h 12mResolved
Sep 26, 2026Public API Health is down; Public API Response is degraded963h 51mResolved
Sep 23, 2026Public API Response is degraded1023h 33mResolved
Sep 16, 2026Public API Response is degraded1198h 10mResolved
Aug 20, 2026Public API Response is degraded1734h 33mResolved
Aug 18, 2026Public API Response is degraded1791h 0mResolved
Aug 17, 2026Public API Response is degraded1808h 0mResolved
Aug 11, 2026Public API Response is degraded1958h 35mResolved
Aug 7, 2026Public API Response is degraded2063h 13mResolved
Aug 2, 2026Public API Response is degraded2168h 43mResolved
Aug 1, 2026Public API Response is degraded2189h 13mResolved
Jul 20, 2026Morpho API degraded due to CDN config propagation1743h 6mResolved
Jul 16, 2026Morpho API downtime due to AWS CloudFront outage1839h 48mResolved
Jun 1, 2026Public API Response, Partner API Health, and 1 other service are down2202h 33mResolved

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.