β 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.
// 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/s406qp04wgktWebflow'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.