March 2010 Uptime Reports for OakLeaf Azure Test Harness Running in the South Central US Data Center

Update 4/3/2010: Pingdom’s monthly report shows 10 minutes of downtime. See below.

Update 4/8/2010: Mon.itor.us report for the week of 3/29 to 4/4/2010 shows two outages totaling 10 minutes.

First the good news: For the second month in a row, Mon.itor.us reported 100% uptime for the live OakLeaf Systems Azure Table Services Sample Project during an entire month. Better yet, this month Pingdom showed no downtime, either.

Following are four weekly reports for March 2010:

I’ll add the fifth report (for 3/29 to 3/31/2010) when Mon.itor.us sends it and Pingdom’s monthly report when I receive it. I received no downtime alerts earlier this week, so I’m confident that there was no downtime from 3/29 to 3/31/2010.

The bad news is that Pingdom listed two outages totaling 10 minutes in their monthly report that weren’t reported by PingdomAlert e-mails:

More bad news is that both mon.itor.us and Pingdom reported an outage on early 4/2/2010:

Again, the reported downtime duration differs, about 9 minutes by mon.itor.us and 25 minutes by Pingdom.

Update 4/8/2010: Mon.itor.us report for the week of 3/29 to 4/4/2010 shows the outages reported in the preceding Problem Alert:

There was no report of problems on 4/2/2010 in the Windows Azure Platform’s Service Dashboard:

As mentioned in previous posts in this series, only one instance of the test harness is running so Microsoft’s service-level agreement (SLA), which requires a minimum of two Windows Azure instances to become effective, doesn’t apply.

Technorati Tags: Windows Azure,Uptime Reports,mon.itor.us,Pingdom,Service Level Agreements,SLAs,Cloud Computing