<?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>Hosting Matters Status Page (Remote)</title>
	<atom:link href="http://hmstatus.com/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://hmstatus.com</link>
	<description></description>
	<lastBuildDate>Fri, 04 Jun 2010 15:25:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>WARHOL: Emergency migrations</title>
		<link>http://hmstatus.com/?p=56</link>
		<comments>http://hmstatus.com/?p=56#comments</comments>
		<pubDate>Fri, 04 Jun 2010 15:25:31 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[Servers]]></category>
		<category><![CDATA[warhol]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=56</guid>
		<description><![CDATA[<p>All warhol-based accounts will be relocated to pollock, effective immediately. An apparent network interface issue is causing the server to babble uncontrollably, resulting in jabber traffic that impacts the ability to reach the server or services to respond properly. The moves to pollock will keep all sites on PHP4/mySQL4 footing for the time being, due [...]]]></description>
			<content:encoded><![CDATA[<p>All warhol-based accounts will be relocated to pollock, effective immediately. An apparent network interface issue is causing the server to babble uncontrollably, resulting in jabber traffic that impacts the ability to reach the server or services to respond properly. The moves to pollock will keep all sites on PHP4/mySQL4 footing for the time being, due to the shorter than usual notice related to these migrations. This will help us avoid any application-related issues on sites until a proper migration to PHP5/mySQL5 can be done with advance notice.</p>
<p>If you have any questions related to these migrations, please contact support via the usual means.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=56</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[Servers] Calliope: reboot and file system check</title>
		<link>http://hmstatus.com/?p=52</link>
		<comments>http://hmstatus.com/?p=52#comments</comments>
		<pubDate>Mon, 19 Apr 2010 13:28:33 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[Servers]]></category>
		<category><![CDATA[calliope]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=52</guid>
		<description><![CDATA[<p>Calliope is currently undergoing a reboot and file system check. It will return shortly.</p>
]]></description>
			<content:encoded><![CDATA[<p>Calliope is currently undergoing a reboot and file system check. It will return shortly.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=52</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[Maintenance] Firewall, php, and mailscanner updates</title>
		<link>http://hmstatus.com/?p=50</link>
		<comments>http://hmstatus.com/?p=50#comments</comments>
		<pubDate>Tue, 13 Apr 2010 23:59:25 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Servers]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=50</guid>
		<description><![CDATA[<p>From the evening of April 16  and continuing through April 18, we will be performing updates and/or maintenance on all shared servers for PHP, firewall, mailscanner, and PCI compliance items. On the dedicated server side, we will be performing firewall and Mailscanner updates and maintenance where required. No client impact is expected. </p>
<p>If you [...]]]></description>
			<content:encoded><![CDATA[<p>From the evening of April 16  and continuing through April 18, we will be performing updates and/or maintenance on all shared servers for PHP, firewall, mailscanner, and PCI compliance items. On the dedicated server side, we will be performing firewall and Mailscanner updates and maintenance where required. No client impact is expected. </p>
<p>If you have any questions related to these maintenance items, please contact support via the usual means.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=50</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>False/fraudulent domain renewal notices</title>
		<link>http://hmstatus.com/?p=48</link>
		<comments>http://hmstatus.com/?p=48#comments</comments>
		<pubDate>Mon, 29 Mar 2010 01:18:54 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[Domains]]></category>
		<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=48</guid>
		<description><![CDATA[<p>Please be on the lookout for false/fraudulent domain renewal notices. This includes both Domain Registry of America (DROA) which has been discussed previously in the forums, as well as the latest ones we have seen, from an outfit claiming to be domainrenewalonline.org. The latter has been sending out notices asking domain holders to click a [...]]]></description>
			<content:encoded><![CDATA[<p>Please be on the lookout for false/fraudulent domain renewal notices. This includes both Domain Registry of America (DROA) which has been discussed previously in the forums, as well as the latest ones we have seen, from an outfit claiming to be domainrenewalonline.org. The latter has been sending out notices asking domain holders to click a link to renew their domain(s), at which time they will receive a &#8220;conformation&#8221; [sic] that the renewal has been completed. Please <strong>do not</strong> click on any such links from this or any other sender if your domain was registered through us or transferred to our management queue from another registrar. Domains registered by us on your behalf will be automatically invoiced and renewed as usual, and no action is required other than the processing of the renewal invoice.</p>
<p>If you have any questions related to this, or receive notices about your domain(s) and have questions, please contact support, and include the message you have received. We will be happy to go through those with you.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=48</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[Maintenance] Firewall, mailscanner udpates</title>
		<link>http://hmstatus.com/?p=46</link>
		<comments>http://hmstatus.com/?p=46#comments</comments>
		<pubDate>Fri, 26 Mar 2010 23:34:37 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[Servers]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=46</guid>
		<description><![CDATA[<p>Firewall and mailscanner updates will be done throughout the network where required, from March 26-28. No client impact is expected.</p>
<p>If you have any questions related to this maintenance, please contact support via the usual means.</p>
]]></description>
			<content:encoded><![CDATA[<p>Firewall and mailscanner updates will be done throughout the network where required, from March 26-28. No client impact is expected.</p>
<p>If you have any questions related to this maintenance, please contact support via the usual means.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=46</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MARJORAM: Migrations and retirement</title>
		<link>http://hmstatus.com/?p=42</link>
		<comments>http://hmstatus.com/?p=42#comments</comments>
		<pubDate>Tue, 23 Mar 2010 14:06:24 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[Servers]]></category>
		<category><![CDATA[marjoram]]></category>
		<category><![CDATA[mint]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=42</guid>
		<description><![CDATA[<p>All sites from marjoram will be relocated to the new mint server on Thursday, March 25, beginning at 8 PM Eastern US time. No action is required on your part unless you are managing your own DNS elsewhere. We will identify any sites that are doing so and send separate notices to those clients with [...]]]></description>
			<content:encoded><![CDATA[<p>All sites from marjoram will be relocated to the new mint server on Thursday, March 25, beginning at 8 PM Eastern US time. No action is required on your part unless you are managing your own DNS elsewhere. We will identify any sites that are doing so and send separate notices to those clients with the new settings to point sites to mint.</p>
<p>If you have any questions related to these migrations, please contact support via the usual means.</p>
<p>Thanks.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=42</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[SERVERS] Escher, drive issues</title>
		<link>http://hmstatus.com/?p=36</link>
		<comments>http://hmstatus.com/?p=36#comments</comments>
		<pubDate>Sat, 14 Mar 2009 17:24:24 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[Servers]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=36</guid>
		<description><![CDATA[<p>We are currently seeing some rather major issues with escher that indicate an impending hardware failure. At this time we are attempting, on an emergency basis, to relocate sites from this server to others within the network. If for some reason this is not possible, given the significant errors we are seeing, we will restore [...]]]></description>
			<content:encoded><![CDATA[<p>We are currently seeing some rather major issues with escher that indicate an impending hardware failure. At this time we are attempting, on an emergency basis, to relocate sites from this server to others within the network. If for some reason this is not possible, given the significant errors we are seeing, we will restore sites from the backups that ran last night. Those backups appear to be intact, and we will attempt to keep the original escher online as long as possible in order to grab any further files that we can from it before it is completely inaccessible.</p>
<p>If you have any questions, please contact support via the usual means.</p>
<p>Edit, 4:45 PM Eastern: All escher-based accounts have been restored to other servers in the network from the backup set. We are attempting to get finals from the original server, to have on hand in the event they are required for any reason.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=36</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[NETWORK] High traffic warning: January 20, 2009</title>
		<link>http://hmstatus.com/?p=33</link>
		<comments>http://hmstatus.com/?p=33#comments</comments>
		<pubDate>Tue, 20 Jan 2009 02:17:30 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=33</guid>
		<description><![CDATA[<p>Tuesday, January 20, 2009 is the Presidential Inauguration. Due to the historic nature of this term&#8217;s inauguration, we are expecting a higher than usual traffic levels outside the usual peak times of 10:00 to 4:00 PM Eastern US time. All staff will be on hand to monitor the network and servers to immediately address any [...]]]></description>
			<content:encoded><![CDATA[<p>Tuesday, January 20, 2009 is the Presidential Inauguration. Due to the historic nature of this term&#8217;s inauguration, we are expecting a higher than usual traffic levels outside the usual peak times of 10:00 to 4:00 PM Eastern US time. All staff will be on hand to monitor the network and servers to immediately address any issues that may arise. </p>
<p>If you have any questions related to this announcement, please contact support via the usual means.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=33</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[NETWORK] Level 3 issues, US &#8211; Northeast</title>
		<link>http://hmstatus.com/?p=25</link>
		<comments>http://hmstatus.com/?p=25#comments</comments>
		<pubDate>Sun, 28 Dec 2008 01:10:14 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=25</guid>
		<description><![CDATA[<p>We have reports and confirmation from other operators of an issue with Level3 primarily affecting routing from the US/Northeast. If you are affected by this issue, your trace to your site/server may look like this:</p>
<p>traceroute to 63.247.133.70 (63.247.133.70), 30 hops max, 40 byte packets
1  heekinlaw.com (65.18.172.2)  1.013 ms  1.224 ms  1.215 [...]]]></description>
			<content:encoded><![CDATA[<p>We have reports and confirmation from other operators of an issue with Level3 primarily affecting routing from the US/Northeast. If you are affected by this issue, your trace to your site/server may look like this:</p>
<p>traceroute to 63.247.133.70 (63.247.133.70), 30 hops max, 40 byte packets<br />
1  heekinlaw.com (65.18.172.2)  1.013 ms  1.224 ms  1.215 ms<br />
2   (69.94.3.5)  0.950 ms  0.950 ms  1.182 ms<br />
3  69.182.114.205 (69.182.114.205)  2.575 ms  2.811 ms  2.808 ms<br />
4  bb1-g1-0-2.mrdnct.sbcglobal.net (151.164.42.54)  3.147 ms  3.387 ms  3.380 ms<br />
5  70.245.63.207 (70.245.63.207)  9.135 ms  9.131 ms *<br />
6  asn3356-level3.eqnwnj.sbcglobal.net (151.164.89.250)  9.116 ms  7.781 ms  7.856 ms<br />
7  ae-31-53.ebr1.Newark1.Level3.net (4.68.99.94)  7.936 ms  20.370 ms  20.364 ms<br />
8  ae-1-100.ebr2.Newark1.Level3.net (4.69.132.22)  7.702 ms  7.697 ms  7.689 ms<br />
9  ae-4-4.ebr2.Washington1.Level3.net (4.69.132.101)  13.161 ms  13.156 ms  13.414 ms<br />
10  * * *<br />
11  * * *<br />
12  * * *<br />
13  * * *<br />
14  * * *<br />
15  * * *<br />
16  * * *</p>
<p>All servers and services are up and operational within the network. As the remote monitor is also affected by this issue, it has been shut down for now, to save unnecessary paging. Local monitoring will be utilized until Level 3 clears whatever issues they are having. Unfortunately, there is nothing we can do related to this issue. We are currently scouting for news to determine if there is any indication from them as to what the problem is and any ETA to resolution.</p>
<p>Update 1:20 PM: Latency report from internetpulse</p>
<p><img class="alignnone size-full wp-image-29" title="Level3 12-28-2008" src="http://hmstatus.com/wp-content/uploads/2008/12/l312282008.jpg" alt="Level3 12-28-2008" width="825" height="531" /></p>
<p>There is currently an unconfirmed report of a fiber cut in Michigan.</p>
<div id="attachment_30" class="wp-caption alignnone" style="width: 839px"><img class="size-full wp-image-30" title="Level3 12-28-2008" src="http://hmstatus.com/wp-content/uploads/2008/12/l312282008-2.jpg" alt="Level 3, Detroit" width="829" height="274" /><p class="wp-caption-text">Level 3, Detroit</p></div>
<p>Update 1:40 PM: It appears that Level3 has cleared their issue. The remote monitor has been enabled once more.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=25</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[NETWORK] Network issue</title>
		<link>http://hmstatus.com/?p=20</link>
		<comments>http://hmstatus.com/?p=20#comments</comments>
		<pubDate>Fri, 26 Dec 2008 03:19:41 +0000</pubDate>
		<dc:creator>HM Admin</dc:creator>
				<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://hmstatus.com/?p=20</guid>
		<description><![CDATA[<p>We are currently working a network issue related to a blown switch port problem we had earlier. This issue will result in slowdowns and/or complete timeouts for various service requests.</p>
<p>Update: This issue has been resolved. Total impact time: 12 minutes.</p>
]]></description>
			<content:encoded><![CDATA[<p>We are currently working a network issue related to a blown switch port problem we had earlier. This issue will result in slowdowns and/or complete timeouts for various service requests.</p>
<p>Update: This issue has been resolved. Total impact time: 12 minutes.</p>
]]></content:encoded>
			<wfw:commentRss>http://hmstatus.com/?feed=rss2&amp;p=20</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
