see thats why you back up R2 with D1. then D1 with eh.. let me think..
see thats why you back up R2 with D1. then D1 with eh.. let me think..
SHm I just saw a new error status, but on second look maybe its not related.
ANope. Thats old news now
Tif that is the status-page error, then i feel like it could be clearer.
KBut the status is about CFaccess, not about KV...
AD1 to static pages, secured by zero trust. :NotLikeThis:
CAccess is down because of its dependency on KV
but yea, give them a second, they know a bunch of stuff is broken and are working on it
but yea, give them a second, they know a bunch of stuff is broken and are working on it
R" Update - We are seeing a number of services suffer intermittent failures. We are continuing to investigate this and we will update this list as we assess the impact on a per-service level. "
Tnow the status page message is improved
RGuillermo Rauch is ecstatic rn
Jhttps://www.shopifystatus.com/incidents lol someone at Shopify was mad GCP was not updating their status page (rightly so!)
AI remember the last time we had r2 downtime. Initially entire group was securing their jobs/ clients /relations. Then reality hits, people started sharing cat memes.
When you are cooked beyond measure, add some cheese and salt and make it worth for somebody.
When you are cooked beyond measure, add some cheese and salt and make it worth for somebody.
![ici.radio-canada.cbc.ca[ping ok]](https://cdn.discordapp.com/avatars/657807026805538837/d9698617f80e04d4775b895bebb73992.webp?size=40)
IGot it… I had a billing issue earlier I thought it was because of billing my page was down
Dthis just solidifies my decision to just go back to storage with postgres and redis. if you rely on Cloudflare for everything, as they are pushing for D1, R2, KV - something like this happens you are done.
ABoss, supabase uses cloudflare services.
Its down as well
Its down as well
Di don't use supabase
Dbest to use managed database services directly. I use digital ocean
ANice. But DO also has some bad reputation. Not meeting SLAs and all
Jsome say AWS is having issues too. We'd know if... any of the big providers would bother updating their status page too
DDO has been fine. It's unlikely DO and Cloudflare go down at the same time. Anyway, I've been moving many services from DO to Cloudflare and now I'll have to just keep both b/c having one point of failure in Cloudflare was just stupid decision
SWe moved all our app code off workers because of D1/DurObj/KV reliability concerns, but are still using KV for versioning/routing. This may be the push to finally switch to versioned workers (wrote it before those were a thing).
Is KV us-central-1?
Is KV us-central-1?
DThey say services recovering, but I dn't see it all. this is a total disaster with KV and completely removes my faith in it as reliable storage. KV is probably best used as a backup for another service.
SZeroTrust/Access definitely recovered (I can reach internal services again), but yeah definitely not KV
Pi was under the impression CF ran its own pops/colos, the fact KV is 100% reliant on GCP is concerning
JKV started responding successfully to me
Tay seems to be working now
1I think the issue is that a lot of backend config stuff is stored in KV in US Central, which also happened to be the location hardest hit by the looks of it
Pdidn't last big outage show holes in their config architecture? thought that was all being mitigated 
SError listing KV entries: KV GET failed: 503 Service temporarily unavailable Hopefully it hits me soon 
Sayyy there it is
Cimportant backend stuff/anything config should be QS (Quicksilver, Cf's own replicated edge kv db)
Cthat's why websites/cdn/proxy continued to work fine
CKV is (clearly now) GCP dependent, and CF Access, dashboard, etc, depend onKV
Dall my kv are still down, i guess they only recover KV by geographic location or something?
Chere's def still some errors, thundering herd problem and all that, recovery is slow
CAll 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.
Rall my sites use KV, and they're all back but 1. For some reason that 1 is still throwing the KV 503.
Rthrows it on both the site and the in the worker ide.
Dfor me it's starting to come back. One thing to say about Cloudflare is that they "eat their own cooking", so if something like KV goes down, even they are screwed, and they've got a lot to lose. So in that sense, issues with something like KV are attended to almost immediately. That being said, this was a pretty bad outage and for me at least, I am reluctant to rely on it as much as I have
RThe same is true for pretty much everyone. When kenisis went down in AWS a couple years ago, it took out most of AWS's provisioning and updating tools
DJust started getting KV failures again. This thing is not stable.
1Seems to be working fine for me 
AIt was a major outage. CF GCP and AWS were affected.
https://www.livemint.com/news/us-news/netizens-claim-major-internet-outage-caused-by-cyberattack-all-details-on-cloudflare-gcp-downtime-here-11749765997009.html#
https://www.livemint.com/news/us-news/netizens-claim-major-internet-outage-caused-by-cyberattack-all-details-on-cloudflare-gcp-downtime-here-11749765997009.html#
