Webflow: [RESOLVED] Reports Of Issues Accessing Hosted Sites, Webflow.com, SSL Certificate Provisioning, and Form Submissions
Cloudflare outage, Dec 5, 2025 · 46 vendors, 46 incidents
Webflow’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +15 min vs the first vendor naming Cloudflare)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>18 vendors, 18 blamed Cloudflare<br/>Unbounce, Expo, GitLab +15"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Klaviyo"]:::blames
root --> h4
later["Later<br/>2 vendors, 2 blamed Cloudflare<br/>Bitrise, Sigma Computing"]:::blames
root --> later
me["Webflow (this incident)<br/>posted +15 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Hosted Websites - Static pagesSite PagesHosted Websites - CMS pagesWebflow.comWebflow.com & Marketplace - Webflow.com
Timeline of updates
- investigating
We are currently investigating reports of issues accessing hosted sites and webflow.com due to an issue with an upstream provider. We are continuing to investigate and will share additional details as soon as they become available.
- monitoring
Our upstream provider has implemented a fix. As a result, we are seeing a return to expected performance levels across our impacted services and are continuing to monitor the situation closely.
- resolved
Following continued monitoring and confirmation from our upstream provider, we’ve verified that performance across all impacted services has returned to normal. This incident is now resolved. Services were affected between 08:48 and 09:11 UTC. We appreciate your patience and understanding while we worked with our upstream provider to resolve this issue.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 18:22 UTC
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
c8d7f34e624b0610…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).