Well glad this got posted here. We just got rejected from Y comb, our tech is sci fi indeed. Alex Garlands made some sci fi that we've built (are building)
They regularly are unable to create new droplets [or other control issues where you can't perform normal functions with normal latency] and/or have full DC outages.
Pretty much any use case where I'd use something like DO being unable to create new VMs, etc. is the same as an outage.
I asked why as I work for DO's operations team and I wanted to know what your concerns were. Do you have a specific instance of a problem? What you're describing would be considered a MAJOR outage for us and we have not had one in quite some time.
That is annoying enough I'd want to be able to failover if it exceeded 15 minutes. I get it might not be an issue for anyone else but failing over is less complex than mitigating latency issues with droplet creation or whatever.
I get "regularly" to me might mean something different to you but if the 2 DO DCs I was using are hit literally every month with a problem of some kind...it seems regular to me.
Are we making an assumption that the candidate doesn't just say what I want to hear? Reminds me of economics class - "Ok class, before we begin you must first go forward with the assumption all people make rational decisions."
"Not everyone in @ycombinator's latest batch could fundraise.
I was fortunate enough to invest in @coinbase @Amplitude_HQ & @benchling when none of them could raise their full seed rounds after YC.
@BoostVC is looking to write 2 $500k checks into YC companies from the last batch." - @AdamDraper