Termly experienced a major incident on June 4, 2026 affecting Consent Management Platform and Hosted Policies, lasting 1h 1m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Jun 04, 2026, 04:15 PM UTC
Systems affected: - The Termly dashboard was unaccessible for all users. - In some cases, some visitors to a Termly-served website may not have been served the banner during this window. In those cases, the next time the customer visits they will be presented with the banner as usual. In aggregate, this was <20% of visitors. - In some cases, some visitors may not have been able to view specific details in the banner. Root cause: A server component of our continuous integration/continuous deployment (CI/CD) system crashed during deployment, causing a failure mid-process during the production deploy. This resulted in unhealthy production application servers causing the site to go down. Additionally, there was a bug in the CI/CD configuration designed to halt deployment when servers come up in a degraded state. When we attempted to roll back to a healthy state, the rollback failed due to the unhealthy deployment environment, ex tending the outage. The failure in the CI/CD server was tracked back to an out-of-memory issue. Fixes: 1) Completed: Increased the memory allocation on the CI/CD server in question 2) Completed: Address the root cause of the memory usage spike (too much concurrent work) 3) Ticket filed: Fix and improve the CI/CD configuration to halt deployment when new servers come up in a degraded state 4) Ticket filed: Add additional checks to CI/CD to ensure a healthy deployment environment before deploying