<?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>Wed, 16 May 2012 07:00:00 GMT</pubDate>
    <dc:date>2012-05-16T07:00:00Z</dc:date>
    <item>
      <title>Alert: [na14] The salesforce.com Technology Team resolved a performance degradation issue affecting the NA14 instance.  The problem began on March 20, 2012 at 11:52 UTC and performance returned to normal by 12:10 UTC.  The problem resurfaced at 15:43 UTC and was resolved by 15:47 UTC.  During these times, customers on the NA14 instance may have experienced slow performance while using the application.  We apologize for any inconvenience this may have caused you.</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>The problem was caused by a configuration issue in our network tier.  This resulted in excessive traffic on NA14 network devices, degrading performance for other communications including customer requests.
&lt;p&gt;
Actions to Prevent Future Incidents -
The salesforce.com Technology Team -
- Is investigating recent infrastructure changes which may have introduced the configuration issue</description>
      <pubDate>Wed, 21 Mar 2012 00:10:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2012-03-21T00:10:00Z</dc:date>
    </item>
    <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 15:43 UTC and was resolved as of 15:47 UTC. Users on this instance may have experienced slow performance when using the application.  We apologize for any inconvenience this may have caused you.</description>
      <pubDate>Tue, 20 Mar 2012 15:50:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2012-03-20T15:50:00Z</dc:date>
    </item>
    <item>
      <title>Status Update: [na14] NA14  Performance Degradation</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>The Salesforce.com Technology Team is working to isolate a performance degradation issue on the NA14 instance. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.</description>
      <pubDate>Tue, 20 Mar 2012 15:45:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2012-03-20T15:45:00Z</dc:date>
    </item>
    <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 11.50 UTC and was resolved as of 12.10 UTC. We apologize for any inconvenience this may have caused you.</description>
      <pubDate>Tue, 20 Mar 2012 12:19:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2012-03-20T12:19:00Z</dc:date>
    </item>
    <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 11.50 UTC and was resolved as of 12.10 UTC. We apologize for any inconvenience this may have caused you.</description>
      <pubDate>Tue, 20 Mar 2012 12:00:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2012-03-20T12:00:00Z</dc:date>
    </item>
    <item>
      <title>Alert: [na14] On February 24, 2012 the salesforce.com Technology Team resolved a performance degradation impacting the NA14 instance. The problem began at 5:09:00 UTC and was resolved by 12:07:00 UTC. During this time, some customers may have experienced an inability to run Salesforce Object Query Language (SOQL) queries that involve aliases. We apologize for any inconvenience this may have caused.</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>The problem was caused by an unexpected fault in the application tier.  The fault was introduced during a routine application update, which then caused SOQL queries involving aliases to return an error despite being valid queries.  The update was rolled back after the issue was discovered, which removed the fault.  

&lt;b&gt;Actions to Prevent Future Incidents:&lt;/b&gt;
The salesforce.com Technology Team -
- has identified and corrected the fault in the application update.
- is updating testing procedures to better identify these types of issues.</description>
      <pubDate>Fri, 24 Feb 2012 09:05:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2012-02-24T09:05:00Z</dc:date>
    </item>
    <item>
      <title>Alert: [na14] On February 24, 2012 the salesforce.com Technology Team resolved a performance degradation impacting the NA14 instance. The problem began at 5:09:00 UTC and was resolved by 12:07:00 UTC. During this time, some customers may have experienced an inability to run Salesforce Object Query Language (SOQL) queries that involve aliases. We apologize for any inconvenience this may have caused.</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>The problem was caused by an unexpected fault in the application tier.  The fault was introduced during a routine application update, which then caused SOQL queries involving aliases to return an error despite being valid queries.  The update was rolled back after the issue was discovered, which removed the fault.  

&lt;b&gt;Actions to Prevent Future Incidents:&lt;/b&gt;
The salesforce.com Technology Team -
- has identified and corrected the fault in the application update.
- is updating testing procedures to better identify these types of issues.</description>
      <pubDate>Thu, 23 Feb 2012 09:05:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2012-02-23T09:05:00Z</dc:date>
    </item>
    <item>
      <title>Status Update: [na14] Spring 12 NA14 Release ~ Complete</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>All upgrade activities for the NA14 instance are now complete and all features for the Spring '12 release have now been made available for your organization.</description>
      <pubDate>Sat, 11 Feb 2012 08:38:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2012-02-11T08:38:00Z</dc:date>
    </item>
    <item>
      <title>Status Update: [na14] NA14 Scheduled Maintenance Complete</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>The scheduled maintenance for the NA14 instances is complete at this time and all users should be able to access the instance normally. We apologize for any inconvenience caused by this maintenance.</description>
      <pubDate>Sun, 18 Dec 2011 05:32:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2011-12-18T05:32:00Z</dc:date>
    </item>
    <item>
      <title>Alert: [na14] On December 3, 2011 beginning at 21:00 UTC, the instance activation of the new NA14 instance went beyond its scheduled window.  The maintenance activity eventually completed and service was initiated on December 4, 2011 at 00:00 UTC. We apologize for any inconvenience this may have caused you.</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>The maintenance activity consisted of migrating the AP1 instance from our Singapore to Tokyo datacenter, as well as moving a subset of AP1 customers to the new NA14 instance in our Washington, DC datacenter.  The storage tier operations required to prepare for this combination of actions did not complete within the forecasted time, delaying portions of the maintenance activity.&lt;p&gt;&lt;/p&gt;&lt;b&gt;Actions to Prevent Future Incidents:&lt;/b&gt;
The salesforce.com Technology Team is:
-Reviewing the storage procedures to determine why storage operations took longer than estimated.</description>
      <pubDate>Sun, 04 Dec 2011 00:00:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2011-12-04T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>


