<?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"
	>
<channel>
	<title>Comments on: Network hiccuping</title>
	<atom:link href="http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/</link>
	<description>Information about DreamHost Services</description>
	<pubDate>Sat, 22 Nov 2008 03:53:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Film izle</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-207440</link>
		<dc:creator>Film izle</dc:creator>
		<pubDate>Mon, 15 Sep 2008 10:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-207440</guid>
		<description>Thanks</description>
		<content:encoded><![CDATA[<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: smyl</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-107565</link>
		<dc:creator>smyl</dc:creator>
		<pubDate>Thu, 10 Jan 2008 08:20:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-107565</guid>
		<description>lol

if your depending on the income you are loosing from your website being down for a couple of hours
maybe you need to find a new source of income...</description>
		<content:encoded><![CDATA[<p>lol</p>
<p>if your depending on the income you are loosing from your website being down for a couple of hours<br />
maybe you need to find a new source of income&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pablo's Boss</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-107324</link>
		<dc:creator>Pablo's Boss</dc:creator>
		<pubDate>Wed, 09 Jan 2008 18:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-107324</guid>
		<description>YOUR BALLS!</description>
		<content:encoded><![CDATA[<p>YOUR BALLS!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scrooks</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106909</link>
		<dc:creator>scrooks</dc:creator>
		<pubDate>Tue, 08 Jan 2008 23:43:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106909</guid>
		<description>I'm having the same problem as Hugo:  very long latency (10+ seconds) to start loading, then the load is nice and fast.  http://www.scrooks.net/wiki is a one-click install that's never been touched otherwise -- I use it for testing these types of problems as a sort of proof that it's not something I've done causing the problem.  I'm having an email conversation about it with support, but so far we haven't been able to narrow in on anything.</description>
		<content:encoded><![CDATA[<p>I&#8217;m having the same problem as Hugo:  very long latency (10+ seconds) to start loading, then the load is nice and fast.  <a href="http://www.scrooks.net/wiki" rel="nofollow">http://www.scrooks.net/wiki</a> is a one-click install that&#8217;s never been touched otherwise &#8212; I use it for testing these types of problems as a sort of proof that it&#8217;s not something I&#8217;ve done causing the problem.  I&#8217;m having an email conversation about it with support, but so far we haven&#8217;t been able to narrow in on anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Hatton</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106883</link>
		<dc:creator>James Hatton</dc:creator>
		<pubDate>Tue, 08 Jan 2008 22:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106883</guid>
		<description>My site was down for an hour or so and I'm upset at this!

I am soooo angry.  

I'm taking my business and going elsewhere.

...wait.. no I'm not.  I love Dreamhost and all you guys do.

Thank you for being on top of things and awesome.

James Hatton
inhislikeness.com</description>
		<content:encoded><![CDATA[<p>My site was down for an hour or so and I&#8217;m upset at this!</p>
<p>I am soooo angry.  </p>
<p>I&#8217;m taking my business and going elsewhere.</p>
<p>&#8230;wait.. no I&#8217;m not.  I love Dreamhost and all you guys do.</p>
<p>Thank you for being on top of things and awesome.</p>
<p>James Hatton<br />
inhislikeness.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106865</link>
		<dc:creator>James</dc:creator>
		<pubDate>Tue, 08 Jan 2008 21:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106865</guid>
		<description>Grant, Fred, all...

I don't think there are really any excuses that can be made for how Dreamhost handled this, so why defend them?

They said things were resolved when they were not.  
They said it was a "hiccup" when clearly it was a "problem" or an "outage".   (What do you picture a hiccup to be?  Certainly not a long and slow dull pain...)
They mis-characterized the severity level.

(Additionally, they had a planned effort and didn't mention it but maybe it's not their policy.)

If Dreamhost is going to go on record and post status messages to their clients they can't be doing it this way.  Better for them to say nothing at all then to make misleading statements (at best) about the situation, causing a whole slew of clients to waste their time on a false premise.

There is no excuse.  Only apologies.  E.g.:

"We're sorry, we didn't know how big the problem was.  Next time we'll determine its size before saying it's small"
"We're sorry, we didn't realize the problem wasn't resolved.  Next time we'll make sure it's resolved before saying so"
"We're sorry, we used the wrong terms and severity levels.  Now we'll have a rubrik for rating each problem."
"We're sorry our status messages have been unprofessional.  We'll make sure to keep things clean and accurate from now on."
"We're sorry we don't post regular messages about planned maintenance.  That is not our policy." 
"We're sorry we don't give frequent status updates.  We wait for status requests to be logged. That is our policy." 

Let's see some of these from Dreamhost!

People are complaining about complaining about the money it costs...  How is that the issue when Dreamhost says they've got 99.99% uptime?  If they were straightforward with their numbers, then we'd understand that we're NOT getting a deal at all.  We're getting what the market can bare.  Without knowing the true risks, why shouldn't customers be upset?

As for "better communications during outages", Grant.  I think your ticket should be more explicit,  There are many great examples in this thread of what Dreamhost could actually do in the future.  Also it shouldn't be "during outages" if they are planned.  It should be "before planned maintenance".

What the people who are posting to dreamhoststatus need to understand is that if we *see anything* up there, it will calm things down because we know things are getting worked on.  It's when we see nothing when clearly there are problems (which happened first), and when we read falsehoods (which happened next), that we have every right to get really teed off and an argument defending Dreamhost holds no weight.</description>
		<content:encoded><![CDATA[<p>Grant, Fred, all&#8230;</p>
<p>I don&#8217;t think there are really any excuses that can be made for how Dreamhost handled this, so why defend them?</p>
<p>They said things were resolved when they were not.<br />
They said it was a &#8220;hiccup&#8221; when clearly it was a &#8220;problem&#8221; or an &#8220;outage&#8221;.   (What do you picture a hiccup to be?  Certainly not a long and slow dull pain&#8230;)<br />
They mis-characterized the severity level.</p>
<p>(Additionally, they had a planned effort and didn&#8217;t mention it but maybe it&#8217;s not their policy.)</p>
<p>If Dreamhost is going to go on record and post status messages to their clients they can&#8217;t be doing it this way.  Better for them to say nothing at all then to make misleading statements (at best) about the situation, causing a whole slew of clients to waste their time on a false premise.</p>
<p>There is no excuse.  Only apologies.  E.g.:</p>
<p>&#8220;We&#8217;re sorry, we didn&#8217;t know how big the problem was.  Next time we&#8217;ll determine its size before saying it&#8217;s small&#8221;<br />
&#8220;We&#8217;re sorry, we didn&#8217;t realize the problem wasn&#8217;t resolved.  Next time we&#8217;ll make sure it&#8217;s resolved before saying so&#8221;<br />
&#8220;We&#8217;re sorry, we used the wrong terms and severity levels.  Now we&#8217;ll have a rubrik for rating each problem.&#8221;<br />
&#8220;We&#8217;re sorry our status messages have been unprofessional.  We&#8217;ll make sure to keep things clean and accurate from now on.&#8221;<br />
&#8220;We&#8217;re sorry we don&#8217;t post regular messages about planned maintenance.  That is not our policy.&#8221;<br />
&#8220;We&#8217;re sorry we don&#8217;t give frequent status updates.  We wait for status requests to be logged. That is our policy.&#8221; </p>
<p>Let&#8217;s see some of these from Dreamhost!</p>
<p>People are complaining about complaining about the money it costs&#8230;  How is that the issue when Dreamhost says they&#8217;ve got 99.99% uptime?  If they were straightforward with their numbers, then we&#8217;d understand that we&#8217;re NOT getting a deal at all.  We&#8217;re getting what the market can bare.  Without knowing the true risks, why shouldn&#8217;t customers be upset?</p>
<p>As for &#8220;better communications during outages&#8221;, Grant.  I think your ticket should be more explicit,  There are many great examples in this thread of what Dreamhost could actually do in the future.  Also it shouldn&#8217;t be &#8220;during outages&#8221; if they are planned.  It should be &#8220;before planned maintenance&#8221;.</p>
<p>What the people who are posting to dreamhoststatus need to understand is that if we *see anything* up there, it will calm things down because we know things are getting worked on.  It&#8217;s when we see nothing when clearly there are problems (which happened first), and when we read falsehoods (which happened next), that we have every right to get really teed off and an argument defending Dreamhost holds no weight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mickey</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106852</link>
		<dc:creator>Mickey</dc:creator>
		<pubDate>Tue, 08 Jan 2008 21:47:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106852</guid>
		<description>Our site has been hell all day and my emails are full of complaints.  I have other sites on other servers and never have these problems that seem to be a part of beingwith Dreamhost.  That being said it is great to see a web host to so open about these issues and so quick (usually) to respond to problem reports.  We are staying with DH for now but I'm not sure how much longer we can stay if reliabiltiy does not begin to improve.</description>
		<content:encoded><![CDATA[<p>Our site has been hell all day and my emails are full of complaints.  I have other sites on other servers and never have these problems that seem to be a part of beingwith Dreamhost.  That being said it is great to see a web host to so open about these issues and so quick (usually) to respond to problem reports.  We are staying with DH for now but I&#8217;m not sure how much longer we can stay if reliabiltiy does not begin to improve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brimmer</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106826</link>
		<dc:creator>Brimmer</dc:creator>
		<pubDate>Tue, 08 Jan 2008 21:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106826</guid>
		<description>I finally got a response from last nights ticket saying "We had to give the machine a  reboot."
Now, at the exactly the same time I get the email, all of my sites go down again.</description>
		<content:encoded><![CDATA[<p>I finally got a response from last nights ticket saying &#8220;We had to give the machine a  reboot.&#8221;<br />
Now, at the exactly the same time I get the email, all of my sites go down again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hugo</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106769</link>
		<dc:creator>Hugo</dc:creator>
		<pubDate>Tue, 08 Jan 2008 20:17:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106769</guid>
		<description>Mi site is responding very slow, it has a latency over 6-10 seconds to start loading, the download speed is ok.</description>
		<content:encoded><![CDATA[<p>Mi site is responding very slow, it has a latency over 6-10 seconds to start loading, the download speed is ok.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106704</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Tue, 08 Jan 2008 17:58:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.dreamhoststatus.com/2008/01/08/network-hiccuping/#comment-106704</guid>
		<description>Resolved YES?

Sorry but NO NO NO :-(

My website still have continuous downtimes

Downtime                      Duration
08-ene-2008 18:53:56 	2 Mins 7 Secs
08-ene-2008 18:43:34 	5 Mins 31 Secs
08-ene-2008 17:07:40 	1 Hrs 16 Mins
08-ene-2008 16:55:53 	5 Mins 50 Secs
08-ene-2008 8:41:01 	 6 Hrs 14 Mins
08-ene-2008 8:04:36 	 5 Mins 28 Secs
08-ene-2008 7:33:19 	 5 Mins 25 Secs
07-ene-2008 20:43:58 	38 Mins 3 Secs

All CET times</description>
		<content:encoded><![CDATA[<p>Resolved YES?</p>
<p>Sorry but NO NO NO <img src='http://www.dreamhoststatus.com/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
<p>My website still have continuous downtimes</p>
<p>Downtime                      Duration<br />
08-ene-2008 18:53:56 	2 Mins 7 Secs<br />
08-ene-2008 18:43:34 	5 Mins 31 Secs<br />
08-ene-2008 17:07:40 	1 Hrs 16 Mins<br />
08-ene-2008 16:55:53 	5 Mins 50 Secs<br />
08-ene-2008 8:41:01 	 6 Hrs 14 Mins<br />
08-ene-2008 8:04:36 	 5 Mins 28 Secs<br />
08-ene-2008 7:33:19 	 5 Mins 25 Secs<br />
07-ene-2008 20:43:58 	38 Mins 3 Secs</p>
<p>All CET times</p>
]]></content:encoded>
	</item>
</channel>
</rss>
