Skip to main content
Jotform logo

Is Jotform Down?

No — Jotform is up
Jotform's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 751 ms

Right now

The verdict is the worse of these two. How we decide

Jotform's status page

status.jotform.com · read · checked every 3 minutes

Operational
Jotform's components, as its status page reports them
ComponentStatus
FormsOperational
Submission ServiceOperational
Notification ServiceOperational
IntegrationsOperational
Jotform GlobalOperational
Jotform EuropeOperational
APIOperational
HIPAAOperational

FlareWarden checks

jotform.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
751 ms
Checked

By region

  • Chicago reachable, 570 ms
  • Johannesburg reachable, 1207 ms
  • London reachable, 667 ms
  • Los Angeles reachable, 608 ms
  • San Jose reachable, 604 ms
  • Singapore reachable, 845 ms
  • Sydney reachable, 600 ms
  • Tokyo reachable, 907 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Chicago36 ms21 ms25 ms457 ms
Johannesburg15 ms2 ms8 ms850 ms
London56 ms4 ms13 ms497 ms
Los Angeles91 ms2 ms8 ms549 ms
San Jose73 ms12 ms17 ms536 ms
Singapore26 ms2 ms8 ms542 ms
Sydney103 ms2 ms9 ms587 ms
Tokyo114 ms1 ms8 ms684 ms
We check that jotform.com loads, not every feature behind it. Test it yourself

History

Incidents Jotform reported

Since Oct 22, 15 days · from status.jotform.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Jotform website availability

Measured by FlareWarden · jotform.com

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

Last 30 days

91-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 31 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 32 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 29 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 31 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of jotform.com from multiple regions every 6 hours. Jotform's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three 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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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 the verdict is the worse of what it reports and what our checks see: a major outage of Jotform itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Jotform goes down

We check Jotform every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required