Is there an ongoing incident with KV?
Is there an ongoing incident with KV? Getting 500s from workers->KV
3 Replies
No ongoing incident, can you share more details?
@thomasgauvin I was paged at ~12:13AM EDT -- reading a list of KV entries with
const keys = await env.BINDING.list(); was returning a 500 Internal Server Error.
Not sure when exactly it resolved, but I think it was sometime around 1:30AM EDT
(fdb7837214fdd80e018b0bf3ae6355c9 - any worker suffixed with -gateway was impacted, KV namespace is named the same as the worker)Thanks, let me check