<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://status.dogsbody.com"/>
    <title>Yellow on Dogsbody Technology Status Page</title>
    <link>https://status.dogsbody.com/affected/yellow/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2013-06-13T22:01:00+00:00</lastBuildDate>
    <updated>2013-06-13T22:01:00+00:00</updated>
    
    
    
      <atom:link href="https://status.dogsbody.com/affected/yellow/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] Email delayed for users of Yellow server</title>
        <link>https://status.dogsbody.com/issues/id9/</link>
        <pubDate>Thu, 13 Jun 2013 22:01:00 +0000</pubDate>
        <guid>https://status.dogsbody.com/issues/id9/</guid>
        <category>2013-06-13T22:01:00&#43;00:00</category>
        <description>We have been slowly migrating users from our old Yellow server to our shiny new Purple server and planned to complete this work in June.
Unfortunately the Yellow server has developed a fault which means we need to expedite up the migration which will now be done over the next three days.
No email will be lost in the migration however email may be delayed while it finds it’s way from the old server to the new one.</description>
        <content type="html">&lt;p&gt;We have been slowly migrating users from our old Yellow server to our shiny new Purple server and planned to complete this work in June.&lt;/p&gt;
&lt;p&gt;Unfortunately the Yellow server has developed a fault which means we need to expedite up the migration which will now be done over the next three days.&lt;/p&gt;
&lt;p&gt;No email will be lost in the migration however email may be delayed while it finds it’s way from the old server to the new one.&lt;/p&gt;
&lt;p&gt;We apologies for any inconvenience caused.&lt;/p&gt;
&lt;p&gt;Please do contact us if you find any issues with your site or email after this time.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Yellow server degraded</title>
        <link>https://status.dogsbody.com/issues/id8/</link>
        <pubDate>Tue, 07 May 2013 22:29:00 +0000</pubDate>
        <guid>https://status.dogsbody.com/issues/id8/</guid>
        <category>2013-05-07T22:29:00&#43;00:00</category>
        <description>The RAID on Yellow has become degraded and requires a rebuild.
This should not cause any outage however services may run a little slow while the build is in progress.
The build will be completed by 02:00</description>
        <content type="html">&lt;p&gt;The RAID on Yellow has become degraded and requires a rebuild.&lt;/p&gt;
&lt;p&gt;This should not cause any outage however services may run a little slow while the build is in progress.&lt;/p&gt;
&lt;p&gt;The build will be completed by 02:00&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Disabling SSH access to all servers</title>
        <link>https://status.dogsbody.com/issues/id5/</link>
        <pubDate>Tue, 19 Feb 2013 23:55:00 +0000</pubDate>
        <guid>https://status.dogsbody.com/issues/id5/</guid>
        <category>2013-02-19T23:55:00&#43;00:00</category>
        <description>It seems there is a major “0-day” vulnerability doing the rounds and a lot of data is showing SSH as the attack vector, even though the exact vulnerability hasn’t been fully discovered yet or patched.
A number of hosts have already been compromised and we feel it would be better to block SSH access to our servers now and keep your data secure than wait until something goes wrong.
If you desperately need SSH access then please do contact us and we’ll be glad to add your IP address to our whitelists.</description>
        <content type="html">&lt;p&gt;It seems there is a major “&lt;a href=&#34;https://en.wikipedia.org/wiki/Zero-day_(computing)&#34;&gt;0-day&lt;/a&gt;” vulnerability doing the rounds and a lot of data is showing SSH as the attack vector, even though the exact vulnerability hasn’t been fully discovered yet or patched.&lt;/p&gt;
&lt;p&gt;A number of hosts have already been compromised and we feel it would be better to block SSH access to our servers now and keep your data secure than wait until something goes wrong.&lt;/p&gt;
&lt;p&gt;If you desperately need SSH access then please do &lt;a href=&#34;https://www.dogsbodyhosting.net/contact/&#34;&gt;contact us&lt;/a&gt; and we’ll be glad to add your IP address to our whitelists.&lt;/p&gt;
&lt;p&gt;For those of you interested, the vulnerability seems to mostly affect Redhat/CentOS (which we use) with cPanel/Plesk installed (which we do not use) but not exclusively which is why we are taking this action.&lt;/p&gt;
&lt;p&gt;For more information on this vulnerability please see…&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://www.webhostingtalk.com/showthread.php?t=1235797&#34;&gt;http://www.webhostingtalk.com/showthread.php?t=1235797&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://seclists.org/oss-sec/2013/q1/326&#34;&gt;http://seclists.org/oss-sec/2013/q1/326&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://bugzilla.redhat.com/show_bug.cgi?id=911937&#34;&gt;https://bugzilla.redhat.com/show_bug.cgi?id=911937&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://forums.cpanel.net/f185/sshd-rootkit-323962.html&#34;&gt;http://forums.cpanel.net/f185/sshd-rootkit-323962.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; This has now been shown to be a vulnerability that only affects cPanel.  We are opening access back up on those servers with public access. Thank you for your understanding during this. We do everything we can to keep your data safe.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Yellow Reboot</title>
        <link>https://status.dogsbody.com/issues/id4/</link>
        <pubDate>Mon, 28 Jan 2013 11:27:00 +0000</pubDate>
        <guid>https://status.dogsbody.com/issues/id4/</guid>
        <category>2013-01-28T11:27:00&#43;00:00</category>
        <description>Due to a tied up process on the server our yellow.dogsbodyhosting.net server needed to be rebooted today at 23:20 on Mon 28 Jan 2013.
The reboot should take no longer than 10 minutes for all services to come back up.
Apologies for any inconvenience.</description>
        <content type="html">&lt;p&gt;Due to a tied up process on the server our yellow.dogsbodyhosting.net server needed to be rebooted today at 23:20 on Mon 28 Jan 2013.&lt;/p&gt;
&lt;p&gt;The reboot should take no longer than 10 minutes for all services to come back up.&lt;/p&gt;
&lt;p&gt;Apologies for any inconvenience.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Issue with receiving email on yellow server</title>
        <link>https://status.dogsbody.com/issues/id3/</link>
        <pubDate>Tue, 04 Dec 2012 16:26:00 +0000</pubDate>
        <guid>https://status.dogsbody.com/issues/id3/</guid>
        <category>2012-12-04T16:26:00&#43;00:00</category>
        <description>Users of our yellow.dogsbodyhosting.net server may have noticed delayed incoming email today.
We have identified the issue which was caused by a DNS server migration that had an unintended knock on change to our mailserver.
Mail was affected between 11:44 and 16:20 on Tue 4th Dec 2012.
No mail should have been lost and mail will continue to come back in to your inboxes over the next hour.</description>
        <content type="html">&lt;p&gt;Users of our yellow.dogsbodyhosting.net server may have noticed delayed incoming email today.&lt;/p&gt;
&lt;p&gt;We have identified the issue which was caused by a DNS server migration that had an unintended knock on change to our mailserver.&lt;/p&gt;
&lt;p&gt;Mail was affected between 11:44 and 16:20 on Tue 4th Dec 2012.&lt;/p&gt;
&lt;p&gt;No mail should have been lost and mail will continue to come back in to your inboxes over the next hour.&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
