Is Fillout Down?

No — Fillout is up

Fillout's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 212 ms

Right now

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

Fillout's status page

fillout.statuspage.io · read 2 minutes ago · checked every 3 minutes

Operational

Fillout's components, as its status page reports them
Component	Status
Forms (respondent experience)	Operational
Form editor	Operational
Workspaces, Settings & Admin	Operational
Developer API	Operational
Zite Database	Operational
Zite Apps	Operational
Zite App Editor	Operational

Open their status page

FlareWarden checks

fillout.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: 212 ms
Checked: 2 hours ago

By region

Ashburn reachable, 128 ms
Chicago reachable, 179 ms
Johannesburg reachable, 239 ms
London reachable, 104 ms
Los Angeles reachable, 148 ms
Singapore reachable, 291 ms
São Paulo reachable, 320 ms
Tokyo reachable, 292 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	97 ms	1 ms	7 ms	116 ms
Chicago	126 ms	1 ms	22 ms	167 ms
Johannesburg	91 ms	1 ms	63 ms	208 ms
London	64 ms	2 ms	8 ms	92 ms
Los Angeles	84 ms	2 ms	28 ms	136 ms
Singapore	216 ms	1 ms	9 ms	285 ms
São Paulo	287 ms	2 ms	7 ms	312 ms
Tokyo	257 ms	2 ms	8 ms	285 ms

We check that fillout.com loads, not every feature behind it. Test it yourself

History

Incidents Fillout reported

Since Oct 22, 15 days · from fillout.statuspage.io

Incidents: 1
Major or critical: 1
Median to resolve: 25m

Some Zite Custom Domains Unresponsive
major · Oct 22
lasted 25m

Fillout website availability

Measured by FlareWarden · fillout.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 185ms

Last 30 days

73-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

What Fillout does

Fillout is a form, quiz and survey builder used by more than 100,000 organizations for data intake. Forms can take payments, generate PDFs, schedule meetings and route submissions through conditional logic, with over 50 native integrations to push answers into other tools. Teams embed it in signup flows and internal request processes, so it usually sits at the front of a workflow rather than inside it.

What an outage looks like

Embedded and hosted forms fail to load for respondents, or accept answers and then error on submit. The form editor may be unreachable while published forms keep collecting, or the reverse. Integrations stop pushing submissions into connected tools, so answers exist in Fillout but never arrive in your CRM or spreadsheet. Developer API calls that read or create submissions return errors.

What to do about it

Check fillout.statuspage.io, which is published under the Zite name and reports Forms (respondent experience) separately from the Form editor, Workspaces, the Developer API and the Zite app components. The respondent row is the one that matters if you have forms live in a campaign. Avoid rebuilding a form during an incident, and check for duplicate submissions afterwards if respondents retried.

Is it down for everyone, or just you?

If this page says Fillout 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

Fillout outage FAQ

Can people still fill in my form if Fillout is down?

It depends which component failed. The status page lists Forms (respondent experience) separately from the Form editor, precisely because they can fail independently. If only the editor is affected, published forms keep collecting answers and respondents see nothing wrong. If the respondent row is affected, embedded and hosted forms fail to load and submissions are not reaching you.

Why is the status page branded Zite rather than Fillout?

Zite is the parent company. Fillout grew as a form builder past 10,000 paying customers, and the company later built Zite as a broader app-building platform; Fillout remains its own product at fillout.com under the same account. The shared status page therefore lists Fillout's form components alongside Zite Apps, the Zite App Editor and the Zite Database.

Will I lose submissions that were in progress?

Answers already submitted and recorded are held in Fillout, and an incident affecting the editor or the API does not remove them. What is genuinely at risk is a response someone was part-way through when the form stopped responding, since that had not reached Fillout yet. After an incident, check for duplicates from respondents who submitted twice.

Does a Fillout outage break my integrations?

It can, and the failure is quiet. Fillout pushes submissions into connected tools through its integrations, so during an incident an answer can be captured by the form while never arriving in the CRM, spreadsheet or automation on the other side. The Developer API is a separate component again, so custom code reading submissions can fail while the forms themselves are fine.

How we measure this

We request Fillout'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 Fillout 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 Fillout 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 Fillout goes down

We check Fillout 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