cmek-key-lifecycle changedmanage-claude/cmek-key-lifecycle
Nearest release: v2.1.315, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+2added
Lines−2removed
From line
28
where the diff opens
First seen
23 Oct 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 28, old and new numbered
/
from line 28
2828
2929## If Anthropic can’t reach your key
3030
31Requests that store data under your key fail while Anthropic can’t reach it, for example during an outage of your KMS. On Claude Enterprise, these requests include messages in chat and in voice mode.
31An outage of your KMS, for example, can stop Anthropic from reaching your key. When that happens, requests that store data under your key might still succeed for up to 1 hour. After that, they fail until Anthropic can reach your key again. On Claude Enterprise, these requests include messages in chat and in voice mode.
3232
33On the Messages API, these requests return a 503 error with the code `cmek_key_unreachable`, and you can retry them. The Message Batches API retries them for you until your key is available or the batch expires.
33On the Messages API, requests that fail this way return a 503 error with the code `cmek_key_unreachable`, and you can retry them. The Message Batches API retries them for you until your key is available or the batch expires.
3434
3535## Change keys or stop using CMEK
3636
No line in this hunk matches that.