Is Webflow Down?

No — Webflow is up

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

Right now

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

Webflow's status page

status.webflow.com · read 3 minutes ago · checked every 3 minutes

Operational

Webflow's components, as its status page reports them
Component	Status
Data API	Operational
MCP Server	Operational
Site Pages	Operational
Localize	Operational
Ecommerce	Operational
Forms	Operational
Site search	Operational
SSL certificate provisioning	Operational
Webflow.com the service itself	Operational
University	Operational
Support Portal	Operational
Marketplace	Operational

7 more, all operational · show all 19

All of Webflow's components
Component	Status
API & MCP Server
Data API	Operational
MCP Server	Operational
Hosted Websites
Site Pages	Operational
Localize	Operational
Ecommerce	Operational
Forms	Operational
Site search	Operational
SSL certificate provisioning	Operational
Webflow.com & Marketplace
Webflow.com	Operational
University	Operational
Support Portal	Operational
Marketplace	Operational
Analyze & Optimize
Analyze	Operational
Optimize for Webflow sites	Operational
Optimize for non-Webflow sites	Operational
Webflow Canvas	Operational
Dashboard	Operational
Publishing	Operational
Email Notifications	Operational

Open their status page

FlareWarden checks

webflow.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: 1038 ms
Checked: 52 minutes ago

By region

Amsterdam reachable, 822 ms
Chicago reachable, 363 ms
London reachable, 905 ms
San Jose reachable, 679 ms
Singapore reachable, 1894 ms
Sydney reachable, 1652 ms
Tokyo reachable, 1670 ms
Toronto reachable, 320 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	31 ms	97 ms	99 ms	428 ms
Chicago	118 ms	22 ms	23 ms	273 ms
London	33 ms	99 ms	101 ms	504 ms
San Jose	117 ms	68 ms	70 ms	399 ms
Singapore	99 ms	223 ms	224 ms	997 ms
Sydney	52 ms	199 ms	200 ms	853 ms
Tokyo	151 ms	180 ms	181 ms	946 ms
Toronto	85 ms	20 ms	21 ms	235 ms

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

History

Incidents Webflow reported

Since Oct 22, 15 days · from status.webflow.com

Incidents: 1
Major or critical: 1
Median to resolve: 1h 11m

[MONITORING] Reports of issues accessing the Dashboard for some customers
critical · Nov 4
lasted 1h 11m

Webflow website availability

Measured by FlareWarden · webflow.com

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

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

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 17 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. 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 Webflow 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 Webflow 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 Webflow goes down

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