Vault secret updates not propagating to monitoring nodes

Update timeline

1. investigating Sep 22, 2026, 06:00 PM UTC

   #### Summary Since **September 22 at 18:00 UTC**, changes to secrets in Vault have not been reaching the monitoring nodes. This started after checks moved to the new check manager. Checks that use Vault secrets keep running with the last value each node had before the move. If a secret has been rotated or changed since then, checks using it may fail or report wrong results. The issue is still ongoing. #### Impact - **Affected:** checks that use Vault secrets (credentials, tokens, headers, variables) and whose secret was updated after the migration - **Not affected:** checks that don't use Vault secrets, and checks whose secrets haven't changed since the migration - **What users see:** [false DOWN alerts or authentication failures on checks using rotated credentials / no visible effect for most accounts] - **Duration:** ongoing, about 9 days so far (since September 22 at 18:00 UTC)

2. resolved Oct 01, 2026, 03:22 PM UTC

   The secret cache propagation has been fixed, the vault is back and a fully operational