<?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>The cPanel VPS Failover Challenge</title>
	<atom:link href="http://cpanelfailover.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://cpanelfailover.net</link>
	<description>UNIXy&#039;s Geographical Failover Solution</description>
	<lastBuildDate>Sun, 25 Oct 2009 06:16:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Failover Report &#8211; 21-Oct-2009</title>
		<link>http://cpanelfailover.net/2009/10/25/failover-report-21-oct-2009/</link>
		<comments>http://cpanelfailover.net/2009/10/25/failover-report-21-oct-2009/#comments</comments>
		<pubDate>Sun, 25 Oct 2009 06:16:58 +0000</pubDate>
		<dc:creator>UNIXy</dc:creator>
				<category><![CDATA[Uptime Report]]></category>
		<category><![CDATA[cpanel failover report]]></category>
		<category><![CDATA[failover report]]></category>

		<guid isPermaLink="false">http://cpanelfailover.net/?p=23</guid>
		<description><![CDATA[Per the uptime monitor, Pingdom, cpanelfailover.net was unreachable for a period of 2 minutes. During this period of time, the failover mechanism was already underway. The solution has worked as designed. Surprisingly, our other uptime monitoring vendors did not report down time. This inconsistency prompted us to research the issue and ask for an explanation [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: left;">Per the uptime monitor, Pingdom, cpanelfailover.net was unreachable for a period of 2 minutes. During this period of time, the failover mechanism was already underway. The solution has worked as designed. Surprisingly, our other uptime monitoring vendors did not report down time. This inconsistency prompted us to research the issue and ask for an explanation from Pingdom. The latter were very helpful in determining the root cause. Here&#8217;s the verbatim report from Pingdom:</p>
<blockquote style="text-align: left;"><p>It seems like the reason to why the site was reported as down is because of that it took more than 30 seconds to load it, which seems to be caused by temporary peering issues, as you can see in for example this error analysis: https://pp.pingdom.com/index.php/member/analysis/XXXXXX.</p></blockquote>
<p style="text-align: left;">This means that even though the disruption was external (remote route), the solution does indeed work. While not perfect, we are still en route to maintain the 99.99% yearly cumulative uptime we have set ourselves to achieve.</p>
<p style="text-align: left;">Cheers!</p>
]]></content:encoded>
			<wfw:commentRss>http://cpanelfailover.net/2009/10/25/failover-report-21-oct-2009/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
