Introducing Workers KV Instant — powered by Quicksilver
- ID
- 30726
- Status
- summarized
- Published
- 01 Oct 2026, 9:00 PM
- Fetched
- 01 Oct 2026, 9:14 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/workers-kv-instant/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 6.5
- Created
- 01 Oct 2026, 9:15 PM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
Cloudflare launched Workers KV Instant, a new mode of Workers KV that keeps the same get()/put()/list()/delete() API but runs on Quicksilver v2, the internal key-value store Cloudflare previously used only for its own products. Cloudflare reports p99 reads of 1.62 ms (vs 287 ms for classic KV across all reads, 160 ms cached), p99 write replication of ~256 ms (vs 4.38 s in classic mode), and sub-millisecond p95 reads, with writes pushed to 300+ edge locations. Cloudflare positions it for infrequently updated data like feature flags and application configuration, and states it is "not for every type of data"; the article excerpt does not include pricing, limits, or migration caveats.
Why it matters
If you keep feature flags or app config in classic Workers KV, this is an API-compatible switch that removes the TTL wait and cuts p99 read latency from 287 ms to 1.62 ms — worth testing if config reads sit in your hot path. The catch is that Cloudflare itself scopes it to infrequently updated data, and this post gives no pricing or write-volume limits, so check those before moving anything write-heavy rather than assuming a free drop-in.
Discussion angle
Would you move your feature flags onto KV Instant given it's explicitly designed for infrequent writes — and what does that constraint mean for anything with chatty write patterns?