<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Website Uptime Monitoring Systems</title>
	<atom:link href="http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/</link>
	<description>Random ramblings and ravings of Richy C</description>
	<lastBuildDate>Wed, 11 Jan 2012 18:16:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: monitoring uptime</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-191738</link>
		<dc:creator>monitoring uptime</dc:creator>
		<pubDate>Tue, 20 Oct 2009 03:51:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-191738</guid>
		<description>Nice post. Thanks for sharing it. Better if you can monitor website rank, position and uptime in one place!</description>
		<content:encoded><![CDATA[<p>Nice post. Thanks for sharing it. Better if you can monitor website rank, position and uptime in one place!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-191405</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 18 Sep 2009 06:03:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-191405</guid>
		<description>Hey Richy.. nice comparison table! You may also be interested in EZ Website Monitoring (http://www.ezwebsitemonitoring.com/) - it&#039;s kind of unique as it provides both uptime monitor and SEO tracking together in one service. Check it out if you have time and even sign up for the beta if you want to help it improve. We have 3 monitoring nodes at the moment and are adding more.. our goal is to have at least 10 monitoring nodes within 6 months.</description>
		<content:encoded><![CDATA[<p>Hey Richy.. nice comparison table! You may also be interested in EZ Website Monitoring (<a href="http://www.ezwebsitemonitoring.com/" rel="nofollow">http://www.ezwebsitemonitoring.com/</a>) &#8211; it&#8217;s kind of unique as it provides both uptime monitor and SEO tracking together in one service. Check it out if you have time and even sign up for the beta if you want to help it improve. We have 3 monitoring nodes at the moment and are adding more.. our goal is to have at least 10 monitoring nodes within 6 months.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richy C.</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-189897</link>
		<dc:creator>Richy C.</dc:creator>
		<pubDate>Sun, 17 May 2009 19:07:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-189897</guid>
		<description>I&#039;ve just heard about http://www.serverdensity.com/ - 10GBP/15USD per month per server with on server monitoring.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just heard about <a href="http://www.serverdensity.com/" rel="nofollow">http://www.serverdensity.com/</a> &#8211; 10GBP/15USD per month per server with on server monitoring.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richy C.</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-189434</link>
		<dc:creator>Richy C.</dc:creator>
		<pubDate>Mon, 16 Mar 2009 17:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-189434</guid>
		<description>Thanks for the correction Arun - I&#039;ve updated the table.

It is a shame that providers don&#039;t provide a simple &quot;comparison feature table&quot; showing exactly what they offer at what prices: this isn&#039;t a &quot;dig&quot; at your company, but just generally - some say &quot;We offer voice notifications&quot;: but no price indications, some just say &quot;Our monitoring network&quot; without the number of nodes - and some force you to sign up to find out basic pricing!</description>
		<content:encoded><![CDATA[<p>Thanks for the correction Arun &#8211; I&#8217;ve updated the table.</p>
<p>It is a shame that providers don&#8217;t provide a simple &#8220;comparison feature table&#8221; showing exactly what they offer at what prices: this isn&#8217;t a &#8220;dig&#8221; at your company, but just generally &#8211; some say &#8220;We offer voice notifications&#8221;: but no price indications, some just say &#8220;Our monitoring network&#8221; without the number of nodes &#8211; and some force you to sign up to find out basic pricing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arun</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-189433</link>
		<dc:creator>Arun</dc:creator>
		<pubDate>Mon, 16 Mar 2009 16:35:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-189433</guid>
		<description>Richy,

Nice list. I would like to point out the following corrections to the Site24x7 entry in the list.

- Number of monitoring nodes is 14.
- keyword checks is &#039;yes&#039;
- Unwanted text checking is &#039;yes&#039;
- Basic auth is &#039;yes&#039;

Arun
Site24x7</description>
		<content:encoded><![CDATA[<p>Richy,</p>
<p>Nice list. I would like to point out the following corrections to the Site24x7 entry in the list.</p>
<p>- Number of monitoring nodes is 14.<br />
- keyword checks is &#8216;yes&#8217;<br />
- Unwanted text checking is &#8216;yes&#8217;<br />
- Basic auth is &#8216;yes&#8217;</p>
<p>Arun<br />
Site24x7</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richy C.</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-189406</link>
		<dc:creator>Richy C.</dc:creator>
		<pubDate>Thu, 12 Mar 2009 21:20:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-189406</guid>
		<description>I&#039;ve also been told about http://www.ippatrol.co.uk/ .</description>
		<content:encoded><![CDATA[<p>I&#8217;ve also been told about <a href="http://www.ippatrol.co.uk/" rel="nofollow">http://www.ippatrol.co.uk/</a> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-189403</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 12 Mar 2009 16:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-189403</guid>
		<description>Take a look at Panopta (&lt;a href=&quot;http://www.panopta.com&quot; rel=&quot;nofollow&quot;&gt;www.panopta.com&lt;/a&gt;) - they have a number of the features you&#039;re looking for, in particular excellent outage verification.  We&#039;ve never had a false alert with them yet!</description>
		<content:encoded><![CDATA[<p>Take a look at Panopta (<a href="http://www.panopta.com" rel="nofollow">http://www.panopta.com</a>) &#8211; they have a number of the features you&#8217;re looking for, in particular excellent outage verification.  We&#8217;ve never had a false alert with them yet!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richy C.</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-189400</link>
		<dc:creator>Richy C.</dc:creator>
		<pubDate>Thu, 12 Mar 2009 12:09:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-189400</guid>
		<description>Killer features? Well, I would personally like:
* At least 2 checking nodes on different networks to avoid false positives (there&#039;s nothing worse than being woken up at 3am for a false alert)
* Ideally 1 node per continent/major backbone so we could view potential latency issues
* SMS and email alerts are a must
* Ideally customisable Twitter alerts (&quot;We&#039;ve just been notified that service X is done, we&#039;re looking at it&quot;) for customer reassurance
* Which then goes hand-in-hand with RSS, HTTP POST/RPC and public status pages
* Cheap (Alertra, whilst well known, is extremely expensive: Wormly seems to have an ideal price point
* Keyword monitoring (it&#039;s alright telling me if my page is just not reachable, but if it doesn&#039;t show text from my MySQL database, then it&#039;s broken...)

Hope it helps!</description>
		<content:encoded><![CDATA[<p>Killer features? Well, I would personally like:<br />
* At least 2 checking nodes on different networks to avoid false positives (there&#8217;s nothing worse than being woken up at 3am for a false alert)<br />
* Ideally 1 node per continent/major backbone so we could view potential latency issues<br />
* SMS and email alerts are a must<br />
* Ideally customisable Twitter alerts (&#8220;We&#8217;ve just been notified that service X is done, we&#8217;re looking at it&#8221;) for customer reassurance<br />
* Which then goes hand-in-hand with RSS, HTTP POST/RPC and public status pages<br />
* Cheap (Alertra, whilst well known, is extremely expensive: Wormly seems to have an ideal price point<br />
* Keyword monitoring (it&#8217;s alright telling me if my page is just not reachable, but if it doesn&#8217;t show text from my MySQL database, then it&#8217;s broken&#8230;)</p>
<p>Hope it helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-189398</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 12 Mar 2009 08:19:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-189398</guid>
		<description>Some good facts in this one as well - like the comparisons. We are contemplating launching a UK based service along these lines (with a few differences - but nothing earth shattering) - mainly because we already have the product ready from in-house use.

My last sweep of research showed that it was fairly pointless because the market space is quite chocca, and there are some good (and very cheap or even free) alternatives.. so curious as to what might be a killer feature.

Oh well. As ever - more market research required!</description>
		<content:encoded><![CDATA[<p>Some good facts in this one as well &#8211; like the comparisons. We are contemplating launching a UK based service along these lines (with a few differences &#8211; but nothing earth shattering) &#8211; mainly because we already have the product ready from in-house use.</p>
<p>My last sweep of research showed that it was fairly pointless because the market space is quite chocca, and there are some good (and very cheap or even free) alternatives.. so curious as to what might be a killer feature.</p>
<p>Oh well. As ever &#8211; more market research required!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe McDonald</title>
		<link>http://blog.rac.me.uk/2009/03/11/website-uptime-monitoring-systems/comment-page-1/#comment-189396</link>
		<dc:creator>Joe McDonald</dc:creator>
		<pubDate>Wed, 11 Mar 2009 23:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rac.me.uk/?p=1418#comment-189396</guid>
		<description>http://www.websitehawk.com is another one

as low as 1 minute interval
2 nodes
keyword checking - yes
unwanted text checking -yes
basic auth = yes
pop3/smtp/imap = yes
any alert mail/sms/etc =yes

3 free url monitors 
.50 a monitor for premium monitors</description>
		<content:encoded><![CDATA[<p><a href="http://www.websitehawk.com" rel="nofollow">http://www.websitehawk.com</a> is another one</p>
<p>as low as 1 minute interval<br />
2 nodes<br />
keyword checking &#8211; yes<br />
unwanted text checking -yes<br />
basic auth = yes<br />
pop3/smtp/imap = yes<br />
any alert mail/sms/etc =yes</p>
<p>3 free url monitors<br />
.50 a monitor for premium monitors</p>
]]></content:encoded>
	</item>
</channel>
</rss>

