Every certificate outage has the same postmortem: the certificate was valid, then, on a date everyone could have known in advance, it was not. This white paper dissects the most predictable outage in infrastructure, from the expired certificates that took down O2, Microsoft Teams, Starlink, and GitHub, to the CA/Browser Forum schedule cutting maximum TLS certificate lifetimes from 398 days to 47 by 2029, and the process failures that let renewals silently slip.
What's Inside
- The Outage Nobody Scheduled: a dated ledger of seven public expiry incidents, 2018 through 2025, all cited
- The Renewal Window Is About to Shrink: the 398-to-47-day lifetime schedule and what it multiplies
- Why Renewals Silently Fail: incident-frequency data and the three structural failure modes
- What Actually Prevents It: what continuous monitoring adds on top of renewal automation
- Sources: every statistic and incident traced to a primary source
Download the paper for the full incident ledger and renewal-window timeline, or see how Certificate Monitoring keeps expiry off your incident list.