← Back to the carnage
WEBFLOW
⚪ Update: [RESOLVED] Reports of 503 errors on some hosted sites, Webflow.com, and MCP Server
// The official story
[RESOLVED] Reports of 503 errors on some hosted sites, Webflow.com, and MCP Server
// Status page says
Aug 25 , 23:58 UTC Resolved - This incident has been resolved. Aug 25 , 23:57 UTC Update - Some hosted sites, Webflow.com, and MCP Server experienced 503 errors. We’re no longer seeing customer impact related to this issue, and the incident is now resolved. We appreciate your patience while we worked to resolve this issue. Aug 25
🔗 Official status page (for the PR-approved version)
https://status.webflow.com/incidents/4tnmh35gm0mjWebflow'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.