Certainly self-reported incident: BR §2.2 test website certificates expired after renewal stopped
Certainly reported a self-disclosed incident affecting its BR §2.2 test websites. Between 2026-08-01 03:47 UTC and 2026-08-05 14:45 UTC, 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, and certificate renewal stopped because renewal runs during VM startup. The company said newly implemented monitoring detected the failures, but the alert remained at reduced priority under its review policy for new alerts. Certainly also noted that this was the third incident affecting these test websites in a little over 14 months, and it referenced prior bugs #1968836 and #2052399 as context. The bug remains ASSIGNED, with no resolution recorded in the thread excerpt.
- Non-compliance began when four BR §2.2 test websites started presenting expired Subscriber Certificates.
- Certainly identified and ended the non-compliance after monitoring detected the failures and incident response restored the affected state.
- Fastly representative — Certainly filed a full incident report describing expired test-website certificates, the root cause, impact, timeline, and prior related incidents.