Salesforce.com System Status and Alerts

Status Update: [cs13] Summer 12 CS13 Release -complete

Sat, 12 May 2012 12:35:00 GMT

All upgrade activities for the CS13 instance are now complete and all features for the Summer '12 release have now been made available for your organization.

Status Update: [cs13] Summer 12 CS13/CS14 Release -update

Sat, 12 May 2012 05:05:00 GMT

The Summer '12 release is now live for the CS13/CS14 instance. The CS13/CS14 should be generally available as we continue to perform upgrade activities. We will update Trust once these activities are complete. NOTE: Refreshing your sandbox may change the instance on which your sandbox resides. For more details please reference the solution "Why does my instance change whenever I refresh my sandbox?" in the Help & Training.

Status Update: [cs13] Summer 12 CS13/CS14 Release - start

Sat, 12 May 2012 05:00:00 GMT

The scheduled upgrade for CS13/CS14 is about to begin. During this period the salesforce.com service is expected to be generally available. Your organization should expect to experience a disruption of up to five (5) minutes during this timeframe. We appreciate your patience while we update this instance to Summer '12

Alert: [cs13] On April 8, 2012 starting at 05:01 UTC, customers on the NA0, NA3, NA4, EU0, CS2, CS4, and CS13 instances experienced degraded performance and/or an inability to use Force.com Sites functionality. The salesforce.com Technology Team started with a systematic troubleshooting approach to isolate and eliminate the potential cause and services were restored by 07:49 UTC.

Sun, 08 Apr 2012 00:49:00 GMT

The issue was caused by a fault on the proxy tier shared by the impacted instances. Troubleshooting performed during the incident did not identify the specific cause of the problem. The problem was cleared by restarting the proxy application on all members of the proxy tier.

Alert: [cs13] Detail: The salesforce.com Technology Team resolved a performance degradation issue affecting the CS13 instance. The problem began on March 26, 2012 at 19:12 UTC and was resolved by 20:00 UTC. During this time, customers on the CS13 instance may have experienced slow performance while using the Salesforce application.

Tue, 27 Mar 2012 02:35:00 GMT

The problem was isolated to a resource contention within the CS13 storage tier. It was resolved by suspending back-end storage operations and database processes. Suspending these processes does not affect any customer requests.
At salesforce.com, our top priority is to ensure your success. We are currently focused on resolving this issue as well as preventing any recurrences. We thank you for your continued patience.
Actions to Prevent Future Incidents - The salesforce.com Technology Team - - Is reviewing the configuration of the back-end processes for improvements

Status Update: [cs13] CS13 Performance Degradation - Resolved

Wed, 21 Mar 2012 17:55:00 GMT

The salesforce.com Technology Team has resolved the performance degradation issue on the CS13 instance. The problem began at 10.36 UTC and was resolved as of 10.38 UTC. We apologize for any inconvenience this may have caused you.

Alert: [cs13] The salesforce.com Technology Team resolved a performance degradation issue affecting the CS13 instance. The problem began on March 21, 2012 at 10:36 UTC and performance returned to normal by 10:38 UTC. T During these times, customers on the CS13 instance may have experienced slow performance while using the application. We apologize for any inconvenience this may have caused you.

Wed, 21 Mar 2012 13:34:00 GMT

The problem was caused by a failure to open a system file in our database tier which resulted in a build up of sessions causing the incident. Actions to Prevent Future Incidents - The salesforce.com Technology Team - - Is investigating the reasons for the database's failure to access this system file

Alert: [cs13] On 16th March starting at 13.45 UTC, the salesforce.com Technology team became aware of performance degradation affecting application performance for the NA0 / NA3 / NA4 / EU0 / CS2 / CS4 / CS13 instances. The problem was isolated to a non-performant network availability enhancement, and this was resolved by 13.46 UTC 16th March. We apologize for any inconvenience this may have caused you.

Fri, 16 Mar 2012 16:38:00 GMT

Non-performant transit provider The salesforce.com Technology Team - - will review all aspects of the test to ensure non-performant elements are addressed.

Alert: [cs13] On February 24, 2012 the salesforce.com Technology Team resolved a performance degradation impacting the CS13 instance. The problem began at 9:34:00 UTC and was resolved by 14:14: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.

Fri, 24 Feb 2012 09:05:00 GMT

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. Actions to Prevent Future Incidents: 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.

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Fri, 10 Feb 2012 03:39:00 GMT

The problem is due to an unexpected fault within the new framework for Time Based Workflow introduced in the Spring '12 Release. Temporary workarounds were implemented to improve service for impacted customers, followed by application update that resolved the root issue. Actions to Prevent Future Incidents: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Thu, 09 Feb 2012 03:37:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Wed, 08 Feb 2012 03:34:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Tue, 07 Feb 2012 03:30:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Mon, 06 Feb 2012 03:26:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Sun, 05 Feb 2012 03:24:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Sat, 04 Feb 2012 03:21:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Fri, 03 Feb 2012 03:19:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Thu, 02 Feb 2012 03:16:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Wed, 01 Feb 2012 03:12:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Tue, 31 Jan 2012 03:09:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Mon, 30 Jan 2012 03:06:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Sun, 29 Jan 2012 03:04:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Sat, 28 Jan 2012 02:50:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Fri, 27 Jan 2012 02:47:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Thu, 26 Jan 2012 02:44:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Wed, 25 Jan 2012 02:41:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Tue, 24 Jan 2012 02:38:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Mon, 23 Jan 2012 02:34:00 GMT

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Sun, 22 Jan 2012 02:29:00 GMT

Status Update: [cs13] Spring 12 CS13 Release ~ Complete

Sat, 21 Jan 2012 07:26:00 GMT

All upgrade activities for the CS13 instance are now complete and all features for the Spring '12 release have now been made available for your organization.

Status Update: [cs13] Spring 12 CS13 Release ~ Update

Sat, 21 Jan 2012 06:11:00 GMT

The Spring '12 release is now live for the Sandbox CS13 instance. The Sandbox should be generally available as we continue to perform upgrade activities. We will update Trust once these activities are complete.

Alert: [cs13] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the CS0, CS3, CS4, CS7, CS9, CS11, CS12, and CS13 instances. The problem began on January 20, 2012 and was resolved on February 10, 2012. During this time, customers may have experienced delays in Time Based Workflow processing. Specifically, the impacted Time Based Workflow jobs would remain queued and would not get processed at the expected time. We apologize for any inconvenience this may have caused.

Sat, 21 Jan 2012 02:25:00 GMT

Alert: [cs13] On November 16th, 2011 starting at 04:25 UTC, the salesforce.com Technology Team became aware of a performance degradation affecting customers on the NA0/NA3/NA4/EU0/CS2/CS4/CS13 instances. The issue was cleared at 05:54 UTC. During this time, customers may have experienced an inability to use Sites, intermittent errors when using Single Sign-On, and slow page performance. We apologize for any inconvenience this may have caused you.

Tue, 15 Nov 2011 21:28:00 GMT

The problem is believed to be a flaw in vendor software on our shared networking infrastructure. The affected services were restarted to re-establish normal operations.

Actions to Prevent Future Incidents: - Continuing investigation to be sure we have identified the cause of today's incident - Patches for the vendor software involved are being prepared for production deployment - Additional review of the incident to identify other related infrastructure issues that need to be addressed