Skip to main content
Webflow logo

Is Webflow Down?

No — Webflow is up

Reachable from all 6 checked regions

Average response time: 840ms

Last checked · checks run every 6 hours

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

Webflow uptime

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

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means we have no measurement for that window.

30-day history

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

lax
496ms
DNS 0ms TCP 57ms TLS 59ms TTFB 265ms
lhr
603ms
DNS 1ms TCP 74ms TLS 75ms TTFB 304ms
nrt
1369ms
DNS 0ms TCP 170ms TLS 171ms TTFB 686ms
ord
206ms
DNS 0ms TCP 23ms TLS 27ms TTFB 110ms
sin
1853ms
DNS 0ms TCP 230ms TLS 231ms TTFB 927ms
sjc
644ms
DNS 0ms TCP 66ms TLS 68ms TTFB 310ms
syd
1741ms
DNS 0ms TCP 197ms TLS 198ms TTFB 823ms
yyz
189ms
DNS 0ms TCP 19ms TLS 20ms TTFB 112ms

What Webflow does

Webflow is a visual website builder that publishes production sites, combining a design canvas with a CMS and hosting. Marketing teams often own their entire site within it, so an outage can affect the editing experience, the published site, or both, depending on which part of the platform is failing.

What an outage looks like

A Webflow outage looks like two different problems. If the Designer is affected, editing and publishing fail while the live site keeps serving visitors normally. If hosting is affected, visitors see errors on the published site itself. CMS collection items can fail to load in the editor, and form submissions may not be recorded.

What to do about it

Check status.webflow.com, which separates the Designer, the CMS, hosting and forms. Establish first whether visitors are affected or only editors, because the published site is served independently of the editing tools and often stays up. Form submissions made during an incident may never be recorded, so check for gaps afterwards.

Is it down for everyone, or just you?

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

W
WordPress
Netlify
Netlify
Vercel
Vercel
Figma
Figma

Webflow outage FAQ

Is my Webflow site down or just the editor?
They fail independently and are reported separately. The Designer going down stops you editing and publishing while visitors carry on unaffected, which is the more common shape. Loading your live site in a private window is the quickest way to tell which problem you actually have before escalating anything.
Are form submissions lost during a Webflow outage?
Submissions that fail to reach Webflow are generally not recoverable, since nothing else captured them. If forms are the main conversion path on your site, that is the costliest part of an incident. Checking for an unexplained gap in submissions after service returns is worth doing rather than assuming none were attempted.
Can I publish changes while Webflow is having an incident?
Not if publishing is the affected component. Changes saved in the Designer are retained and can be published once the incident clears, so work is not lost, but anything time-sensitive will wait. Avoid repeatedly retrying a publish during an incident, as partial publishes are harder to reason about afterwards.
Does Webflow hosting go down separately from the CMS?
Yes. Hosting serves the published pages while the CMS backs dynamic collection content, and they are reported as separate components. A CMS incident can leave a mostly static site working while collection-driven pages fail, which is why the status page is worth reading rather than testing only the homepage.

How we measure this

  • We request Webflow's public endpoint every 6 hours from Fly.io regions across six continents — 6 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 Webflow publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Webflow 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