Is Webflow Down? How to Check Webflow Status Right Now

Webflow is hosting infrastructure, design tool, and CMS in a single platform — when it works, you barely think about it. When Webflow goes down, the consequences stack fast: published sites go offline for visitors, Editors can't publish content updates, Ecommerce checkouts break, and form submissions vanish. Unlike single-purpose tools, a Webflow outage touches multiple business functions at once.

Here's how to quickly determine whether Webflow is down, identify which component is failing, and limit impact on your sites and customers.

Is Webflow Down Right Now?

Check these sources in order:

1. Statusfield — Webflow status — real-time monitoring across Webflow's hosting CDN, Designer, Editor, CMS, and Ecommerce.
2. Twitter/X — search Webflow down or Webflow publish failed sorted by Latest. Webflow users are vocal about outages, especially publish failures.
3. Downdetector — useful for confirming user-reported spikes but lacks component-level granularity.

What Actually Breaks During a Webflow Outage

Webflow runs several independent subsystems. A degradation in one doesn't automatically affect the others.

Component	What it does	Impact when down
Hosting / CDN	Serves published Webflow sites to visitors via global CDN	Sites go offline or return errors for all visitors worldwide
Designer	Web-based visual development environment	Designers can't edit or build; canvas may fail to load
Editor	In-context content editing for non-technical users	Editors can't update content; publish button may fail silently
CMS API	REST API for reading and writing CMS collection data	Integrations and external tools reading/writing content stop working
Ecommerce	Product catalog, cart, checkout, and order processing	Purchases fail; cart items may not persist; orders don't complete
Forms	Webflow-hosted form submission and notification	Form submissions are lost or not delivered to your inbox
Workspaces / Dashboard	Project management, team access, billing, settings	Account management unavailable; can't add team members or access projects
Publish pipeline	Processes Designer or Editor publish actions to CDN	Publish appears to succeed but changes don't go live

Common Webflow Error Symptoms

What you see	What it usually means
Site returns 502 or 503 for visitors	CDN or hosting layer degraded
Publish button shows spinner indefinitely	Publish pipeline is failing or queued
"Publish failed" error in Designer/Editor	Build pipeline error; may be Webflow or your site's complexity
CMS API returns 500 or times out	CMS API layer degraded
Forms submit but email notification never arrives	Form processing degraded; submission may be captured but not delivered
Designer canvas shows blank or fails to connect	Designer back-end or asset loading failing
Ecommerce checkout returns error on payment step	Ecommerce integration or payment processor degraded
Changes visible in Editor but not live after publish	Publish pipeline or CDN cache invalidation failing

Key distinction: The Webflow Editor and CDN hosting are separate subsystems. A Designer/Editor outage does not mean your live sites are down — and a CDN outage can take your published sites offline even when the Designer is fully operational.

How Webflow's Architecture Affects Outage Scope

Hosting and publishing are decoupled. Webflow serves live sites from its CDN independently of the Designer and Editor. When you publish, a build pipeline converts your design into static assets and pushes them to the CDN. A failure in the build pipeline means changes don't reach the CDN — your live site remains on the last successful publish. This is usually acceptable for short outages but becomes a problem when critical content changes (price updates, breaking news, emergency CTAs) can't go live.

Custom domains rely on DNS and SSL certificate provisioning. If you're adding a new custom domain during an outage, SSL certificate provisioning may fail silently. Existing SSL certificates renew automatically, so existing custom domains are not affected by provisioning issues.

Ecommerce checkout relies on a payment processor (typically Stripe) in addition to Webflow. A checkout failure may originate from Webflow's Ecommerce layer, the payment processor, or the integration between them. Check Statusfield for Webflow status and separately verify Stripe status if the issue is on the payment step specifically.

The CMS API is versioned and separate from the CDN. Changes made via the CMS API do not automatically rebuild your site — you still need to trigger a publish. If your integration writes to the CMS API and then triggers a site publish, an API degradation and a publish pipeline degradation are two distinct failure modes.

Is It Webflow or Your Site Configuration?

Before concluding it's a Webflow outage, rule out configuration issues:

Your site has a complex build that exceeds Webflow's publish limits. Very large Webflow projects — thousands of CMS items, complex nested collections, or heavy JavaScript bundles — can hit publish timeouts. If publish failures are scoped to one project while others publish fine, the issue is likely your site's complexity, not Webflow's infrastructure.

