Why SSL certificate expiry causes outages
An expired certificate can make a healthy website look broken. Browsers block access, API clients refuse connections, payment flows fail, and search crawlers may stop trusting the page. The server can be up while the user still sees a hard failure.
Certificate automation helps, but it is not a substitute for monitoring. DNS changes, ACME failures, load balancer misconfiguration, and forgotten subdomains can all leave one hostname serving a stale certificate.
What to check on a certificate
The expiry date is the obvious field, but issuer and subject matter too. The issuer tells you which certificate authority signed the certificate. The subject and alternate names tell you which hostnames the certificate is meant to cover.
The fingerprint and serial number are useful for audits and incident response. They let you confirm whether a certificate changed after a renewal, migration, or emergency replacement.
How early should you alert?
Thirty days is a sensible first warning. Fourteen days should be loud. Seven days is no longer a reminder; it is an incident waiting for a calendar page to turn.
PingPane can monitor a certificate alongside the website or API it protects, so the expiry warning lives next to the uptime history instead of disappearing into a calendar reminder.