Skip to main content
Jotform logo

Is Jotform Down?

No — Jotform is up

Reachable from all 8 checked regions

Average response time: 958ms

Last checked · checks run every 6 hours

Official status page: https://status.jotform.com

Jotform uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1044ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 22 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

dfw
1016ms
DNS 53ms TCP 1ms TLS 7ms TTFB 1002ms
ewr
686ms
DNS 17ms TCP 6ms TLS 12ms TTFB 651ms
fra
829ms
DNS 12ms TCP 0ms TLS 7ms TTFB 711ms
gru
859ms
DNS 13ms TCP 1ms TLS 8ms TTFB 672ms
iad
701ms
DNS 23ms TCP 1ms TLS 6ms TTFB 691ms
jnb
1334ms
DNS 175ms TCP 1ms TLS 8ms TTFB 1015ms
lax
826ms
DNS 119ms TCP 20ms TLS 40ms TTFB 817ms
lhr
891ms
DNS 20ms TCP 1ms TLS 8ms TTFB 768ms
nrt
1543ms
DNS 122ms TCP 1ms TLS 8ms TTFB 1317ms

What Jotform does

Jotform builds online forms for registrations, applications, payments and surveys, embedded on websites or shared as links. The forms are usually customer-facing, so an outage is not felt by the team that built them but by the people trying to submit, who see a failure and rarely come back.

What an outage looks like

Forms fail to load where they are embedded, leaving a blank space on an otherwise working page. Submissions error on send, or appear to succeed without arriving in the inbox. File uploads attached to a submission fail while the rest of the form works. Notification emails do not arrive, and integrations that forward submissions elsewhere stop firing.

What to do about it

Check status.jotform.com, which reports Forms, the Submission Service, the Notification Service, Integrations and the API separately, and splits Jotform Global from Jotform Europe and the HIPAA environment. Confirm which environment your account uses. Check the submission list rather than your inbox, since notifications fail independently of submissions being recorded.

Is it down for everyone, or just you?

If this page says Jotform is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Jotform outage FAQ

Are submissions lost during a Jotform outage?
Submissions the platform accepted are stored and appear in your account. The genuine loss is the person who hit a form that would not load or would not submit, because nothing about that attempt is captured. For a form tied to a deadline, that silent loss is the real cost rather than any missing stored data.
I got no email but is the submission there?
Very possibly. The Notification Service is a separate component from the Submission Service, so a submission can be recorded correctly while the email announcing it never sends. Always check the submissions list in your account before telling someone their form did not go through. Delayed notifications frequently arrive once the component recovers.
Which Jotform environment should I check?
Jotform reports Jotform Global, Jotform Europe and a HIPAA environment separately, and your account is on one of them. Accounts created under European data residency or with HIPAA compliance enabled do not follow the global status. Checking the wrong environment gives an answer that has nothing to do with your forms.
Do embedded forms break the page they sit on?
No. An embedded form loads in its own frame, so a Jotform incident leaves a gap on your page while everything else renders normally. Visitors usually read that as a broken website rather than a third-party outage. During a long incident, replacing the embed with an email address keeps enquiries coming in.
Do file uploads survive an outage?
Uploads are the most fragile part of a submission, since they are larger and take longer. A submission can be recorded with its text fields intact while the attached file failed to store. If uploads matter, check a sample of submissions taken during the incident and ask those people to resend files if they are missing.

How we measure this

  • We request Jotform's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Jotform publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Jotform goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required