<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Hosting Blog &#187; &#187; DreamHost Web Hosting</title>
	<atom:link href="http://www.hosting-blog.com/tag/dreamhost-web-hosting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hosting-blog.com</link>
	<description>News from the hosting world</description>
	<lastBuildDate>Thu, 20 Nov 2008 13:01:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>DreamHost&#8217;s 7.5 Million Dollar Mistake</title>
		<link>http://www.hosting-blog.com/news/dreamhosts-75-million-dollar-mistake/</link>
		<comments>http://www.hosting-blog.com/news/dreamhosts-75-million-dollar-mistake/#comments</comments>
		<pubDate>Tue, 15 Jan 2008 22:43:25 +0000</pubDate>
		<dc:creator>Web Hosting Blog</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Dreamhost]]></category>
		<category><![CDATA[DreamHost Web Hosting]]></category>
		<category><![CDATA[dreamhost.com]]></category>

		<guid isPermaLink="false">http://www.hosting-blog.com/news/dreamhosts-75-million-dollar-mistake/</guid>
		<description><![CDATA[Last night, DreamHost ran a standard billing cycle to clean up stragglers from 2007. Unfortunately, the biller was run for 2008 (December 31st, 2008 to be exact). This caused everyone to be billed as if today was 2008-12-31, wreaking havoc, including debiting huge amounts of money from people&#8217;s checking accounts, suspending accounts for non-payments and [...]]]></description>
			<content:encoded><![CDATA[<p>Last night, <a href="http://www.dreamhost.com/">DreamHost</a> ran a standard billing cycle to clean up stragglers from 2007. Unfortunately, the biller was run for 2008 (December 31st, 2008 to be exact). This caused everyone to be billed as if today was 2008-12-31, wreaking havoc, including debiting huge amounts of money from people&#8217;s checking accounts, suspending accounts for non-payments and all the &#8220;worst possible scenario&#8221; situations you could possibly imagine.</p>
<blockquote><p>We had a <em>teensy eensy weensy</em> little billing error last night… my first clue <em>something</em> was up when I saw this morning’s <strong>daily</strong> billing report (so far): <strong>$7,500,000</strong>.</p>
<p>It turns out due to my excessively fat fingers, <strong>nearly every one</strong> of our customers has been seriously over-billed in the last 12 hours.</p>
<p>&#8230;</p>
<p><strong>The end to this story</strong> is that of course, <strong>I’m</strong> very very sorry, <strong>we’re</strong> very very sorry, and I’m sure <strong>you’re</strong> very very sorry this happened. I really am. I understand the sort of problems that an unexpected large charge to your credit card (or worse yet, your debit card) can cause. If the tone of this blog post seemed a little light, I apologize I don’t mean to offend and I realize how serious an issue this is. I’ve been up since 3:50am trying to undo the damage and maybe I’m a little shell-shocked.</p>
<p>&#8230;</p>
<p>We’re going through and fixing everything right now, but it may take several hours before all affected accounts are corrected. You will receive an email when yours is fixed, and if your credit card was charged, the charge will be refunded automatically.</p></blockquote>
<p><em>Source: <a href="http://www.dreamhoststatus.com/2008/01/15/billing-issues/">dreamhoststatus.com</a> and <a href="http://blog.dreamhost.com/2008/01/15/um-whoops/">blog.dreamhost.com</a></em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.hosting-blog.com/news/dreamhosts-75-million-dollar-mistake/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>DreamHost Blocks GoogleBot</title>
		<link>http://www.hosting-blog.com/news/dreamhost-blocks-googlebot/</link>
		<comments>http://www.hosting-blog.com/news/dreamhost-blocks-googlebot/#comments</comments>
		<pubDate>Tue, 22 May 2007 00:00:00 +0000</pubDate>
		<dc:creator>Web Hosting Blog</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[DreamHost Web Hosting]]></category>
		<category><![CDATA[dreamhost.com]]></category>

		<guid isPermaLink="false">http://www.hosting-blog.com/news/dreamhost-blocks-googlebot</guid>
		<description><![CDATA[<a href="http://www.thewhir.com/find/web-hosts/dir/small_business_web_hosting.cfm">Web hosting provider</a> <a href="http://www.dreamhost.com/">DreamHost Web Hosting</a> has sent an email to its customer, the owner of Romanian site <a href="http://www.zoso.ro/">Zoso.ro</a>, ordering that its high traffic sites block the Googlebot, reports <a href="http://www.searchenginejournal.com/dreamhost-blocks-googlebot-on-client-sites/4932/">Search Engine Journal</a>, an act that would be potentially crippling to the online enterprise.]]></description>
			<content:encoded><![CDATA[<p>Web hosting provider <a href="http://www.dreamhost.com/">DreamHost Web Hosting</a> has sent an email to its customer, the owner of Romanian site <a href="http://www.zoso.ro/">Zoso.ro</a>, ordering that its high traffic sites block the Googlebot, reports <a href="http://www.searchenginejournal.com/dreamhost-blocks-googlebot-on-client-sites/4932/">Search Engine Journal</a>, an act that would be potentially crippling to the online enterprise.</p>
<p>The email sent to Zoso.ro&#8217;s owner from DreamHost states that the Google bot&#8217;s activity on Zoso.ro&#8217;s sites was creating a heavy load on the DreamHost Web server. DreamHost says that this surge in traffic was affecting its other customers on Zoso.ro&#8217;s shared server.</p>
<p>The email proceeded to notify Zoso.ro&#8217;s owner that &#8220;in order to maintain stability on the Web server&#8221;, DreamHost was &#8220;forced to block Google bot via the .htaccess file.&#8221; The Web host then suggested to Zoso.ro&#8217;s owner that he make files unsearchable by robots and crawlers, since this usually adds to a greater number of hits.</p>
<p>DreamHost says it hosts more than 500,000 domains, which it doesn&#8217;t explicitly identify as parked domains, but which may very likely be the case.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hosting-blog.com/news/dreamhost-blocks-googlebot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

