<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Geek Guilders,</p>
<p>As promised, the end of story WRT my hosting debacle.</p>
<p>Name.com had a botched upgrade on the server that hosts some of
my sites. To wit:</p>
<p>"Thank you for contacting <a href="http://name.com"
rel="noreferrer">Name.com</a>. 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. <br>
<br>
Please let us know if you have any additional questions and we
will be happy to help!"<br>
</p>
<p>This means five facts:</p>
<p>1. They lied to me about my site being proxy'd</p>
<p>2. It took them at least two days to fix whatever it was that was
broken after the proxy was installed</p>
<p>3. It took five days of constant hounding to get even the vague
answer above</p>
<p>4. They're not using best practices to expose a root cause
analysis</p>
<p>5. Could've been much worse, and the site was lucky to be alive
due to shenanigans.</p>
<p>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. <br>
</p>
<p>Name dot com, they name is: Mud.</p>
<p>Tom</p>
<p><br>
</p>
<p>-- </p>
<pre class="moz-signature" cols="72">Tom Henderson
ExtremeLabs, Inc.
+1 317 250 4646
Twitter: @extremelabs
Skype: extremelabsinc</pre>
</body>
</html>