← Back to the carnage
WEBFLOW
⚪ Webflow's upstream provider decided to test everyone's patience between midnight and 4am UTC. Sites loaded like dial-up era nostalgia, SSL certificates took their sweet time provisioning. Drama's over, upstream provider finally did their job. (Auto-resolved: no updates in 24h)
// The official story
[RESOLVED] Reports of latency loading some hosted sites and issues provisioning SSL certificates
// Status page says
Jul 2 , 10:59 UTC Resolved - Between approximately 00:00 UTC and 04:05 UTC, some hosted sites experienced slower loading times and SSL certificates took longer than expected to provision. We're no longer seeing customer impact related to this issue. Following confirmation from an upstream provider and verification by our team, this incident is now resolved. Thank you for your patience while our upstream provider worked to resolve th
🔗 Official status page (for the PR-approved version)
https://status.webflow.com/incidents/c9n7tdd322v5Webflow'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.