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.
JIf the response gives you a normal KV value, you don't see it down there, it's just an extra log I printed out to check
JYeah - give it a bit for the fix to rollout everywhere - Cloudflare's network is very large so it can take a little bit for fixes to land everywhere.
JWe're seeing it intermittently resolved depending on which location etc. you hit, so just give it a little while to fully propagate 
JThe KV propagation is up to 60 seconds.
How come there's no change after 17 minutes?
How come there's no change after 17 minutes?
JThe fix is rolling out. Please be patient.
JWill cloudflare compensate you financially for this?
JIf you're an ENT customer, I'd recommend you reach out to your account team for any SLA information and compensation.
JAs a pay-go user, you're welcome to submit a ticket, but as far as I know there's no official SLA for things like this, sorry.
JI used to use a pro rating.
Nevertheless, when I ask for a ticket, I get an answer after a few days by email
Ask me again lol
When I inquired again, I only got the same macro answer.
So I didn't want to spend 20 dollars on that crap.
The service is a mess.
Where the hell am I supposed to ask?
They don't even see discord
They don't even look at the community
Tickets are even Macro-answers
Nevertheless, when I ask for a ticket, I get an answer after a few days by email
Ask me again lol
When I inquired again, I only got the same macro answer.
So I didn't want to spend 20 dollars on that crap.
The service is a mess.
Where the hell am I supposed to ask?
They don't even see discord
They don't even look at the community
Tickets are even Macro-answers
IThey don't even see discordThe issue has been acknowledged. It's not a matter of "not seeing it", it's actively being worked on by the relevant teams. If you don't want to spend money on Pro, that's fine - but debating this won't get the issue resolved faster
Jwhen I asked about 'enterprise grade', I couldn't get a reply even after a year
I don't even know why contract tickets exist
I don't even know why contract tickets exist
JIf you configure redundancy like that, don't you think it should all be redundant, including domain services, pages, and serverless functions?
GHi all, I as wondering has anyone did any benchmarks for js vs wasm in case its a very simple gateway (like storing request in KV)
I dont expect for latency to change much but I am wondering if there is any difference in cpu time used
I dont expect for latency to change much but I am wondering if there is any difference in cpu time used
KThe WASM will always be slower, but it's unlikely to be noticeable unless your Worker bundle goes above 1 MiB - since that's when cold starts are bad.
GI mean I wonder if there is any difference in cpu usage once function is running
Glike startup aside
MJS is likely to be faster for HTTP request processing. The benefit of Wasm is usually in heavy, off-request compute or where you want to use non-JS libraries/code
Gyeah, thats what im thinking as well, I just dont have numbers to prove it. I might end up doing some benchmarks myself
KThe WASM performance hits are usually when you’re doing any large copying of data between the WASM <-> JS boundary. Since the stringref proposal isn’t stabilised yet, strings are always copied rather than a reference being passed.
KUnless it’s a large workload, I doubt there’ll be differences other than a few milliseconds (if that)
Gyep, thats what I am thinking. I think the only place where one may see any difference is cost. I am not sure if I should expect it to be higher or lower for such case
Anyways, I will write up a benchmark someday to play around with it. Im just curious
Anyways, I will write up a benchmark someday to play around with it. Im just curious
TI just switched a short algorithm from JS to WASM. My worker was taking about 3.5ms before and after.
TI was worried that invoking the WASM runtime would have a big performance impact but I didn't see it.
Lhey folks! has someone implemented simple locks with kv? for implementing a synchronized monotonic counter
KKV is eventually consistent so I'm not too sure it fits your use-case
KWrites take some time to propagate, reads are cached, etc
Lhmm. good point.
D#durable-objects are much more suited for that - with KV the best you could do (not recommended) is to write a key on each request, and then list them 1000 at a time to count (again, not recommended, not scalable, just a way to abuse KV into what you want)
Lcool! will look into this
Lthanks @Dani Foldi @kian ! 
Lhmm are there any replication guarantees? like writes are replicated in the same order?
Llike if i find the key i’m looking for, every key i’ve written before will appear in a kv prefix scan
HThere is not
