- Service Status
- /
- Jotform

Is Jotform Down?
- 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
| Component | Status |
|---|---|
| Forms | Operational |
| Submission Service | Operational |
| Notification Service | Operational |
| Integrations | Operational |
| Jotform Global | Operational |
| Jotform Europe | Operational |
| API | Operational |
| HIPAA | Operational |
FlareWarden checks
jotform.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- 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
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Chicago | 36 ms | 21 ms | 25 ms | 457 ms |
| Johannesburg | 15 ms | 2 ms | 8 ms | 850 ms |
| London | 56 ms | 4 ms | 13 ms | 497 ms |
| Los Angeles | 91 ms | 2 ms | 8 ms | 549 ms |
| San Jose | 73 ms | 12 ms | 17 ms | 536 ms |
| Singapore | 26 ms | 2 ms | 8 ms | 542 ms |
| Sydney | 103 ms | 2 ms | 9 ms | 587 ms |
| Tokyo | 114 ms | 1 ms | 8 ms | 684 ms |
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 streakMeasured 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.
Related services
Jotform outage FAQ
Are submissions lost during a Jotform outage?
I got no email but is the submission there?
Which Jotform environment should I check?
Do embedded forms break the page they sit on?
Do file uploads survive an outage?
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
403or429means 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


