Webflow: Degraded performance and downtime on CMS sites
Timeline of updates
- resolved
We encountered a large amount of requests that bypassed our caching layer which caused downtime and degraded performance on our render cluster. This lasted for about 60 minutes on 2/11 starting around 7pm CET, but only affected sites that were published during this window. We have added protections and added more capacity to our render cluster. We have also amended our alerting and monitoring so that our engineers can be notified earlier of sudden load.
From Webflow’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.webflow.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Webflow, started 2017-02-23 21:49 UTC, resolved after 0 min, 1 update(s).
- Title
- Degraded performance and downtime on CMS sites
- Vendor
- Webflow
- Date
- URL
- https://rewindex.com/company/webflow/incidents/9206s6ynrntn
Webflow profileRecent Webflow incidentsAll outages on February 23, 2017Webflow in February 2017MarkdownJSON