Error listing KV entries: KV GET failed: 503 Service temporarily unavailable Hopefully it hits me soon All Cloudflare services have been restored and are now fully operational. We are moving the incident to Monitoring while we watch platform metrics to confirm sustained stability.
Why are all the explanations being so vague?Transparency is nice and it'd be cool to see a blog post about what exactly is used under the hood, but I mean for an incident report the bottom line is just: Cloudflare's products failed for hours due to an outage. Themselves, upstream or not, it's their responsibility to make systems reliable and not have downtime, and they detailed they're working towards that
Workers KV removed a storage provider as we worked to re-architect KV’s backend
Moving the object store inhouse does not solve the issue of lack of fall-over. What if a problem with R2 causes a similar issue in the future?I don't think they were really clear fully on their plans, maybe they plan on their own + GCP as a backup. R2 is their service/internal to them, even if they planned on going with just R2 if there's any issues it's internal to them/for them to fix. Basically them being in control of more the infra in the same way GCS does for example
cacheTtl for a KV.get() to 300000s (~3.5 days) instead of 300s (5min). That resulted in caching the values and seeing stale data for longer than expected.cacheTtl to be 300 after a couple days when we realized there's an issue with stale data, but we are still seeing stale data regardless. The fix was merged more than 2h ago, and fetched some entries to reset the cacheTtl as the docs say here, but no luck.The effective cacheTtl of an already cached item can be reduced by getting it again with a lower cacheTtl. For example, if you did NAMESPACE.get(key, {cacheTtl: 86400}) but later realized that caching for 24 hours was too long, you could NAMESPACE.get(key, {cacheTtl: 300}) or even NAMESPACE.get(key) and it would check for newer data to respect the provided cacheTtl, which defaults to 60 seconds.

Error listing KV entries: KV GET failed: 503 Service temporarily unavailablecacheTtlcacheTtlKV.get()300000s300s300