halo i want to ask, is it paid workers plan really have unlimited read and put kv?
halo i want to ask, is it paid workers plan really have unlimited read and put kv?
W"message": "KV put() limit exceeded for the day.", I just paid workers plan, but still have error
BYes, there's no limit. But you still have to pay for the requests above the included ones
https://developers.cloudflare.com/kv/platform/pricing/
https://developers.cloudflare.com/kv/platform/pricing/
WI’ve only used 2,000 write operations in KV, in a month. While the monthly limit is 1 million.
BI was just making it clear that there is no limit to how much you can write, besides the per-second per-key limit, but that you don't get unlimited writes included for the base subscription price
Wmy question is why i got this message "message": "KV put() limit exceeded for the day.",, its make my web functionality goes down
BI'm unsure
Wis there any customer support that i can contact?
BIt requires a paid plan, otherwise you could wait for someone that can look into your account to see this Discord chat. No guarantee though
BYou could try redeploying your application and see if that fixes things?
Wmy current plan is paid plan brother.
B
Discover which Cloudflare plan is correct for your requirements. Find out more about Cloudflare plan pricing and sign up for Cloudflare here!
BIf your zone is on a paid plan, then go to the support tab in your dashboard and create a ticket
Wlooks like cloudflare caching my free plan. my problem fix when i downgrade plan. when i downgrade plan, all paid plan feature come up. may be its triggering force cache. 
Thi guys, for some reason I can't delete my KV namespace
Tit's showing this error:
remove namespace: 'namespace has associated scripts: pages-worker--1260571-production'but that deployment has been deleted a long time ago
Vis it possible to update a key from playwright tests?
VI have a worker running locally and want to create a test session for a user
TIf you want to access Workers KV from an external service, you can use the REST API https://developers.cloudflare.com/api/resources/kv/
If you are running Workers locally, you can also use remote bindings in your wrangler configuration https://developers.cloudflare.com/changelog/2025-09-16-remote-bindings-ga/
If you are running Workers locally, you can also use remote bindings in your wrangler configuration https://developers.cloudflare.com/changelog/2025-09-16-remote-bindings-ga/
Interact with Cloudflare's products and services via the Cloudflare API
Cloudflare Docs
You can now connect to R2 buckets, D1 databases, and other resources running on Cloudflare, while running your Worker's code locally, on your own machine.
PJust wanted to confirm there is no Change Data Capture capability with KV, right? I was hoping I could send CRUD events to a Queue so I can trigger other behaviors in response to the KV state changes. I know I can do this in a Worker, but was looking for a storage level solution, like DynamoDB Streams so each Worker interfacing with the KV don't need to handle this concern. Is this on this roadmap and if not can I request it
Cthere seems to be a KV type issue in current wrangler version
Property cursor does not exist on type 'KVNamespaceListResult<unknown, string>'.cursor
Cnevermind, i needed to check for list_complete before, otherwise its not alwaysreturning the cursor property !
TThanks for letting us know, let us know if you run into anything else!
PAre there more KV upper tiers on the business plan? I'm storing a lot of per-user configuration data in KV (both read and write), which means occasionally getting cold reads since its locally cached but can be modified in other places. Response times in APAC and OC (Australia especially) are rough. I had some friends in Japan and Australia hit a benchmarking endpoint (i know timing across I/O isn't the most precise, but it seems to be relatively accurate given the endpoint resolution time)
300-400ms reads and 1500ms writes aren't exactly the end of the world, especially with waitUntil, but it is frustrating for some users. Thought I'd ask before looking into migrating to per-user durable objects
300-400ms reads and 1500ms writes aren't exactly the end of the world, especially with waitUntil, but it is frustrating for some users. Thought I'd ask before looking into migrating to per-user durable objects
1Are those read times done immediately after writing? Keen in mind KV takes 60 seconds to be globally replicated
PYeah the eventual consistency isn’t an issue. The problem is more per user data could be updated overnight, and when they check during the day, it hits a cold read
PRead your own write is extraordinarily performant. It’s just cold reads
1Only way to avoid cold reads is to regularly read I guess 
DOs would be a good use case as long as the instances are spawning close to users (I've had this issue recently where I had DOs spawn on the other side of Australia to me, was seeing 100s of ms extra request time)
DOs would be a good use case as long as the instances are spawning close to users (I've had this issue recently where I had DOs spawn on the other side of Australia to me, was seeing 100s of ms extra request time)
THi everyone, I'm using KV to cache some heavy db calls in my app, I have something like
Even with both
I think I might be misunderstanding something about how KV works, is there some gotchas I must be aware of? Thanks
const cached = await KV.get(key, { type: 'json', cacheTtl: 1800 })
if (cached) return cached
await KV.put(key, JSON.stringify(value), { expirationTtl: 1800 })Even with both
cacheTtl expirationTtl I think I might be misunderstanding something about how KV works, is there some gotchas I must be aware of? Thanks
TKV does store the key value pairs for as long as the expiration ttl, and it should return the values so we'd probably need more of your code to understand why you're going to D1 instead of KV (because it should be in KV)
TGot it, I'm testing to see if the issue isn't somewhere else before I ask for further help
TOne other thing: i tried to delete a KV Namespace from the Dashboard, but get a error message saying
However I don't have any pages project anymore (I used to have one before I moved to open-next with Workers instead). I checked and none of my current Workers use that namespace anymore.
remove namespace: 'namespace has associated scripts: pages-worker--2406846-productionHowever I don't have any pages project anymore (I used to have one before I moved to open-next with Workers instead). I checked and none of my current Workers use that namespace anymore.
CBulk update can only be used with the REST API or the Wrangler CLI for now, which means I need to create an API key. I’m wondering if this can be used with Workers KV bindings in the future, as that would be more convenient.
DCan I assume KV is done again? All my workers with KV are failing with KV errors, and can't log into the Cloudflare Dashboard either, which is exactly what happened last time. I believe the dashboard is powered by some KV in the background.
ALikewise. It resumes for a moment then disappears
TThis was related to the outage on November 18, here is the report: https://blog.cloudflare.com/18-november-2025-outage/
The Cloudflare Blog
Cloudflare suffered a service outage on November 18, 2025. The outage was triggered by a bug in generation logic for a Bot Management feature file causing many Cloudflare services to be affected.
Mwondering if anyone here also have p99 >500ms for reads in same region?
HWhat is the “external resource” in this case? Do you need an HTTP API? Do you want filesystem access?
HYou could expose a Worker that mimics the API you want?
Rdefault sorting by ID is extremely weird btw. I think you guys should change that to Name
1Searching by prefix would be the closest you can get for this
KI found a similar (unanswered) question from 2024, but I'll try anyway: I need to implement a counter on Workers using KV, but it has a 1 write per second key limit (https://developers.cloudflare.com/kv/platform/limits/). Is the limit really enforced? Is there any workaround?
HWhat exactly are you trying to do?
KA "usage counter" within the worker, where a local meter aggregates the local counter and flushes the collected data periodically
HYou could use a DO, which aggregates counts, and then periodically pushes to KV?
KI could, but KV is simpler as I already use it for other things on the same worker
KSo it is enforced and there is no workaround?
HI will note too that KV Read TTL is 60 seconds, so even if you were able to write multiple times a second, any readers would see updates a minute later.
TL;DR no
TL;DR no
