kya_unavailable: The verification provider is unavailable
The verification provider could not be reached, refused the deployment's credential, or answered with an attestation that does not verify (another signer, another subject, a level whose checks do not match, or a stale attestation). Nothing was stored; an attestation stored earlier is unchanged and still counts until it expires.
What to do
- Retry the check later.
- Operators: confirm
CORE_KYA_MOCK_URL, the test key and the pinned signerCORE_KYA_MOCK_SIGNER.
On the wire
HTTP 409, error type state_error. Answered by POST /owner/v1/kya/checks. Every client gets errorDetail, with or without Dynamo-Error-Detail: 1. On the multi-tenant hosted tier the KYA routes need Dynamo-Version 1.8.0 or later: the front door answers a request served at an earlier version with HTTP 404 version_unavailable before the core sees it, and serves a request that names no version at the account's default (1.8.0 for new accounts). A single-tenant core answers whatever version the request names.
{
"error": "state",
"reason": "kya_unavailable",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "kya_unavailable",
"message": "…",
"param": "serviceNode",
"doc_url": "…/errors/kya_unavailable.md",
"fix": "the verification provider could not be reached or its answer did not verify; retry later (the stored attestation, if any, is unchanged)"
}
}
See KYA and all error codes.