Strapi Outage History

7 incidents recorded over the last 365 days, 7 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.

Live Strapi status99.88% uptime history

Every Recorded Strapi Incident

Strapi incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jul 21, 2026Projects unavailable following a redeployment815h 7mResolved
Jul 20, 2026Compute provider deployment outage831h 7mResolved
Jun 16, 2026Deployment failures1649h 41mResolved
May 22, 2026Delayed / Failed API responses1687h 11mResolved
Feb 24, 2026Project creation unavailable1569h 48mResolved
Feb 12, 2026Issues with Login with Magic Link1849h 8mResolved
Jan 7, 2026Runtime logs service degradation2007h 8mResolved

How to Read This Strapi 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 Strapi 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 Strapi outage in this window ran 83d 15h, against a mean recovery of 61d 23h. If you depend on Strapi 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.