← Back to the carnage
WEBFLOW
🟡 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.
// The official story
[MONITORING] Increased publishing times for some customers
// Status page says
Sep 28 , 14:16 UTC Monitoring - We’ve deployed changes to address the increased publishing times affecting some customers and are no longer seeing active impact. Our team is continuing to monitor the situation closely. Sep 28 , 12:32 UTC Update - Our team is continuing to investigate increased publishing times affecting some customers. We’re working to understand the
🔗 Official status page (for the PR-approved version)
https://status.webflow.com/incidents/br9bm7k124mtWebflow'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 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.
⚪ WEBFLOW
Sep 17, 2026
⚪ Webflow briefly forgot how to let people authorize stuff in Client Workspaces. They dug it up, dusted it off, and declared victory 12 minutes later. The speed suggests they knew exactly where the body was buried.