Skip to main content
Webflow logo

Is Webflow Down?

No — Webflow is up

Reachable from all 8 checked regions

Average response time: 1073ms

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
870ms
Avg response, 30 days

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

30-day history

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

ams
726ms
DNS 10ms TCP 88ms TLS 90ms TTFB 370ms
arn
939ms
DNS 17ms TCP 109ms TLS 110ms TTFB 499ms
nrt
1451ms
DNS 43ms TCP 170ms TLS 171ms TTFB 771ms
ord
441ms
DNS 250ms TCP 19ms TLS 20ms TTFB 361ms
sin
2477ms
DNS 260ms TCP 228ms TLS 583ms TTFB 1564ms
sjc
596ms
DNS 51ms TCP 67ms TLS 68ms TTFB 324ms
syd
1798ms
DNS 160ms TCP 203ms TLS 205ms TTFB 981ms
yyz
157ms
DNS 7ms TCP 17ms TLS 19ms TTFB 84ms

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 up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

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 — 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 Webflow 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 Webflow 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