Is Webflow down — or is it just your app?
The live indicator below comes straight from status.webflow.com. If Webflow reports a hosting or CDN incident, every published site is affected and the fix is on their side. More often, though, Webflow is green and your site is still broken for visitors: a form that stopped delivering leads, a third-party script that errors, or an expired site plan. Here is how to tell which one you have.
Checking Webflow's official status… live from status.webflow.com
Nightlamp is not affiliated with Webflow and this is not the official status page. For platform incidents, the source of truth is status.webflow.com. This page exists for the other half of the question: what to do when the platform is green and your app still isn't working.
What status.webflow.com does tell you
- Published-site hosting and CDN availability
- The Designer and dashboard
- Form submission backend incidents
- CMS API and publishing pipeline incidents
Webflow can be green while your app is down
Forms submit but the lead never reaches you
Form notification emails land in spam, the notification address is stale, or the monthly submission limit on your plan is hit. Visitors see a success message; you silently lose every lead. Webflow's status page has nothing to report.
Custom code broke the page
An embedded third-party script (chat widget, analytics, payment embed) changed or went down, and now it blocks rendering or throws errors on your most important page. That's between your embed and the third party — not Webflow infrastructure.
Your CMS-driven automation stopped
Zapier/Make scenarios that publish CMS items or sync data fail on an expired token or a renamed field. The site looks fine; the content pipeline behind it is dead.
The site plan or domain lapsed
An expired card on the site plan or a missed domain renewal takes yourdomain.com offline while webflow.io keeps working — and while status.webflow.com stays green.
Platform problem or your problem? Run this checklist
- Check status.webflow.com — an active hosting/CDN incident affects all published sites.
- Load your site on the .webflow.io staging domain: if staging works but your domain doesn't, it's DNS, SSL, or a lapsed plan.
- Submit your most important form and confirm the notification actually arrives.
- Open the browser console on the broken page — custom-code errors show up there, not on any status page.
- Check your Zapier/Make run history for failed scenarios.
- If login or gated content is involved, trigger the auth email and confirm delivery.
If sign-in emails are part of the broken flow, our free magic-link tester checks the full email round-trip in one click.
Checklist points at your own app? Our guide to fixing forms that submit but deliver no lead walks through each failure symptom by symptom.
Stop checking status pages after the fact
Nightlamp watches your Webflow app's actual flows — checkout, signup, login emails, scheduled jobs — and a real engineer sends a plain-English diagnosis when one breaks, whether or not the platform is having an incident.
Start 14-day trial · no cardFrequently asked questions
Webflow's status page is green but my site is down. Why?
status.webflow.com covers Webflow's hosting, Designer, and form backend. Lapsed site plans, expired domains, broken custom code embeds, hit form-submission limits, and failed third-party integrations all break your site without ever appearing on Webflow's status page.
Does Webflow's status page tell me when my forms stop delivering leads?
Only if Webflow's form backend itself has an incident. The far more common failures — notification emails in spam, a stale notification address, or a hit submission limit — are invisible to it. Test the full form-to-inbox path yourself, or monitor it continuously.
How do I get alerted when my Webflow site breaks but Webflow is up?
Monitor your site's actual flows: the form-to-lead path, the pages with custom code, your domain and SSL expiry. Nightlamp watches those continuously and sends a plain-English diagnosis from a real engineer when one breaks.
Newsletter
One real no-code incident + the fix, monthly
A post-mortem from a real no-code outage — what broke, how it was found, and the fix — once a month. Confirming also gets you the no-code incident runbook pack.
Double opt-in. One-click unsubscribe. No spam, ever.