← Back to the carnage
WEBFLOW
🟡 Webflow's Canvas decided to play gatekeeper with Client Seat users, then implemented a fix and started monitoring like nothing went wrong. Recovery in progress, but trust issues remain.
// The official story
[MONITORING] Reports of issues accessing Webflow Canvas via Client Seats
// Status page says
Apr 1 , 14:14 UTC Update - We are continuing to monitor for any further issues. Apr 1 , 14:13 UTC Monitoring - A fix has been implemented for the issue impacting some users with a Client seat role who were unable to access Webflow Canvas. We are seeing recovery and are continuing to monitor the situation closely to ensure stability. Apr 1 , 1
🔗 Official status page (for the PR-approved version)
https://status.webflow.com/incidents/26knm6lx1bf1Webflow'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.