WEBFLOW

⚪ A handful of sites woke up naked—CSS vanished between 23:00-23:30 UTC. Webflow's Per Page CSS feature decided to ghost some users, but disabling it brings the styling back. Fashion emergency averted for most. (Auto-resolved: no updates in 24h)

⏰ Apr 08, 2026 Fixed (for now) spotted via status_rss

// The official story

[RESOLVED] Reports of CSS not loading for a very small number of hosted sites

// Status page says

Apr 8 , 03:10 UTC Investigating - We’re investigating reports that CSS is not loading as expected for a very small number of sites. This may cause some pages to appear without styling for affected customers. Users with Per Page CSS enabled who published their site between 23:00–23:30 UTC may be affected. Some users have reported that disabling Per Page CSS and republishing their site temporarily restores expected behavior.<

🔗 Official status page (for the PR-approved version)

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

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.