← Back to the carnage
WEBFLOW

🟠 Webflow decided to play 'are you who you think you are?' with login credentials. They've apparently stopped the bleeding, but are staying glued to their monitors like anxious parents waiting for test results. Mitigation deployed, fingers crossed.

⏰ Jul 15, 2026 FYI spotted via status_rss

// The official story

[MONITORING] Reports of issues logging in to Webflow

// Status page says

Jul 15 , 00:39 UTC Monitoring - We’ve implemented a mitigation and are no longer seeing customer impact related to this issue. We’re continuing to monitor the situation closely and will provide another update as soon as we have more information. Thank you for your patience. Jul 15 , 00:23 UTC Update - We are continuing to investigate this issue. Jul <

πŸ”— Official status page (for the PR-approved version)

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

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.