Skip to main content
Fillout logo

Is Fillout Down?

No — Fillout is up

Reachable from all 8 checked regions

Average response time: 178ms

Last checked · checks run every 6 hours

Official status page: https://fillout.statuspage.io

Fillout uptime

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

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 27 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

27-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: 100.00% uptime, 16 checks
Aug 26: 100.00% uptime, 32 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 31 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 31 checks
Sep 2: 100.00% uptime, 31 checks
Sep 3: 100.00% uptime, 21 checks
Sep 4: 100.00% uptime, 22 checks
Sep 5: 100.00% uptime, 32 checks
Sep 6: 100.00% uptime, 32 checks
Sep 7: 100.00% uptime, 29 checks
Sep 8: 100.00% uptime, 49 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 36 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 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.

ewr
123ms
DNS 73ms TCP 1ms TLS 20ms TTFB 115ms
fra
78ms
DNS 39ms TCP 1ms TLS 18ms TTFB 71ms
gru
303ms
DNS 265ms TCP 1ms TLS 12ms TTFB 295ms
iad
160ms
DNS 123ms TCP 1ms TLS 7ms TTFB 151ms
jnb
184ms
DNS 55ms TCP 0ms TLS 60ms TTFB 155ms
lax
187ms
DNS 110ms TCP 1ms TLS 27ms TTFB 163ms
lhr
127ms
DNS 68ms TCP 3ms TLS 9ms TTFB 120ms
nrt
266ms
DNS 225ms TCP 1ms TLS 10ms TTFB 259ms

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 18 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.
  • 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 Fillout publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Fillout goes down

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

Start Free Monitoring
Free plan available No credit card required