<?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>Fri, 17 May 2013 23:37:00 GMT</pubDate>
    <dc:date>2013-05-17T23:37:00Z</dc:date>
    <item>
      <title>Status Update: [ NA14 ] NA14 Performance Degradation - Resolved</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>The salesforce.com Technology Team has resolved the performance degradation issue on the NA14 instance. The problem began at 19:18 UTC and was resolved as of 19:49 UTC. During this time, customers may have experienced slow performance or intermittent errors on API transactions.&#xD;
&#xD;
Thank you for your continued business and patience during this situation.</description>
      <pubDate>Fri, 17 May 2013 20:25:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2013-05-17T20:25:00Z</dc:date>
    </item>
    <item>
      <title>Alert: [ NA14 ] On May 17 2013, the salesforce.com Technology Team observed a performance degradation affecting API transactions on the NA14 instance.  The problem began at 19:18 UTC and was resolved by 19:49 UTC.  During this time, some customers' API transactions with the Salesforce application may have experienced slow performance or intermittent errors.  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 resource exhaustion on the application servers used for API query caching.  The exhaustion was addressed and normal API performance was restored.&#xD;
 &#xD;
Actions to Prevent Future Incidents &#xD;
The salesforce.com Technology Team &#xD;
- Is adding capacity and enhancing the system configuration, to better manage resources and prevent a similar exhaustion in the future&#xD;
- Is making infrastructure improvements to more quickly detect and be resilient to this type of resource exhaustion</description>
      <pubDate>Fri, 17 May 2013 23:37:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2013-05-17T23:37:00Z</dc:date>
    </item>
    <item>
      <title>Alert: [ NA14 ] On March 25 2013, the salesforce.com Technology Team observed a performance degradation issue affecing the NA14 instance.  The problem began at 16:37 UTC and was resolved by 16:45 UTC. During this time, customers on the NA14 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 resource contention within the NA14 database tier.  The contention cleared and normal performance was restored.&#xD;
 &#xD;
Actions to Prevent Future Incidents:&#xD;
The salesforce.com Technology Team -&#xD;
- Is continuing to work with our database vendor to more efficiently manage resources within the databse tier</description>
      <pubDate>Mon, 25 Mar 2013 21:45:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2013-03-25T21:45:00Z</dc:date>
    </item>
  </channel>
</rss>

