Certainly self-reported incident: test website certificate renewal failure after production deployment drift; remediation completed and bug resolved
Certainly reported a self-disclosed incident affecting its BR §2.2 test websites. Between 2026-08-01 and 2026-08-05, four of its six test websites presented Subscriber Certificates whose validity periods had expired. Certainly said the root cause was a one-off manual production deployment change that prevented the VM’s daily reboot, which in turn stopped certificate renewal because renewal runs during VM startup. The company also said replacement monitoring detected the failures, but the alert remained at reduced priority during an incomplete cutover from the legacy monitoring tool. Since the prior summary, Certainly reported that all four remediation action items were completed, including moving renewal to an externally scheduled workflow, promoting the replacement alert to paging priority, updating the incident-resolution procedure, and making reviewed source authoritative for production deployments. The report closure summary states that the remediation is complete and requests closure, and the bug is now RESOLVED/FIXED.
- Four BR §2.2 test websites began presenting expired Subscriber Certificates.
- The non-compliance was identified and ended after incident response restored the affected state.
- Certainly stated that all remediation action items were complete and requested closure of the incident report.
- The bug was marked RESOLVED with resolution FIXED.
- Fastly representative — Certainly filed a full incident report describing the expired test-website certificates, the root cause, impact, timeline, and prior related incidents.
- Fastly representative — Certainly reported that the externally managed scheduler had run successfully for 9 consecutive days and a pre-expiration alert rule had been deployed, while other action items remained incomplete.
- Fastly representative — Certainly reported that action items #1 and #2 were complete, while #3 and #4 were in progress.
- Fastly representative — Certainly reported that action item #3 was complete and action item #4 remained in progress.
- Fastly representative — Certainly posted a closure summary stating that all four action items were complete and requesting closure of the incident report.
- CCADB representative — CCADB issued a final call for comments or questions and said the report would be closed on approximately 2026-09-11.