Cloudflare
Cloudflare health checks stop accepting legacy TLS ciphers on February 1, 2027
74 days left — Feb 01, 2027
- What stops working
- Cloudflare's HTTPS Health Checks and Load Balancer monitors will no longer complete a TLS handshake with origin servers that only support 3DES or RSA-key-exchange cipher suites. After February 1, 2027 those probes fail and the origin is marked unhealthy, so load balancers may pull it out of rotation. Normal proxied visitor traffic is not affected.
- Who is affected
- Cloudflare customers using Health Checks or Load Balancing against origins running old TLS stacks (older Windows Server and IIS, legacy appliances, old Java application servers).
- Official migration path
- Enable TLS 1.3, or at least one ECDHE cipher suite, on every origin that is health-checked.
- What the official path does not cover
- Cloudflare does not audit which origins behind your load balancers still negotiate only legacy ciphers, nor reconfigure vendor appliances or old application servers. The audit, TLS reconfiguration and failover testing is the paid work.
- Source
- Cloudflare Docs: API deprecations, entry dated November 5, 2026 · announced 2026-11-05 · verified 2026-11-18
Need this done before Feb 01, 2027?
Fixed price, fixed scope, fixed date. From $2,500 for a single integration or workflow; you get the working replacement, the code, and a before/after check. Quote within one business day.
One short form (company, email, what runs on this, needed-by). Reply within one business day.
Not ready yet? Get an email when Cloudflare deadlines approach · Firms: get listed for Cloudflare work.
Spotted a wrong date? Report it — corrected with the source within one business day.