Revocation and recovery

Commercial access, Project Images enablement, binding state and Project status participate in CDN delivery eligibility. Service Account status, scopes, credential validity and IP policies authorize API requests; disabling one Service Account does not revoke the Project’s shared delivery URLs. Paid access can expire independently of measured usage. Ordinary usage excess does not automatically revoke access.

Unavailable access information is not proof that access was revoked or granted. Your application should distinguish temporary delivery failures from a confirmed loss of product access.

Delivery authorization runs before warm-cache lookup. Revocation is not instantaneous: a previously verified allow can remain fresh for up to 60 seconds after its last verification, so publishing a denial does not immediately invalidate every edge instance. If access verification is temporarily unavailable, the current policy permits reuse for up to 15 minutes from that last successful verification, never beyond the access snapshot's explicit expiry. A newer denial, once observed, overrides an older allow. These are edge decision windows, not an end-to-end propagation SLA; publication delays and provider conditions also matter.

Do not assume a URL that worked previously remains authorized. The edge may temporarily refuse while its authority is unavailable; use bounded retries for temporary errors, not repeated binding creation.

After a service recovery, verify delivery with a current ready URL before treating your integration as healthy. A previous successful request does not prove current availability. Keep a fallback image and use bounded retries; contact support with the request ID if the problem persists.