Last night I was testing DO managed Kubernetes cluster with persistent volume claim and the volume took 15 minutes to reattach after the pod is rescheduled to another host. I thought it was just some weird hiccup and went to bed.
The incident report indicated the problem started 4 hours ago (around 9pm GMT) but I was having problem around 4pm. It's definitely not a 2-hour incident.
our disks in London went down at about 8:45pm UTC (10 mins 100% disk utilization alert triggered at 5 to) and DO recovery message was sent out at about 2am UTC. We switched our service (keychest.net) on at 3:15am
Thank you for your comment! It would work if you have a US company or are selling to US customers, but, unfortunately, we don’t have documents for India yet. We may expand into this market later, but for now we are focusing on US. You can also benefit from the Terms of Use and Privacy Policy we will launch soon, since they are pretty international.
You can't change what has already happened. And trying to change that will only cause more trouble.
Inform somebody higher up about this. Do it more subtly instead of name calling. Usually people sitting higher up will take this into consideration on future decisions.