<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Salesforce.com System Status and Alerts</title>
    <link>http://trust.salesforce.com</link>
    <description>Real-time updates from trust.salesforce.com on alerts, availability and system health</description>
    <pubDate>Tue, 21 May 2013 15:27:00 GMT</pubDate>
    <dc:date>2013-05-21T15:27:00Z</dc:date>
    <item>
      <title>Alert: [ NA2 ] The salesforce.com Technology Team has resolved the search performance degradation on the NA2 instance. The problem began at 13:00 UTC and was resolved as of 13:56 UTC. During this period customers on this instance may have experienced an inability to search for changed or newly created content but old content was fine throughout.</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>The problem was caused by a server hardware fault within the NA2 search tier. The faulty server has been taken offline for an emergency maintenance. The maintenance has completed and the search functionality has been fully restored.&#xD;
&#xD;
Actions to Prevent Future Incidents:&#xD;
The salesforce.com Technology Team -&#xD;
- Is investigating more effective methods to ensure that the search application is more resilient to these kind of faults.</description>
      <pubDate>Tue, 21 May 2013 15:27:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2013-05-21T15:27:00Z</dc:date>
    </item>
    <item>
      <title>Alert: [ NA2 ] On April 25 2013, the salesforce.com Technology Team observed a performance degradation issue affecting the NA2 instance.  The problem began at 22:14 UTC and was resolved by 22:16 UTC.  During this time, customers on the NA2 instance may have experienced slow performance or intermittent errors while accessing the Salesforce application.  Thank you for your continued business and patience during this situation.</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>The problem was caused by a hardware failure within the NA2 database tier.  Application requests were automatically rebalanced around the failure and further customer impact was minimized.  During the rebalancing process, database performance was impacted.&#xD;
 &#xD;
Actions to Prevent Future Incidents:&#xD;
The salesforce.com Technology Team -&#xD;
- Is working with our vendor to investigate and resolve the hardware failure&#xD;
- Is investigating ways to increase system resiliency and further mitigate customer impact</description>
      <pubDate>Thu, 25 Apr 2013 23:22:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2013-04-25T23:22:00Z</dc:date>
    </item>
    <item>
      <title>Alert: [ NA2 ] Detail: The salesforce.com Technology Team has resolved a performance degradation issue on the NA2 instance. The problem began on April 2, 2013 at 14:09 UTC and was resolved by 14:16 UTC. During this time, customers on the NA2 instance may have experienced slow performance or intermittent errors while using the Salesforce application. Thank you for your continued business and patience during this situation.</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>Root Cause: The problem was isolated to resource contention within the database tier.&#xD;
&#xD;
Actions to Prevent future incidents:&#xD;
The salesforce.com Technology Team -&#xD;
-Is investigating the root cause of the resource contention with our salesforce.com Technology Teams</description>
      <pubDate>Tue, 02 Apr 2013 16:13:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2013-04-02T16:13:00Z</dc:date>
    </item>
  </channel>
</rss>

