Security

TLS Certificate Rotation Without Uptime Surprises

Build repeatable cert renewals with overlap, monitoring, and rollback.

By Priya DesaiSRE Lead|Published December 23, 2025|5 min read
Lock and circuitry symbolizing secure uptime

Renew with overlap

Issue new certificates at least 14 days before expiry and deploy behind a canary load balancer.

Keep the old certificate live until synthetic and browser checks validate the new chain.

Overlap windows prevent single flip mistakes from becoming customer-visible downtime.

Monitor the whole chain

Use Watch.Dog to check OCSP, intermediate certs, and SNI responses from multiple regions.

Alert when remaining validity dips below your policy threshold so renewals are never a surprise.

Document rollback paths

Store previous certs securely and keep load balancer switch scripts in runbooks.

Practice rollback in staging with the same DNS and edge settings you use in production.

Article stats

  • Author: Priya Desai
  • Role: SRE Lead
  • Published: December 23, 2025
  • Reading time: 5 min

Tags

#tls#certificates#uptime#watchdog

Put this into practice

Deploy monitors, share beautiful status pages, and automate incident narratives with Watch Dog.

Start for free

Launch reliable uptime monitoring with Watch.Dog

Create a free workspace, import your monitors, and ship status updates and alerts from one place.

Don't wait more

Watch Dog enables you can quickly identify and address any issues or incidents that may arise