Hi Kamal Nasser,
Before 10 hours, I could not login and assumed that firewall blocked my ip, which it does like charm reglarly. Hence, it did not occur to me that kernel could be the culprit.
Today, I found that my droplet in Singapore did not respond to powercycle, i.e. it did not respond to "hardware reset". From console access, I found that kernel was hanging and became non-responsive.
The matter was placed to DigitalOcean support and a ticket opened with with a "click on critical".
The support staff reacted with lightening speed diving into the problem. They found a problem with hypervisor and began to investigate the problem, if it was only my droplet or some others affected.
There it goes. They immediately brought my droplet online.
I wrote that DigitalOcean must accept a "self-penalty" and give a credit of ten times the hours of downtime, which means hundred hours.
The support staf rejected my request and pointed out that if they identified any mistake on side of DigitalOcean then the MONTHLY CHARGE FOR 620 HOURS IN FULL SHALL BE IMMEDIATELY CREDITED! In the answer, they brought to my notice the SLA in effect and showed me a link of this page.
I was not aware of any SLA or this page and had requested to credit 100 hours. But they denied and credited 620 hours!!! I received the credit note of the monthly chanrge in full immediately.
My friends, I am still speechless and do not know what more to say beyond thanks ....