← Back to the carnage
WEBFLOW

⚪ Webflow's hosting infrastructure briefly forgot how to return anything but error codes, then remembered. Sites are breathing normally again after the servers decided to have an identity crisis for 95 minutes. (Auto-resolved: no updates in 24h)

⏰ Jan 23, 2026 Fixed (for now) spotted via status_rss

// The official story

[RESOLVED] Reports of intermittent 500 errors on some hosted sites

// Status page says

Jan 23 , 16:54 UTC Resolved - This incident has been resolved and services are operating normally. We’re no longer seeing customer impact related to this issue. Thank you for your patience while we worked to address this. Jan 23 , 15:19 UTC Monitoring - We’re seeing signs of recovery and customer impact has been mitigated. Services are operating as expected at this time, a

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

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

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.