← Back to the carnage
WEBFLOW

⚪ Webflow locked customers out of their accounts for about an hour overnight. The good news: they fixed it. The bad news: your auth system chose violence at 11:30 PM UTC. At least the incident report will be shorter than your rebuild time.

⏰ Jul 15, 2026 FYI spotted via status_rss

// The official story

[RESOLVED] Reports of issues logging in to Webflow

// Status page says

Jul 15 , 02:46 UTC Resolved - This incident is now resolved. Some customers experienced issues logging in to Webflow between 23:30 UTC on July 14 and 00:30 UTC on July 15. We’re no longer seeing customer impact related to this issue. Thank you for your patience while we worked to resolve this. Jul 15 , 00:39 UTC Monitoring - We’ve implemented a mitigation and are no

🔗 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.