<?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/"
	
	>
<channel>
	<title>
	Comments on: Poor experience and uptime with rapidvps.com	</title>
	<atom:link href="https://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom/feed" rel="self" type="application/rss+xml" />
	<link>https://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom</link>
	<description>Web Programming, Linux System Administation, and Entrepreneurship in Athens Georgia</description>
	<lastBuildDate>Thu, 13 Aug 2009 01:54:03 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>
	<item>
		<title>
		By: Hugh		</title>
		<link>https://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom/comment-page-1#comment-1340</link>

		<dc:creator><![CDATA[Hugh]]></dc:creator>
		<pubDate>Thu, 13 Aug 2009 01:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom#comment-1340</guid>

					<description><![CDATA[RapidVPS is SUCKS !!! Believe me, they are the worst Host Ive ever used. Thats why they can never grow their reputation.]]></description>
			<content:encoded><![CDATA[<p>RapidVPS is SUCKS !!! Believe me, they are the worst Host Ive ever used. Thats why they can never grow their reputation.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Brandon		</title>
		<link>https://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom/comment-page-1#comment-940</link>

		<dc:creator><![CDATA[Brandon]]></dc:creator>
		<pubDate>Tue, 03 Jun 2008 16:46:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom#comment-940</guid>

					<description><![CDATA[Thanks for the follow-up Rick.   You guys did keep me updated fairly regularly during that problem.  It felt like it dragged on forever though - probably because I had a lot of work to get done and was frustrated that I couldn&#039;t even reliably stay connected to the server where all of it was stored.

Ideally, in a situation like that  where you are troubleshooting a hardware problem, I&#039;d like to see you move the customer data to a new server (something as easy as moving the hard drives to a new box), then troubleshoot the problematic server when it doesn&#039;t affect customers.]]></description>
			<content:encoded><![CDATA[<p>Thanks for the follow-up Rick.   You guys did keep me updated fairly regularly during that problem.  It felt like it dragged on forever though &#8211; probably because I had a lot of work to get done and was frustrated that I couldn&#8217;t even reliably stay connected to the server where all of it was stored.</p>
<p>Ideally, in a situation like that  where you are troubleshooting a hardware problem, I&#8217;d like to see you move the customer data to a new server (something as easy as moving the hard drives to a new box), then troubleshoot the problematic server when it doesn&#8217;t affect customers.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rick Blundell		</title>
		<link>https://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom/comment-page-1#comment-939</link>

		<dc:creator><![CDATA[Rick Blundell]]></dc:creator>
		<pubDate>Tue, 03 Jun 2008 15:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom#comment-939</guid>

					<description><![CDATA[Hi Brandon, sorry to hear about the bad experience. I looked back in our records based on the date of your blog entry, and we did have a service node failure on this day. It turned out to be a failed ram dimm. After a few hours of physically troubleshooting the system at the datacenter (the reboots you noted), we managed to isolate the problem to a single dimm chip. Unfortunately these things do happen and we try to deal with them the fastest way possible. I do believe we kept in constant contact to inform you that we were working on the problem, and it was eventually solved. I just checked the node and it has 28 days of uptime, damn hardware failures!

Best of luck!
Rick Blundell
RapidVPS]]></description>
			<content:encoded><![CDATA[<p>Hi Brandon, sorry to hear about the bad experience. I looked back in our records based on the date of your blog entry, and we did have a service node failure on this day. It turned out to be a failed ram dimm. After a few hours of physically troubleshooting the system at the datacenter (the reboots you noted), we managed to isolate the problem to a single dimm chip. Unfortunately these things do happen and we try to deal with them the fastest way possible. I do believe we kept in constant contact to inform you that we were working on the problem, and it was eventually solved. I just checked the node and it has 28 days of uptime, damn hardware failures!</p>
<p>Best of luck!<br />
Rick Blundell<br />
RapidVPS</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Brandon		</title>
		<link>https://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom/comment-page-1#comment-881</link>

		<dc:creator><![CDATA[Brandon]]></dc:creator>
		<pubDate>Tue, 15 Jan 2008 18:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom#comment-881</guid>

					<description><![CDATA[We do have several dedicated servers, but they run our production servers, and I don&#039;t want to be doing development on them.   

The new VPS that I have actually works great.  I&#039;m logged onto it all day long and it performs very well, as I have expected.  I also have one of our dedicated servers rsync&#039;ing all of the code and subversion repositories every 15 minutes, just in case something like that happens again.

The problem here was not with a VPS.  I have used VPS&#039;s from various companies and have a pretty good idea what to expect out of them.  I was just surprised at the seemingly low performance and number of problems I got from rapidvps.]]></description>
			<content:encoded><![CDATA[<p>We do have several dedicated servers, but they run our production servers, and I don&#8217;t want to be doing development on them.   </p>
<p>The new VPS that I have actually works great.  I&#8217;m logged onto it all day long and it performs very well, as I have expected.  I also have one of our dedicated servers rsync&#8217;ing all of the code and subversion repositories every 15 minutes, just in case something like that happens again.</p>
<p>The problem here was not with a VPS.  I have used VPS&#8217;s from various companies and have a pretty good idea what to expect out of them.  I was just surprised at the seemingly low performance and number of problems I got from rapidvps.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: reader		</title>
		<link>https://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom/comment-page-1#comment-880</link>

		<dc:creator><![CDATA[reader]]></dc:creator>
		<pubDate>Sat, 12 Jan 2008 18:58:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom#comment-880</guid>

					<description><![CDATA[If you are seriously putting that much into a VPS 
why not just get a dedicated server. 
VPS&#039;s are just fancy shared hosting accounts
with a crap ton more overhead and problems. 

The problems you ran into were pretty typical of all 
VPS&#039;s because they are just a shared hosts. 
If you are writting 6 hours of php a day you should
be running your own box.]]></description>
			<content:encoded><![CDATA[<p>If you are seriously putting that much into a VPS<br />
why not just get a dedicated server.<br />
VPS&#8217;s are just fancy shared hosting accounts<br />
with a crap ton more overhead and problems. </p>
<p>The problems you ran into were pretty typical of all<br />
VPS&#8217;s because they are just a shared hosts.<br />
If you are writting 6 hours of php a day you should<br />
be running your own box.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Brandon		</title>
		<link>https://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom/comment-page-1#comment-862</link>

		<dc:creator><![CDATA[Brandon]]></dc:creator>
		<pubDate>Wed, 12 Dec 2007 19:44:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.brandonchecketts.com/archives/poor-experience-and-uptime-with-rapidvpscom#comment-862</guid>

					<description><![CDATA[Follow up:

The server was down for about 4 hours while it was fscking.   The support staff didn&#039;t know if the drive was going to recover successfully, so they did offer to restore a backup copy of my vps on a different server, but that would have taken quite a while longer to copy to a new server and extract.

Once it came back up, the server did (thankfully) have all of my data on it.   It would stay up for a few minutes and then reboot.  I was able to copy all of my critical information off in between a couple of those reboots.

I got everything set up on a new RimuHosting server but would still login to the rapidvps server to see how it was doing.   It died or was rebooted about 10 more times.  Once I had all of my critical information off, it was actually funny to watch.

I canceled my rapidvps account today and they did provide me with a full refund for the past month without any haggling.]]></description>
			<content:encoded><![CDATA[<p>Follow up:</p>
<p>The server was down for about 4 hours while it was fscking.   The support staff didn&#8217;t know if the drive was going to recover successfully, so they did offer to restore a backup copy of my vps on a different server, but that would have taken quite a while longer to copy to a new server and extract.</p>
<p>Once it came back up, the server did (thankfully) have all of my data on it.   It would stay up for a few minutes and then reboot.  I was able to copy all of my critical information off in between a couple of those reboots.</p>
<p>I got everything set up on a new RimuHosting server but would still login to the rapidvps server to see how it was doing.   It died or was rebooted about 10 more times.  Once I had all of my critical information off, it was actually funny to watch.</p>
<p>I canceled my rapidvps account today and they did provide me with a full refund for the past month without any haggling.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
