The Digital Ocean outage on 28-Nov-2024 was caused by a mistaken clientHold put on DigitalOceanSpaces.com by Network Solutions, probably by one person, which continued for hours because a bevy of clueless VeriSign executives, notified in multiple escalations, didn’t know who to contact to reverse this simple mistake that lead to a major corporation bleeding revenue and reputation.
Imagine if Network Solutions accidentally put a clientHold on your domain. You’d have to kiss your domain goodbye because a lot of VeriSign executives will not be helping you, even if they could.
“DigitalOcean is working with Network Solutions to understand what happened on their end that resulted in the clientHold being applied to our domain incorrectly. In addition, we are reviewing other domain registrars as possible new homes for our domains.”
Network solutions as always will learn nothing and do nothing differently.
netsol used to be the gold standard. started going downhill when verisign bought them… got worse when vultures got their hands on it… and started scraping the bottom under web.com ownership.
I’ve had to use Netsol on and off since the 90s; they’ve always been a dumpster fire.
I’ve never worked with a worst registrar. It’s always a high priority to move our domains and assets away from them after acquisitions. There’s really no excuse for how bad they are.
Dammit who forgot to stick the bubble gum back in the contraption this time? Don’t you know that’s what helps stick the duct tape?
So the network solutions execs are useless? Fire all of the ones involved in this debacle.
*22:38 - Incident declared based on monitoring and customer reports of our Cloud Control Panel not loading. *22:44 - Issue detected by an internal alert
Their internal detection system was 6mins slower than customer reporting… 6 mins is an eternity for this kind of thing
