On May 21st, 2013 at 10:08 UTC customers on the CS10 instance experienced an inability to access or use the Salesforce application.

According the salesforce.com Technology Team:

The problem was isolated to a fault within our third party database application.

On May, 18, 2013, an intermittent latency issue affecting the  Rackspace Cloud Sites DFW1.WC2 PHP53-22 Cluster for 2,4 hours. The next day, on May 19, 2013,  rackspace repport another issue in the same datacenter for 12 hours. .

On May, 15, 2013 the North Europe sub-region compute service of Windows Azure was down. This issue affect availability of Virtual Machines (IaaS)  in the sub-region.

Microsoft did not give any information except:

The repair steps have been successfully executed and validated.

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.

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 reported last week.

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 normal Salesforce services were restored.

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.

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 not release any information about the cause of this issue and its restoration.  It is the 3rd time this year that we notice an issue on this service..

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 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.

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 operation failures.

No detailed explanation was given by Microsoft on the issues.