<?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>Sun, 28 Apr 2013 00:00:00 GMT</pubDate>
    <dc:date>2013-04-28T00:00:00Z</dc:date>
    <item>
      <title>Alert: [ EU1 NA8 NA9 CS7 CS8 CS14 ] The salesforce.com Technology Team resolved a performance degradation affecting the NA8, NA9, EU1, CS7, CS8 and CS14 instances. The problem began on April 28, 2013 at 07:22 UTC and was resolved at 16:09 UTC. During this time customers may have experienced problems receiving emails from the affected instances and failures while accessing external services from the Salesforce.com application. Thank you for your continued business and patience during this situation.</title>
      <link>http://trust.salesforce.com/trust/status</link>
      <description>On April 28th at approximately 12:00 AM PST, the salesforce.com Technology team performed a scheduled Load Balancer change that involved upgrading a subset of SSL certificates. This change went through the standard change management process and was executed within the planned maintenance window. While the intended certificate change succeeded as expected, there was an additional change, scheduled for future purposes, that was inadvertently executed on the same load balancers. The monitoring system quickly alerted the salesforce.com team and the unintended change was immediately rolled back. After the rollback, our monitoring system and verification with our support team indicated that full service had been restored.&#xD;
&#xD;
The broader impact to the outbound proxy service was not immediately evident.  A subsequent alert notified the salesforce.com Technology team of additional impact, and the team immediately began troubleshooting efforts. Through these efforts, an incorrect configuration was found on one of the load balancers that was routing outbound proxy traffic to a non-existent destination. Through our investigation, the root cause of the service disruption was identified as  a bug in the rollback commands. The salesforce.com Technology team removed the incorrect configuration and the service was fully restored at 9:00 AM PST.&#xD;
&#xD;
To prevent this from occurring again, the team has identified a number of preventive and mitigating steps, that include faster diagnosis, more expeditious internal and vendor triaging, and improving the review of change plans.</description>
      <pubDate>Sun, 28 Apr 2013 00:00:00 GMT</pubDate>
      <guid>http://trust.salesforce.com/trust/status</guid>
      <dc:date>2013-04-28T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