Your custom domain DNS isn't propagated. If you recently changed your domain's DNS records or added a custom domain, propagation delay may look like a Webflow outage. Verify directly at your Webflow subdomain (e.g., yourproject.webflow.io) to isolate whether the issue is DNS or hosting.

Your CMS API key lacks the right permissions. If an integration is returning 401 Unauthorized from the CMS API, the issue is your API token's scope, not Webflow's infrastructure. Check that your token has read/write access to the relevant collection.

Your form notification email is filtered or bouncing. Webflow sends form submissions to the email address configured in your project settings. If those emails end up in spam or the delivery address is bouncing, it looks like form failures — but the submissions were captured. Check your project's form submissions dashboard before concluding the form system is down.

When these are ruled out and failures persist across projects, the evidence points to a Webflow infrastructure issue. Confirm at Statusfield.

Hardening Your Sites Against Webflow Outages

1. Keep a pre-publish backup of critical content

Before publishing major content updates, export or snapshot your current live site's critical text (pricing, contact information, key CTAs). If a publish fails mid-rollout, you need to know what the live site currently shows — not just what's in the Editor.

2. Use a staging project for build validation

Large or complex Webflow projects can take minutes to publish. Create a staging project (a duplicate of your production site) to test publish reliability before pushing changes to production. If the staging publish fails, investigate before touching the live site.

3. Add monitoring for your live domain

Don't rely solely on Webflow's status page. Statusfield monitors Webflow's infrastructure continuously, but you should also monitor your specific live domain for uptime. A CDN edge issue may affect specific regions even when Webflow's overall status shows operational.

4. Have a static fallback for Ecommerce outages

For Ecommerce sites, display a prominent message when checkout is unavailable — a banner with an alternative purchase path (phone, email order form) is better than a broken checkout that silently fails. Detect failed Stripe loads or Webflow Ecommerce API errors and display the fallback message automatically.

5. Set up CMS API retry logic in your integrations

If you use the CMS API to sync content from external sources, build in retry logic with exponential backoff. A brief CMS API degradation shouldn't cascade into a full sync failure — most outages resolve within minutes, and queued retries keep data consistent.

How to Stay Ahead of Webflow Outages

The goal is to know Webflow is degraded before your clients or visitors do.

Statusfield monitors Webflow continuously and delivers alerts the moment a degradation is detected — through Slack, Discord, email, or webhook. On the free plan you get 3 monitors and 10 alerts/month, no credit card required.

→ Monitor Webflow on Statusfield — free, no credit card required

FAQ

Webflow publish is stuck or failing. Is Webflow down?

Not necessarily — publish failures can be caused by site complexity (large CMS collections, heavy asset bundles) rather than Webflow's infrastructure. First, check Statusfield to see if the publish pipeline is reporting degradation. If Statusfield shows Webflow operational, try publishing a minimal test project. If that publishes fine, the issue is scoped to your site's build, not Webflow's infrastructure.

My Webflow site is down but the Designer works fine. What's happening?

Webflow's hosting CDN and the Designer are separate subsystems. A CDN or hosting degradation takes live sites offline while the Designer remains fully functional. Check Statusfield specifically for hosting status. You can also verify at your Webflow subdomain (yourproject.webflow.io) — if that's also offline, the issue is in Webflow's hosting layer.

Is Webflow down for everyone or just my site?

Check Statusfield first. If Statusfield shows Webflow hosting as degraded, the impact is broad. If Statusfield shows operational status, the issue is likely scoped to your site — custom domain DNS, SSL certificate provisioning, or a site-specific build problem. Try accessing your Webflow subdomain directly to bypass custom domain issues.

Webflow form submissions aren't arriving. What should I check?

First, check Statusfield for form processing status. If Webflow shows operational, check your project's form submissions in the Webflow dashboard — submissions may have been captured but the email notification is failing. Verify the notification email address in your project settings and check spam folders. Also confirm the form's reCAPTCHA or bot protection isn't blocking legitimate submissions.

How long do Webflow outages typically last?

Most Webflow degradations are partial — affecting one component (publish pipeline, CMS API, or a specific CDN region) while others remain operational. These typically resolve within 15–60 minutes. Full hosting outages that affect live site visitors are rare and usually resolve within 1–2 hours. Monitor Statusfield for live updates during an incident.