β Back to the carnage
WEBFLOW
βͺ π§ Form submission emails took an unscheduled sabbatical courtesy of an upstream provider hiccup. The good news: your actual form data survived intact. The bad news: customers got the silent treatment while notifications queued up like rejected concert tickets. All cleared now.
// The official story
[RESOLVED] Reports of form notification emails not being delivered for some customers
// Status page says
Feb 20 , 18:03 UTC Resolved - Form notification emails were not delivered as expected between 14:15 and 16:41 UTC due to an issue with an upstream provider. All queued emails from this period have since been successfully processed and delivered. Form submissions themselves were not impacted and remained accessible via the Forms tab in site settings throughout the incident. Weβre no longer seeing any impact, and th
π Official status page (for the PR-approved version)
https://status.webflow.com/incidents/1x9kmymwnyzyWebflow's Greatest Hits
βͺ WEBFLOW
Sep 28, 2026
βͺ Webflow's publishing speeds went full sloth mode for a hot minute, then engineers threw spaghetti at the wall and declared victory. Sites are live again, customer patience rewarded with a participation trophy.
βͺ WEBFLOW
Sep 28, 2026
π‘ Webflow customers discovered their sites publish at geological timescales. Engineers deployed a fix and claim victory, though 'monitoring closely' is tech speak for 'fingers crossed.' Apparently deployment speed and reliability are mutually exclusive concepts.
βͺ WEBFLOW
Sep 22, 2026
βͺ Forms kept working, webhooks kept humming, but notification emails decided to ghost users for nearly two days. The emails have been revived and are awkwardly apologizing to your inbox.
βͺ WEBFLOW
Sep 22, 2026
βͺ π§ Webflow briefly decided notification emails were optional. Forms still worked, webhooks still fired, but your customers' inbox notifications took an unscheduled vacation. Now resolved, and yes, they're monitoring it like a hawk.