Skip to main content

Is Typeform Down?

No — Typeform is up

Reachable from all 8 checked regions

Average response time: 114ms

Last checked · checks run every 6 hours

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

Typeform uptime

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

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

30-day history

25-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 32 checks
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 24 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 40 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 31 checks
Aug 17: 100.00% uptime, 40 checks
Aug 18: 100.00% uptime, 40 checks
Aug 19: 100.00% uptime, 40 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 36 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 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
79ms
DNS 0ms TCP 1ms TLS 3ms TTFB 73ms
fra
73ms
DNS 0ms TCP 1ms TLS 4ms TTFB 67ms
gru
68ms
DNS 0ms TCP 3ms TLS 5ms TTFB 55ms
iad
77ms
DNS 1ms TCP 2ms TLS 5ms TTFB 66ms
jnb
227ms
DNS 0ms TCP 0ms TLS 3ms TTFB 224ms
lax
94ms
DNS 1ms TCP 1ms TLS 4ms TTFB 88ms
lhr
69ms
DNS 0ms TCP 2ms TLS 4ms TTFB 61ms
nrt
64ms
DNS 0ms TCP 1ms TLS 4ms TTFB 57ms
ord
243ms
DNS 0ms TCP 2ms TLS 4ms TTFB 236ms

What Typeform does

Typeform builds conversational forms and surveys that ask one question at a time, used for lead capture, customer research, event registration and job applications. Forms are usually embedded in someone else's website or shared as a link, so the people affected by an outage are typically respondents who have no idea Typeform is involved.

What an outage looks like

Embedded forms fail to render and leave a blank space in an otherwise working page, or load but reject the final submission, so a respondent who filled everything in sees an error at the last step. Shared links return errors, webhooks to downstream systems are delayed, and the builder may refuse to publish changes while existing forms carry on serving normally.

What to do about it

Check status.typeform.com, which separates form rendering and response submission from the builder, the Responses and Webhooks APIs, embeds and OAuth login. If only the builder is affected, live forms are still collecting. Where a campaign depends on it, pause the traffic you are sending rather than letting respondents hit a broken form, and check webhook-driven systems for gaps afterwards.

Is it down for everyone, or just you?

If this page says Typeform 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
Jotform
Calendly
Calendly
Airtable
Airtable
DocuSign
DocuSign

Typeform outage FAQ

Are responses lost if Typeform goes down mid-submission?
A response that was never submitted is lost, because the answers live in the respondent's browser until they reach Typeform. Responses already recorded are safe and appear once the platform recovers. The practical risk is silent: someone abandons a form that failed at the last step and does not come back, so you see a dip in completions rather than an error.
Is Typeform down or is my embed broken?
Embeds are tracked separately from form rendering on Typeform's status page, so check both before editing your site. A form that works at its typeform.com link but not on your page points at the embed rather than the platform. If neither is flagged as degraded, look at content blockers and content security policy rules, which break embedded forms in exactly this way.
Do webhooks fire for responses collected during an outage?
They may arrive late rather than not at all, since the Webhooks API is a separate component from response submission. Responses can be recorded while delivery to your systems lags, which leaves the CRM or spreadsheet on the other end incomplete for a while. Reconcile against the response list in Typeform afterwards rather than assuming everything downstream arrived.
Can I still edit forms while Typeform is having problems?
Sometimes, because the builder is listed apart from the runtime components. When only the builder is degraded, published forms keep collecting responses while you cannot change them, which is inconvenient but harmless. The reverse also happens: the builder works while form rendering fails, so verify by opening a live form rather than judging from the editor.
How do I know how many responses an outage cost me?
Compare completion rates either side of the incident window rather than counting errors, since abandoned attempts leave no record. Typeform reports partial responses for forms that were started but not finished, which is the closest signal available. Note the start and end times from the status page so the gap is explainable when someone reviews the campaign later.

How we measure this

  • We request Typeform'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 Typeform 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 Typeform 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