← Back to the carnage
WEBFLOW

🟠 Webflow handed some sites a participation trophy (500 errors) earlier today, then pretended it never happened. Crisis averted via 'mitigation measures'—tech speak for 'we turned it off and back on.'

⏰ Jun 11, 2026 Fixed (for now) spotted via status_rss

// The official story

[MONITORING] Reports of intermittent 500 errors for some hosted sites

// Status page says

Jun 11 , 20:44 UTC Monitoring - Earlier today, a small number of hosted sites experienced intermittent 500 errors. We identified the cause of the issue and implemented mitigation measures. We’re no longer seeing active customer impact related to this issue, and affected sites have returned to normal operation. Our team is continuing to monitor the situation closely and will provide further updates as needed. Thank you for

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

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

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.