I guess I should say the 40-50ms is e2e of the entire worker request and sending it back to the clie
I guess I should say the 40-50ms is e2e of the entire worker request and sending it back to the client.
Uno clue what just the kv request time inside the worker is 
Toh okay. So i guess it could only take single digit latency
Tbc averate latency from anywhere not my local computer to my computer is 20-30ms
JI'm using kv to manage the session.
But from today, "error code:500" keeps responding.
Strangely, there is no problem in the local development environment.
kv is being used as an http request. Even if you throw it with postman, it gives you a normal response.
But from today, "error code:500" keeps responding.
Strangely, there is no problem in the local development environment.
kv is being used as an http request. Even if you throw it with postman, it gives you a normal response.
RHi, I got an email from CF to inform me that I reached 50% of my free KV tier. DashBoard shows: Which obvious limit did I miss in the free tier. I though I had 100000 operations perfay.
JThis is just my opinion, but I think what was possible in the local environment was possible because the request was made in Korea.
In Korea, if you don't use Business grade, you will receive requests from other countries when you request them on your PC.
In Korea, if you don't use Business grade, you will receive requests from other countries when you request them on your PC.
DIndeed, you get 100k/day read operations, but only 1000 write, 1000 list and 1000 delete operations (https://developers.cloudflare.com/workers/platform/pricing/#workers-kv)
By default, users have access to the Workers Free plan. The Workers free plan includes limited usage of Workers, Pages Functions and Workers KV. Read …
Rthank you @Dani Foldi , I missed the 1000list limit
JI'm spending money on this and I'm debugging it lol
JAre you guys fixing this error? It's not even reflected on https://www.cloudflarestatus.com/ , so should I move on to upstash?
Welcome to Cloudflare's home for real-time and historical data on system performance.
EThe best way to get eyes on issues for them to be fixed is through a support ticket (https://dash.cloudflare.com/?to=/:account/support), the help in this community is best-effort and has no guarentee of help or response.
That said, are you able to explain more about the issue? Are you using the Cloudflare API (
That said, are you able to explain more about the issue? Are you using the Cloudflare API (
api.cloudflare.com
Jresponse image
Customers have been complaining that they have not been able to log in for six hours.
The funny thing is it's not a region issue.
Registering kv from other pages functions is normally registered
When I fetch a request to read kv in pages functions that is suddenly not working now with v4 api, this is the only one that gets 500 errors answered.
Customers have been complaining that they have not been able to log in for six hours.
The funny thing is it's not a region issue.
Registering kv from other pages functions is normally registered
When I fetch a request to read kv in pages functions that is suddenly not working now with v4 api, this is the only one that gets 500 errors answered.
ECan you share your account ID?
JIt's a sensitive matter, so can I DM you?
EYes
EMy DMs are open, it will be your own settings
EI sent a friend request if that helps
Ji sent it
EThanks
JMy English is poor, but I will tell you something to refer to
- There is only one page function in which 500 errors occur.
- Copy the same request as it is, and if you request it in a different environment, you get a normal response.
- It worked normally until yesterday.
- I can't take any action because the KV Server is experiencing an internal error.
GMaybe 'normal response' is cached in your browser?
JKV request responses are handled by functions(worker), does the browser cache matter?
GI was thinking that browser does not do a request at all, just pulls the cached result but it sounds like this is not the case
JEven if you make a different key and read it, it's the same.
The status code is 500 in the first place, but I don't think it makes sense that this is my problem.
Because I haven't modified the code related to this recently and it's a problem that has occurred since today.
The status code is 500 in the first place, but I don't think it makes sense that this is my problem.
Because I haven't modified the code related to this recently and it's a problem that has occurred since today.
JI'm using this for session management now and the same domain services are all paralyzed.
I felt for the first time that there was a huge disappointment and lack of safety for KV.
I'm thinking about whether I should change everything to real
I felt for the first time that there was a huge disappointment and lack of safety for KV.
I'm thinking about whether I should change everything to real
upstash even now.Gim not sure whats the issue but you should definetelly check logs. My guess its an issue with your code
GI just wanted to say thank you for mentioning upstash, it seems great! I might end up using it myself!!
JLog is all the images above what can I do with that?
GI would expect for log to contain errors?
JIf my code is wrong, why does the local or other environment work when it's copied?
Gi have no idea, i guess its cloudflare issue
JIf you look at the page function log, the only response is error code 500
Jt's a waste of money I paid them
JThere’s a known issue right now with various APIs throwing 500s. It’s being investigated and a fix should be out soon. Sorry for any inconvenience.
EThanks for the report @TL&D
JYour response is too slow.
Why didn't you reflect it on cloudflarestatus.com?
It was already over four hours when I discovered it.
I use walkers for a fee, but I can't even inquire about tickets because I use cloudflare as free.
I hope you think about this part and reflect it
Why didn't you reflect it on cloudflarestatus.com?
It was already over four hours when I discovered it.
I use walkers for a fee, but I can't even inquire about tickets because I use cloudflare as free.
I hope you think about this part and reflect it
JI'm not a Cloudflare employee, but a community member simply passing along the information as I receive it. I understand this is frustrating, and only apologise for that. For us to escalate issues, we have to see it impacting multiple users, and until very recently, we did not have many reports of this. Once we did, it was escalated, and we got confirmation within minutes which was then relayed to you.
JI'm sure we'll get an update on the status page soon. Thanks for your patience.
Jhttps://www.cloudflarestatus.com/incidents/03vm5mx76pc6 has now been updated to include a note about this:
Cloudflare API in Pages Functions may also have been affected returning intermittent 500 errors.
A fix has been implemented and we are monitoring the results.
JI think I misunderstood because you gave me the answer like an employee I'm sorry.
But why do you say sorry when you're not an employee? The front and the back are a bit weird?
But why do you say sorry when you're not an employee? The front and the back are a bit weird?
JI still feel bad when people have issues, having experienced things like this myself 
Just trying to empathise with your situation - sorry for any confusion.
Just trying to empathise with your situation - sorry for any confusion.JIt sounds like a fix is rolling out though, so hopefully you won't be seeing issues for much longer! 
EA note was added to https://www.cloudflarestatus.com/incidents/03vm5mx76pc6
Cloudflare API in Pages Functions may also have been affected returning intermittent 500 errors.
A fix has been implemented and we are monitoring the results.
JWhat did you fix? The error is not solved at all.
JThat's a very different error. It sounds like you're getting a key and requesting it to parse as JSON, but haven't stored valid JSON in the value
JTry getting it as
textjson and logging the result.Jenv.NAMESPACE.get(key, { type: "text" }); instead of env.NAMESPACE.get(key, { type: "json" }); for example.JWhat are you saying.
JSON parsing has an error because the value above says "error:code 500".
JSON parsing has an error because the value above says "error:code 500".
JApologies, I missed that. You're likely just waiting for the fix to roll out then. It's still in the process of rolling out.
