Over a million developers have joined DZone.

Uptime Report for My Live Windows Azure Web Site: June 2013

DZone's Guide to

Uptime Report for My Live Windows Azure Web Site: June 2013

· Cloud Zone ·
Free Resource

Create a continuous deployment pipeline with open source tools. Watch the screencast.

My Android MiniPCs and TVBoxes blog runs WordPress on WebMatrix with Super Cache on Windows Azure Web Site (WAWS) Preview and ClearDB’s MySQL database (Venus plan) in Microsoft’s West U.S. (Bay Area) data center. Service Level Agreements aren’t applicable to the Web Services Preview; only sites with two or more Reserved Web Site instances qualify for the usual 99.95% uptime SLA.

I use Windows Live Writer to author posts that provide technical details of low-cost MiniPCs with HDMI outputs running Android JellyBean 4.1+. The site emphases high-definition 1080p video recording and rendition.


The site commenced operation on 4/25/2013. To improve response time, I implemented WordPress Super Cache on May 15, 2013.

Here’s Pingdom’s summary report for June 2013:


Pingdom’s graphical Uptime report (in Downtime mode) for June 2013:


And here’s their Response Time report for the same period:


Note: I have no explanation for the difference in reported response time.

I plan to report and log uptime values monthly with pages similar to OakLeaf Systems’Uptime Report for my Live OakLeaf Systems Azure Table Services Sample Project posts, which has more that two full years of uptime and response time data as of June 2013.

Month Year Uptime Downtime Outages Response Time
June 2013 99.34% 04:45:00 30 2,431 ms
May 2013 99.58% 03:05:00 32 2,706 ms

As noted above, Windows Azure Web Sites are in preview mode as of June 2013 so the usual 99.98% uptime Service Level Agreement (SLA) doesn’t apply.

Leverage your CDN to optimize + secure your cloud infrastructure. Here's how.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}