I would really be interested to understand what caused this issue. @Daniel Ray if someone could provide a writeup after its all done that would be amazing!
I was working for more than 2 months on a project with D1, I am disappointed, I feel like I wasted time. When will D1 be used stably? I come from AWS Dynamo, previously FIrebase.
D1 can be used stably. Every service has downtime that happens occasionally such as this incident. AWS Dynamo and Firebase have also both had incidents before.
I don't know about AWS Dynamo. But I have never experienced downtime using Firestore for 3 years, probably because they have some kind of redundancy / replica in case accident happens.
incidents happen all the time and they will still happen until chatgpt will control everything. LoL. But for real, the value Cloudlfare provides allow for some incidents once in a while
everything eventually has issues, too many moving pieces. What matters more is how they respond & fix it. D1 is def more prone to issues too with it being sql and a single durable object in a single location, rather then something like Firestore which is nosql over many machines and always being replicated. Somewhat just trade offs to nosql vs sql though
seems that some of the d1 dbs have recovered, at least based off the overview of my acct, like 2/4 or something. I had ~3-4 which never were impacted curiously.