WEBFLOW

⚪ 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.

⏰ Sep 17, 2026 FYI spotted via status_rss

// The official story

[RESOLVED] Reports of issues authorizing MCP for sites within Client Workspaces

// Status page says

Sep 17 , 10:12 UTC Resolved - This incident has been resolved. Thank you for your patience while we worked on this issue. Sep 17 , 10:00 UTC Monitoring - A fix has been implemented and customers should now be able to authorize MCP for sites within client Workspaces as expected. Sep 17 , 09:44 UTC Identified</

🔗 Official status page (for the PR-approved version)

https://status.webflow.com/incidents/vrhggv5r9dy9

Webflow'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.