β Back to the carnage
WEBFLOW
π‘ Webflow's upstream payment provider decided to ghost transactions, leaving customers stuck at checkout. They've declared 'recovery' underway, which in status-page-speak means 'we found the problem and our vendor is slowly fixing it.'
// The official story
[MONITORING] Reports of issues completing payments on some new plan purchases
// Status page says
Feb 18 , 14:20 UTC Monitoring - We have identified that the issue is arising with an upstream provider, and are now seeing recovery. As a result, all new plan purchases should work as expected. We are continuing to closely monitor the situation. Feb 18 , 13:50 UTC Investigating - Weβre currently investigating reports that some customers are unable to complete payments with
π Official status page (for the PR-approved version)
https://status.webflow.com/incidents/rf6jf7hl9l6wWebflow'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.