Framer Outage History

6 incidents recorded over the last 365 days, 6 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 Framer status99.78% uptime history

Every Recorded Framer Incident

Framer incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 14, 2026Editor is unavailable519h 24mResolved
Sep 22, 2026Elevated errors in AI features1058h 41mResolved
Aug 12, 2026Degraded analytics data collection1932h 45mResolved
Jun 22, 2026Degraded AI usage and analytics data collection1687h 28mResolved
Jun 18, 2026Degraded AI features1794h 2mResolved
Jun 13, 2026Database Upgrade28 minResolved

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 Framer 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 Framer 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 Framer 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 Framer outage in this window ran 80d 12h, against a mean recovery of 48d 13h. If you depend on Framer 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.