<?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>IWGCR</title>
	<atom:link href="http://iwgcr.org//feed/" rel="self" type="application/rss+xml" />
	<link>http://iwgcr.org</link>
	<description>International Working Group on Cloud Computing Resiliency</description>
	<lastBuildDate>Tue, 14 May 2013 14:10:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Storage fault at Salesforce</title>
		<link>http://iwgcr.org/storage-fault-at-salesforce/</link>
		<comments>http://iwgcr.org/storage-fault-at-salesforce/#comments</comments>
		<pubDate>Tue, 14 May 2013 14:10:55 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[Salesforce]]></category>
		<category><![CDATA[Storage]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1306</guid>
		<description><![CDATA[<p>On May 12, 2013, from 11:00 UTC to 12:47 UTC the NA11 instance of Salesforce.com was disrupted. According the salesforce.com Technology Team: an unexpected fault within the storage tier. The root cause of the fault is, at this time, still under investigation. Date Service Duration Critical Data Lost 2013-05-12 Salesforce 1.95 hour no &#160;</p><p>The post <a href="http://iwgcr.org/storage-fault-at-salesforce/">Storage fault at Salesforce</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>On May 12, 2013, from 11:00 UTC to 12:47 UTC the NA11 instance of Salesforce.com was disrupted. According the salesforce.com Technology Team:</p>
<blockquote><p>an unexpected fault within the storage tier. The root cause of the fault is, at this time, still under investigation.</p></blockquote>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-05-12</td>
<td width="128">Salesforce</td>
<td width="111">1.95 hour</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>The post <a href="http://iwgcr.org/storage-fault-at-salesforce/">Storage fault at Salesforce</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/storage-fault-at-salesforce/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gmail 502</title>
		<link>http://iwgcr.org/gmail-502/</link>
		<comments>http://iwgcr.org/gmail-502/#comments</comments>
		<pubDate>Fri, 10 May 2013 15:21:29 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[Frustrated users]]></category>
		<category><![CDATA[Gmail]]></category>
		<category><![CDATA[Google Apps]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1302</guid>
		<description><![CDATA[<p>On May, 8 2013, a small subset of  users residing in India and the Middle-East region was unable to access Gmail. The nature of this issue was sporadic, users were experiencing 502 errors when accessing Gmail. The issue has started at 00:30:00 PDT and was confirmed as resolved at 01:15:00 PDT. A 502 error was previously [...]</p><p>The post <a href="http://iwgcr.org/gmail-502/">Gmail 502</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>On May, 8 2013, <em>a small subset of  users residing in India and the Middle-East region </em>was unable to access Gmail.</p>
<blockquote><p>The nature of this issue was sporadic, users were experiencing 502 errors when accessing Gmail. The issue has started at 00:30:00 PDT and was confirmed as resolved at 01:15:00 PDT.</p></blockquote>
<p>A 502 error was <a href="http://iwgcr.org/bad-gateway-for-%ef%bb%bf%ef%bb%bfgmail/">previously reported last week</a>.</p>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-05-08</td>
<td width="128">Google Apps</td>
<td width="111">45 minutes</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>The post <a href="http://iwgcr.org/gmail-502/">Gmail 502</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/gmail-502/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Salesforce CS9 disruption</title>
		<link>http://iwgcr.org/salesforce-cs9-disruption/</link>
		<comments>http://iwgcr.org/salesforce-cs9-disruption/#comments</comments>
		<pubDate>Fri, 10 May 2013 15:13:17 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[Frustrated users]]></category>
		<category><![CDATA[Salesforce]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1300</guid>
		<description><![CDATA[<p>This May, 04, 2013 the Salesforce;com CS9 instance was disrupted from 10h48 UTC to 11:57 UTC. According the salesforce.com Technology Team The problem was caused by a connectivity issue within the CS9 database tier. This issue subsequently caused the database to fault and become unresponsive. The connectivity issue was resolved, the database was brought back online and [...]</p><p>The post <a href="http://iwgcr.org/salesforce-cs9-disruption/">Salesforce CS9 disruption</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>This May, 04, 2013 the Salesforce;com CS9 instance was disrupted from 10h48 UTC to 11:57 UTC.</p>
<p>According the salesforce.com Technology Team</p>
<blockquote><p>The problem was caused by a connectivity issue within the CS9 database tier. This issue subsequently caused the database to fault and become unresponsive. The connectivity issue was resolved, the database was brought back online and normal Salesforce services were restored.</p></blockquote>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-05-04</td>
<td width="128">Salesforce</td>
<td width="111">1,1 hour</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>The post <a href="http://iwgcr.org/salesforce-cs9-disruption/">Salesforce CS9 disruption</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/salesforce-cs9-disruption/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bad Gateway for ﻿﻿Gmail</title>
		<link>http://iwgcr.org/bad-gateway-for-%ef%bb%bf%ef%bb%bfgmail/</link>
		<comments>http://iwgcr.org/bad-gateway-for-%ef%bb%bf%ef%bb%bfgmail/#comments</comments>
		<pubDate>Mon, 06 May 2013 14:14:34 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[Google Apps]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1297</guid>
		<description><![CDATA[<p>Last May, 02, 2013 Gmail users were experiencing 502 errors and latency when accessing email. This 40 minutes of service disruption has not been explained in detail by Google engineers. Date Service Duration Critical Data Lost 2013-05-02 Google Apps 40 minutes no &#160;</p><p>The post <a href="http://iwgcr.org/bad-gateway-for-%ef%bb%bf%ef%bb%bfgmail/">Bad Gateway for ﻿﻿Gmail</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>Last May, 02, 2013 Gmail users were experiencing 502 errors and latency when accessing email.</p>
<p>This 40 minutes of service disruption has not been explained in detail by Google engineers.</p>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-05-02</td>
<td width="128">Google Apps</td>
<td width="111">40 minutes</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>The post <a href="http://iwgcr.org/bad-gateway-for-%ef%bb%bf%ef%bb%bfgmail/">Bad Gateway for ﻿﻿Gmail</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/bad-gateway-for-%ef%bb%bf%ef%bb%bfgmail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Worldwide Azure Access Control 2.0 issue</title>
		<link>http://iwgcr.org/worldwide-azure-access-control-2-0-issue/</link>
		<comments>http://iwgcr.org/worldwide-azure-access-control-2-0-issue/#comments</comments>
		<pubDate>Thu, 25 Apr 2013 10:51:08 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[Microsoft Azure]]></category>
		<category><![CDATA[WAAD]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1291</guid>
		<description><![CDATA[<p>This April 23, 2013 from 4:40 PM UTC to 8:22 PM UTC worldwide Windows Azure Customers experienced a issue on the Access Control 2.0. This service is critical for customer that use it to authenticating and authorizing their users to gain access to their web applications and services hosted in Azure. Microsft Azure team did [...]</p><p>The post <a href="http://iwgcr.org/worldwide-azure-access-control-2-0-issue/">Worldwide Azure Access Control 2.0 issue</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p style="text-align: justify;"><a href="http://iwgcr.org/wp-content/uploads/2012/07/windows-azure.jpg"><img class="alignright  wp-image-831" style="margin-left: 10px; margin-right: 10px;" alt="windows-azure" src="http://iwgcr.org/wp-content/uploads/2012/07/windows-azure.jpg" width="166" height="114" /></a>This April 23, 2013 from 4:40 PM UTC to 8:22 PM UTC worldwide Windows Azure Customers experienced a issue on the <a href="http://msdn.microsoft.com/en-us/library/hh147631.aspx">Access Control 2.0</a>. This service is critical for customer that use it to authenticating and authorizing their users to gain access to their web applications and services hosted in Azure.</p>
<p style="text-align: justify;">Microsft Azure team did not release any information about the cause of this issue and its restoration.  <a href="http://iwgcr.org/tag/waad/">It is the 3rd time this year that we notice an issue on this service.</a>.</p>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-04-23</td>
<td width="128">Windows Azure</td>
<td width="111">4 hours</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>The post <a href="http://iwgcr.org/worldwide-azure-access-control-2-0-issue/">Worldwide Azure Access Control 2.0 issue</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/worldwide-azure-access-control-2-0-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Salesforce.com EU0 search issue</title>
		<link>http://iwgcr.org/salesforce-com-eu0-search-issue/</link>
		<comments>http://iwgcr.org/salesforce-com-eu0-search-issue/#comments</comments>
		<pubDate>Tue, 23 Apr 2013 07:06:54 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[Frustrated users]]></category>
		<category><![CDATA[Salesforce]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1288</guid>
		<description><![CDATA[<p>This April 22, 2013 at 09:05 UTC the EU0 instance of salesforce.com users were unable to search for newly created or updated records. According the salesforce.com Technology Team : The problem was caused by resource contention on the EU0 Search tier. In response to the resource contention, a subset of Search queries were automatically routed to a [...]</p><p>The post <a href="http://iwgcr.org/salesforce-com-eu0-search-issue/">Salesforce.com EU0 search issue</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>This April 22, 2013 at 09:05 UTC the EU0 instance of salesforce.com users were unable to search for newly created or updated records.</p>
<p>According the salesforce.com Technology Team :</p>
<blockquote><p>The problem was caused by resource contention on the EU0 Search tier. In response to the resource contention, a subset of Search queries were automatically routed to a secondary Search method which does not perform as well as the primary Search method. The resource contention was cleared and normal Search performance was restored.</p></blockquote>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-04-22</td>
<td width="128">Salesforce</td>
<td width="111">30 minutes</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>The post <a href="http://iwgcr.org/salesforce-com-eu0-search-issue/">Salesforce.com EU0 search issue</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/salesforce-com-eu0-search-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Difficult week for Azure SQL Database﻿﻿ Service</title>
		<link>http://iwgcr.org/difficult-week-for-azure-sql-database%ef%bb%bf%ef%bb%bf-service/</link>
		<comments>http://iwgcr.org/difficult-week-for-azure-sql-database%ef%bb%bf%ef%bb%bf-service/#comments</comments>
		<pubDate>Fri, 19 Apr 2013 12:15:40 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[Microsoft Azure]]></category>
		<category><![CDATA[Software bug]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1286</guid>
		<description><![CDATA[<p>On April 13, from 8:02 PM UTC to 10:41 PM UTC the Azure SQL Database in the West US sub-region experiencing intermittent failures with Create\Delete\Alter database operations. This April 16, from 10:08 PM UTC to April,17 9:30 AM UTC the SQL Azure Windows SQL Database East Asia sub region has suffered a software bug which resulted in delete server [...]</p><p>The post <a href="http://iwgcr.org/difficult-week-for-azure-sql-database%ef%bb%bf%ef%bb%bf-service/">Difficult week for Azure SQL Database﻿﻿ Service</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>On April 13, from 8:02 PM UTC to 10:41 PM UTC the Azure SQL Database in the West US sub-region experiencing intermittent failures with Create\Delete\Alter database operations.</p>
<p>This April 16, from 10:08 PM UTC to April,17 9:30 AM UTC the SQL Azure Windows SQL Database East Asia sub region has suffered a software bug which resulted in delete server operation failures.</p>
<p>No detailed explanation was given by Microsoft on the issues.</p>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-04-13</td>
<td width="128">Windows Azure</td>
<td width="111">3 hours</td>
<td width="139">no</td>
</tr>
<tr>
<td>2013-04-16</td>
<td width="128">Windows Azure</td>
<td width="111">11,5 hours</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>The post <a href="http://iwgcr.org/difficult-week-for-azure-sql-database%ef%bb%bf%ef%bb%bf-service/">Difficult week for Azure SQL Database﻿﻿ Service</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/difficult-week-for-azure-sql-database%ef%bb%bf%ef%bb%bf-service/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Mail, Groups, Drive, Documents, Spreadsheets, Presentations and API down</title>
		<link>http://iwgcr.org/google-mail-groups-drive-documents-spreadsheets-presentations-and-api-down/</link>
		<comments>http://iwgcr.org/google-mail-groups-drive-documents-spreadsheets-presentations-and-api-down/#comments</comments>
		<pubDate>Wed, 17 Apr 2013 15:51:53 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[Frustrated users]]></category>
		<category><![CDATA[Google Apps]]></category>
		<category><![CDATA[Outage]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1282</guid>
		<description><![CDATA[<p>This April 17, 2013 many google services have suffered a service disruption at same time. Google Mail issue was noticed at 2:58 PM UTC+2 and restored at 4:52 PM UTC+2. Google said it have affected 0.007% of the Google Mail user base. Google Group issue was noticed at 3:51 PM UTC+2 and restored at 5:15 [...]</p><p>The post <a href="http://iwgcr.org/google-mail-groups-drive-documents-spreadsheets-presentations-and-api-down/">Google Mail, Groups, Drive, Documents, Spreadsheets, Presentations and API down</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p style="text-align: justify;"><a href="http://iwgcr.org/wp-content/uploads/2012/07/GoogleAppslogo-e1343656872128.jpg"><img class="alignright size-full wp-image-871" style="margin-left: 10px; margin-right: 10px;" alt="GoogleAppslogo" src="http://iwgcr.org/wp-content/uploads/2012/07/GoogleAppslogo-e1343656872128.jpg" width="200" height="100" /></a>This April 17, 2013 many google services have suffered a service disruption at same time.</p>
<ul style="text-align: justify;">
<li>Google Mail issue was noticed at 2:58 PM UTC+2 and restored at 4:52 PM UTC+2. Google said it have <a href="http://www.google.com/appsstatus#hl=en&amp;v=issue&amp;ts=1366235999000&amp;iid=f1583d7e731ba748b2c0ff847868a813">affected 0.007% of the Google Mail user base</a>.</li>
<li>Google Group issue was noticed at 3:51 PM UTC+2 and restored at 5:15 PM UTC+2. Google said it have <a href="http://www.google.com/appsstatus#hl=en&amp;v=issue&amp;ts=1366235999000&amp;iid=c05dbbaf6b5d79b3b394e9e9b10655ad">affected 1% of the Google Groups user base</a>.</li>
<li>Google Drive issue was noticed at 3:01 PM UTC+2 and restored at 4:45 PM UTC+2. <a href="http://www.google.com/appsstatus#hl=en&amp;v=issue&amp;ts=1366235999000&amp;iid=369723584758ad9cdfd010ac44c8272e">No information was given by Google on the users impact</a>.</li>
<li>Google <a href="http://www.google.com/appsstatus#hl=en&amp;v=issue&amp;ts=1366235999000&amp;iid=0769c60b5ebb6b07431940fd6886c933">Documents</a>, <a href="http://www.google.com/appsstatus#hl=en&amp;v=issue&amp;ts=1366235999000&amp;iid=507416a9498c14c17543636abb3164ef">Spreadsheets</a> and <a href="http://www.google.com/appsstatus#hl=en&amp;v=issue&amp;ts=1366235999000&amp;iid=b58e2d4c13ff617d5bd22a13a90b799a">Presentations</a> issue was noticed at 3:11 PM and restored at 4:48 PM UTC+2. No information was given by Google on the users impact.</li>
</ul>
<p style="text-align: justify;">What is shared by all theses services? Maybe the &#8220;Admin control panel / API&#8221; that <a href="http://www.google.com/appsstatus#hl=en&amp;v=issue&amp;ts=1366235999000&amp;iid=bb886daf880ab16f9a8b5f8bbe2f34b0">suffred an outage</a> from 2:20 PM UTC+2 to 4:59 PM UTC+2.</p>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-04-17</td>
<td width="128">Google Apps</td>
<td width="111">3 hours</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>The post <a href="http://iwgcr.org/google-mail-groups-drive-documents-spreadsheets-presentations-and-api-down/">Google Mail, Groups, Drive, Documents, Spreadsheets, Presentations and API down</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/google-mail-groups-drive-documents-spreadsheets-presentations-and-api-down/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>No iMessage or FaceTime for 5 hours</title>
		<link>http://iwgcr.org/no-imessage-or-facetime-for-5-hours/</link>
		<comments>http://iwgcr.org/no-imessage-or-facetime-for-5-hours/#comments</comments>
		<pubDate>Wed, 10 Apr 2013 08:10:53 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[Frustrated users]]></category>
		<category><![CDATA[Messaging]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1277</guid>
		<description><![CDATA[<p>iMessage is an instant messenger service developed by Apple Inc. for iOS and OS X Mountain Lion.  The iMessage protocol is based  on Apple push notifications (APNS). FaceTime is a videotelephony software application and related protocol developed by Apple Inc. Both dependent of a Keep-Alive connection with the Apple servers. On April 09, 2013 9:11 PM UTC+1, Apple users were unable [...]</p><p>The post <a href="http://iwgcr.org/no-imessage-or-facetime-for-5-hours/">No iMessage or FaceTime for 5 hours</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p style="text-align: justify;"><a href="http://en.wikipedia.org/wiki/IMessage"><img class="alignright" style="margin-left: 10px; margin-right: 10px;" alt="iMessage" src="http://upload.wikimedia.org/wikipedia/en/thumb/d/d9/IMessageScreenshot.png/200px-IMessageScreenshot.png" width="112" height="168" />iMessage</a> is an instant messenger service developed by Apple Inc. for iOS and OS X Mountain Lion.  The iMessage protocol is based  on Apple push notifications (APNS). <a href="http://en.wikipedia.org/wiki/FaceTime">FaceTime</a> is a videotelephony software application and related protocol developed by Apple Inc.</p>
<p style="text-align: justify;">Both dependent of a Keep-Alive connection with the Apple servers.</p>
<p style="text-align: justify;">On April 09, 2013 9:11 PM UTC+1, Apple users were unable to place FaceTime calls and use iMessage until the April 10, 2013 2:20 AM UTC+1<br />
No explanation was given by Apple about the outage.</p>
<p>(<a href="http://gigaom.com/2013/04/09/the-multihour-imessage-outage-todays-that-is-continues/">source</a>)</p>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-04-09</td>
<td width="128">Apple iMessage</td>
<td width="111">5 hours</td>
<td width="139">no</td>
</tr>
<tr>
<td>2013-04-09</td>
<td width="128">Apple FaceTime</td>
<td width="111">5 hours</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>The post <a href="http://iwgcr.org/no-imessage-or-facetime-for-5-hours/">No iMessage or FaceTime for 5 hours</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/no-imessage-or-facetime-for-5-hours/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Azure Compute Service Interruption</title>
		<link>http://iwgcr.org/azure-compute-service-interruption/</link>
		<comments>http://iwgcr.org/azure-compute-service-interruption/#comments</comments>
		<pubDate>Tue, 09 Apr 2013 13:50:02 +0000</pubDate>
		<dc:creator>iwgcr</dc:creator>
				<category><![CDATA[Downtime]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[Microsoft Azure]]></category>

		<guid isPermaLink="false">http://iwgcr.org/?p=1274</guid>
		<description><![CDATA[<p>On April 03, 2013 the Compute service of the Windows Azure East Asia sub-region has suffred an interruption from  03:33 AM UTC to 4:16 AM UTC. No explanation was given by Microsoft about this interruption. Date Service Duration Critical Data Lost 2013-04-03 Windows Azure 1 hour no &#160;</p><p>The post <a href="http://iwgcr.org/azure-compute-service-interruption/">Azure Compute Service Interruption</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>On April 03, 2013 the Compute service of the Windows Azure East Asia sub-region has suffred an interruption from  03:33 AM UTC to 4:16 AM UTC.</p>
<p>No explanation was given by Microsoft about this interruption.</p>
<div>
<table border="1" cellpadding="0">
<tbody>
<tr>
<td>
<p align="center"><strong>Date</strong></p>
</td>
<td width="128">
<p align="center"><strong>Service</strong></p>
</td>
<td width="111">
<p align="center"><strong>Duration</strong></p>
</td>
<td width="139">
<p align="center"><strong>Critical Data Lost</strong></p>
</td>
</tr>
<tr>
<td>2013-04-03</td>
<td width="128">Windows Azure</td>
<td width="111">1 hour</td>
<td width="139">no</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
</div>
<p>The post <a href="http://iwgcr.org/azure-compute-service-interruption/">Azure Compute Service Interruption</a> appeared first on <a href="http://iwgcr.org">IWGCR</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://iwgcr.org/azure-compute-service-interruption/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
