Jotform Outage History

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

Jotform incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Feb 19, 2026Service DisruptionWe are currently experiencing a service disruption. Our team is actively investigating and working to restore full stability as soon as possible.-228 minResolved
Feb 9, 2026Jotform OutageThe issue has been identified and resolved. All systems should be functional now.1h 53mResolved
Nov 18, 2025Cloudflare OutageOn 18 November 2025, our platform experienced service disruptions due to a global Cloudflare outage affecting multiple regions and services worldwide. During this period, some users may have encountered slow responses…0 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 Jotform 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 Jotform 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 Jotform 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 Jotform outage in this window ran 1h 53m, against a mean recovery of 57 min. If you depend on Jotform 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.