Unverified50% confidenceReleaseExact time
Vercel Blob added a TTL feature, allowing an expiration period (1 to 730 days) to be specified at write time via the ttlDays parameter, after which the system deletes it automatically.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/17/2026
First Seen
Valid until: 2/15/2027
Sources
Related Entities
Related Claims
UnverifiedSetting a TTL counts as one Advanced Operation per started 60 days, on top of the write operation; a 7-day TTL counts once, and the 730-day cap counts as 13.76% similarUnverifiedIdempotency records typically set a TTL of 24 hours to 7 days to align with the bank reconciliation window; a retry after the key expires will execute the payment again, and the mitigation is dual-layer storage (hot storage in Redis + cold storage in an immutable ledger).68% similarUnverifiedThe retention window inferred from the two snapshots (the seller's own host data is consistent with a cutoff point between 29.55 and 37.77 days, with an 8.2-day gap) is not a schedulable plan and cannot be encoded as a TTL constant.64% similarVerifiedThe cache is not permanently valid; providers usually have a TTL of a few minutes to an hour, and the hit rate fluctuates with user behavior.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1181355API
curl https://kongchang.com/api/v1/knowledge/claims/1181355MCP
get_claim(id=1181355)