[Ipg-smz] End of the geek debacle story
Tom Henderson
thenderson at extremelabs.com
Thu Apr 4 13:24:46 UTC 2019
Geek Guilders,
As promised, the end of story WRT my hosting debacle.
Name.com had a botched upgrade on the server that hosts some of my
sites. To wit:
"Thank you for contacting Name.com <http://name.com>. We have checked
with our system admin on this matter and he has told us on this issue.
He informed us that NGINX was enabled for a time to assist with a server
resource issue we were facing due to upgrades that were happening to the
server. Once the resource issue was resolved, NGINX was removed and your
site should not continue to be proxied. We apologize for any
inconvenience this may have caused.
Please let us know if you have any additional questions and we will be
happy to help!"
This means five facts:
1. They lied to me about my site being proxy'd
2. It took them at least two days to fix whatever it was that was broken
after the proxy was installed
3. It took five days of constant hounding to get even the vague answer above
4. They're not using best practices to expose a root cause analysis
5. Could've been much worse, and the site was lucky to be alive due to
shenanigans.
They did not have an adequate roll-back plan. They didn't have a chain
of authorities to notify clients of the truth. They were unprepared to
move clients among hosts, instead, bringing up a separate instance of
the httpd as an intercept instead of being able to fix the first one, or
move them as VMs, or other atomic instance kit to working infrastructure.
Name dot com, they name is: Mud.
Tom
--
Tom Henderson
ExtremeLabs, Inc.
+1 317 250 4646
Twitter: @extremelabs
Skype: extremelabsinc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://netpress.org/pipermail/ipg-smz_netpress.org/attachments/20190404/aaf17b12/attachment.html>
More information about the Ipg-smz
mailing list