<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: OSFlash down time and a warning about LiquidWeb</title>
	<atom:link href="http://aralbalkan.com/753/feed" rel="self" type="application/rss+xml" />
	<link>http://aralbalkan.com/753</link>
	<description>Passionate geekisms.</description>
	<lastBuildDate>Tue, 22 May 2012 18:33:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sue</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-258041</link>
		<dc:creator>Sue</dc:creator>
		<pubDate>Thu, 08 Oct 2009 18:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-258041</guid>
		<description>Just wondering how your new web hosting company is working out for you and who you chose?</description>
		<content:encoded><![CDATA[<p>Just wondering how your new web hosting company is working out for you and who you chose?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anony</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-210045</link>
		<dc:creator>anony</dc:creator>
		<pubDate>Thu, 29 Jan 2009 05:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-210045</guid>
		<description>To the original poster, you were on a shared environment, if your site is affecting others what do you expect?  How is it fair to others to NOT suspend your site, and let it continue to affect other people?  What you pay for the shared hosting is cheap so stop whining about it considering you are paying pennies.  They have a ton of other customers who pay a lot more than you do and you got more than your money&#039;s worth, LiquidWeb is the best hosting out there, and they have the most helpful support staff on their dedicated server team who will do anything you ask them to.</description>
		<content:encoded><![CDATA[<p>To the original poster, you were on a shared environment, if your site is affecting others what do you expect?  How is it fair to others to NOT suspend your site, and let it continue to affect other people?  What you pay for the shared hosting is cheap so stop whining about it considering you are paying pennies.  They have a ton of other customers who pay a lot more than you do and you got more than your money&#8217;s worth, LiquidWeb is the best hosting out there, and they have the most helpful support staff on their dedicated server team who will do anything you ask them to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-155197</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 12 Jun 2008 21:17:01 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-155197</guid>
		<description>Personally anytime you use a VPS you know its like moving into a frat house. You have 30 guys sharing one house problems will always arise. It is a bad situation for the host and yourself. As other have posted moving to another VPS on another host will cause you same issues down the road. Moving to a dedicated server is really your only option. I have my Server hosted at Server Intellect and if say someone or something goes rouge on my server at least i know it wont be shut down. The server would have to break the TOS agreement in order for my server and services to be shut down, which personally if someone has gained access to my box I want it shut down ASAP anyways. Dedicated server is the way to go, never have to worry about someone bogging down the box.</description>
		<content:encoded><![CDATA[<p>Personally anytime you use a VPS you know its like moving into a frat house. You have 30 guys sharing one house problems will always arise. It is a bad situation for the host and yourself. As other have posted moving to another VPS on another host will cause you same issues down the road. Moving to a dedicated server is really your only option. I have my Server hosted at Server Intellect and if say someone or something goes rouge on my server at least i know it wont be shut down. The server would have to break the TOS agreement in order for my server and services to be shut down, which personally if someone has gained access to my box I want it shut down ASAP anyways. Dedicated server is the way to go, never have to worry about someone bogging down the box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fang</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-65028</link>
		<dc:creator>fang</dc:creator>
		<pubDate>Sat, 04 Aug 2007 00:24:54 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-65028</guid>
		<description>Hi Aral,

Can I download Red5 from sourceforge or somewhere else? Thanks.</description>
		<content:encoded><![CDATA[<p>Hi Aral,</p>
<p>Can I download Red5 from sourceforge or somewhere else? Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Public SWX gateway is down! at Aral Balkan</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-45466</link>
		<dc:creator>Public SWX gateway is down! at Aral Balkan</dc:creator>
		<pubDate>Sat, 02 Jun 2007 20:36:20 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-45466</guid>
		<description>[...] It&#8217;s so sad because I&#8217;ve been with these people for the past five years and they were so amazing (at least at the beginning). I am still in disbelief that they would do this. It&#8217;s the worst thing you can do as a web host and it isn&#8217;t the first time it has happened to me either (I had LiquidWeb do something similar on a false alarm once). It&#8217;s a horrible thing to disable someone&#8217;s application without telling them. Instead, you should contact them and propose a solution (&#8221;look, you&#8217;ve outgrown this account, let&#8217;s move you to this one.&#8221;) [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s so sad because I&#8217;ve been with these people for the past five years and they were so amazing (at least at the beginning). I am still in disbelief that they would do this. It&#8217;s the worst thing you can do as a web host and it isn&#8217;t the first time it has happened to me either (I had LiquidWeb do something similar on a false alarm once). It&#8217;s a horrible thing to disable someone&#8217;s application without telling them. Instead, you should contact them and propose a solution (&#8221;look, you&#8217;ve outgrown this account, let&#8217;s move you to this one.&#8221;) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-11836</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 01 Mar 2007 15:51:23 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-11836</guid>
		<description>Hi Aral,

I&#039;m a person who happened to come across this web page while searching for reviews and such on LiquidWeb. Being a Sysadmin for a hosting company and reading through this I do understand what you have said, but I can also understand their policy of turning you off. 

Look at a scenario of another VPS on the same server also went rouge and was affecting your website. You phone them to find out what&#039;s going on and why you getting such poor performance only to be told &quot;Another VPS on the server has gone rouge, we have emailed the client and are awaiting his response&quot;. 

I doubt very much you are going to be calm and say &quot;sure, no problem, thanks&quot; you are more than likely going to ask why they can&#039;t just turn it off, so it doesn&#039;t affect your websites. Fact of the matter is that you wouldn&#039;t care if they turned off another rouge VPS to make sure your vps isn&#039;t affected, so I don&#039;t see why other people who are hosted on the same server should care.

Unfortunately the hosting company always gets stuck in the middle of situations like this, where you have 50 clients screaming and shouting because 1 client is affecting their websites. Personally I think LiquidWeb made the right decision, turn off your vps and notify you about it. If you don&#039;t want to be affected nor have others affected by Neighbor-to-Neighbor performance problems, then consider going with a dedicated server rather than a vps solution.


kthx
Dave</description>
		<content:encoded><![CDATA[<p>Hi Aral,</p>
<p>I&#8217;m a person who happened to come across this web page while searching for reviews and such on LiquidWeb. Being a Sysadmin for a hosting company and reading through this I do understand what you have said, but I can also understand their policy of turning you off. </p>
<p>Look at a scenario of another VPS on the same server also went rouge and was affecting your website. You phone them to find out what&#8217;s going on and why you getting such poor performance only to be told &#8220;Another VPS on the server has gone rouge, we have emailed the client and are awaiting his response&#8221;. </p>
<p>I doubt very much you are going to be calm and say &#8220;sure, no problem, thanks&#8221; you are more than likely going to ask why they can&#8217;t just turn it off, so it doesn&#8217;t affect your websites. Fact of the matter is that you wouldn&#8217;t care if they turned off another rouge VPS to make sure your vps isn&#8217;t affected, so I don&#8217;t see why other people who are hosted on the same server should care.</p>
<p>Unfortunately the hosting company always gets stuck in the middle of situations like this, where you have 50 clients screaming and shouting because 1 client is affecting their websites. Personally I think LiquidWeb made the right decision, turn off your vps and notify you about it. If you don&#8217;t want to be affected nor have others affected by Neighbor-to-Neighbor performance problems, then consider going with a dedicated server rather than a vps solution.</p>
<p>kthx<br />
Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BIT-101 Blog &#187; Blog Archive &#187; Mail was down, server was full</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-7427</link>
		<dc:creator>BIT-101 Blog &#187; Blog Archive &#187; Mail was down, server was full</dc:creator>
		<pubDate>Sun, 12 Nov 2006 13:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-7427</guid>
		<description>[...] This reminds me a bit of Aral&#8217;s issue with Liquidweb, where they just shut down OSFlash with no warning or notice due to some big load that the site was putting on the server. [...]</description>
		<content:encoded><![CDATA[<p>[...] This reminds me a bit of Aral&#8217;s issue with Liquidweb, where they just shut down OSFlash with no warning or notice due to some big load that the site was putting on the server. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reyer</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-5278</link>
		<dc:creator>Reyer</dc:creator>
		<pubDate>Sun, 08 Oct 2006 22:33:15 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-5278</guid>
		<description>Aral, I would be happy to host osflash or any mirror. Our servers are busy nose picking the whole day. Maybe OSFlash will make them really doing their job! Let me know.</description>
		<content:encoded><![CDATA[<p>Aral, I would be happy to host osflash or any mirror. Our servers are busy nose picking the whole day. Maybe OSFlash will make them really doing their job! Let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tink</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-5009</link>
		<dc:creator>Tink</dc:creator>
		<pubDate>Tue, 03 Oct 2006 12:15:10 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-5009</guid>
		<description>&quot;They really need to implement a policy that says that they will not shut down web sites/servers before investigating the cause...

But this isn’t the rank-and-file support person’s problem (unless they weren’t following procedure), it’s the fault of the procedure/process itself.&quot;

Well the comment below would imply that isn&#039;t tehir policy.

&quot;It is not company policy to disable server environments in this manner and it was an unfortunate mistake that you were not first contacted.&quot;</description>
		<content:encoded><![CDATA[<p>&#8220;They really need to implement a policy that says that they will not shut down web sites/servers before investigating the cause&#8230;</p>
<p>But this isn’t the rank-and-file support person’s problem (unless they weren’t following procedure), it’s the fault of the procedure/process itself.&#8221;</p>
<p>Well the comment below would imply that isn&#8217;t tehir policy.</p>
<p>&#8220;It is not company policy to disable server environments in this manner and it was an unfortunate mistake that you were not first contacted.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aral</title>
		<link>http://aralbalkan.com/753/comment-page-1#comment-4973</link>
		<dc:creator>aral</dc:creator>
		<pubDate>Mon, 02 Oct 2006 17:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/753#comment-4973</guid>
		<description>Tink: As you mention at the end of your comment, Travis is basically doing what he can to make up for it. I have no doubt that the exposure that a popular (and targetted?) blog provides may set me aside from the rest but I have to say that until this incident, LiquidWeb&#039;s support has actually been quite good. This appears to be more of a policy issue than anything else. They really need to implement a policy that says that they will not shut down web sites/servers before investigating the cause. Of course, if something is repeatedly causing problems, they should shut it down. But they shouldn&#039;t if it is an isolated case. But this isn&#039;t the rank-and-file support person&#039;s problem (unless they weren&#039;t following procedure), it&#039;s the fault of the procedure/process itself.</description>
		<content:encoded><![CDATA[<p>Tink: As you mention at the end of your comment, Travis is basically doing what he can to make up for it. I have no doubt that the exposure that a popular (and targetted?) blog provides may set me aside from the rest but I have to say that until this incident, LiquidWeb&#8217;s support has actually been quite good. This appears to be more of a policy issue than anything else. They really need to implement a policy that says that they will not shut down web sites/servers before investigating the cause. Of course, if something is repeatedly causing problems, they should shut it down. But they shouldn&#8217;t if it is an isolated case. But this isn&#8217;t the rank-and-file support person&#8217;s problem (unless they weren&#8217;t following procedure), it&#8217;s the fault of the procedure/process itself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

