Salesforce.com System Status and Alerts

Alert: [na1] The salesforce.com Technology Team observed a performance degradation issue affecting the NA1 instance. The problem began on May 9, 2012 at 16:10 UTC and was resolved by 18:13 UTC. During this time, a subset of customers may have experienced delays in Web-To-Case, Web-To-Lead and dashboard refreshes. Thank you for your continued business and patience during this situation.

Thu, 10 May 2012 01:12:00 GMT

The issue was isolated to resource contention on the database tier. The resulting contention was addressed, allowing for normal behavior to gradually resume.

Actions to Prevent Future Incidents: The salesforce.com Technology Team - - Is investigating options to more efficiently manage resources on the database tier

Status Update: [na1] NA1 Performance Degredation - Resolved

Wed, 09 May 2012 18:13:00 GMT

The salesforce.com Technology Team has resolved the performance degradation on NA1. The issue began at 8:25am PDT and was resolved at 10:33am PDT. We thank you for your continued patience and business.

Status Update: [na1] NA1 Performance Degradation - Update

Wed, 09 May 2012 17:50:00 GMT

The salesforce.com Technology Team has identified the root cause of the NA1 performance degradation and has taken action to resolve it. At this time customers on NA1 should gradually begin to see an improvement in performance with dashboard refreshes and Web-To-Case and Web-To-Lead queue processing. Please continue checking trust.salesforce.com for updated regarding this issue. We apologize for any inconvenience this may have caused.

Status Update: [na1] NA1 Performance Degradation

Wed, 09 May 2012 17:10:00 GMT

The salesforce.com Technology Team is working to resolve a Performance Degradation on the NA1 instance. At this time, a small subset of customers may experience issues with dashboard refreshes and delays with Web-To-Case and Web-To-Lead queue processing. Please check the status of trust.salesforce.com frequently for updates regarding this issue. Thank you for your continued patience during this situation.

Status Update: [na1] Informational Message

Wed, 09 May 2012 08:11:00 GMT

The salesforce.com Technology Team are working to resolve an issue on the trust.salesforce.com environment. The number of transactions detailed on this page are currently inaccurate for 05/09/2012. There are currently no issues which would adversely impact customers.

Status Update: [na1] AP0 (English)/AP1 salesforce.com Scheduled Maintenance Complete

Sat, 05 May 2012 18:02:00 GMT

The AP0 (English)/AP1 salesforce.com scheduled maintenance has successfully completed. Users will now be able to access the salesforce.com service. Thank you for your patience during the maintenance window.

Status Update: [na1] Sandbox CS5 salesforce.com Scheduled Maintenance Complete

Sat, 05 May 2012 18:01:00 GMT

The CS5 sandbox instance scheduled maintenance has successfully completed. Users will now be able to access the salesforce.com service. Thank you for your patience during the maintenance window.

Status Update: [na1] AP0 (English)/AP1 salesforce.com Scheduled Maintenance Beginning

Sat, 05 May 2012 16:58:00 GMT

The AP0 (English)/AP1 salesforce.com scheduled maintenance is beginning at 10:00 AM PDT. During this time, the salesforce.com service will be generally available.

Alert: [na1] The salesforce.com Technology Team resolved a service disruption issue affecting the NA1 instance. The problem began on May 1, 2012 at 15:56 UTC and was resolved by 16:02 UTC. During this time, a subset of customers on the NA1 instance may have experienced slow performance or an inability to access the application. Thank you for your continued business and patience during this situation.

Tue, 01 May 2012 20:37:00 GMT

The issue was isolated to contention within the NA1 database tier. The contention cleared without direct intervention. Actions to Prevent Future Incidents: The salesforce.com Technology Team - - Is investigating the cause of the database contention

Status Update: [na1] NA1 Service Disruption - Resolved

Tue, 01 May 2012 16:09:00 GMT

The salesforce.com Technology Team has resolved the service availability issue on the NA1 instance. The problem began at 15:56 UTC and was resolved as of 16:02 UTC. We apologize for any inconvenience this may have caused you.

Status Update: [na1] NA1 Service Disruption

Tue, 01 May 2012 16:00:00 GMT

The salesforce.com Technology Team is working to isolate a service availability issue on the NA1 instance. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] Informational Message - Update 1

Wed, 25 Apr 2012 14:29:00 GMT

The salesforce.com Technology Team are working to resolve an issue on the trust.salesforce.com environment. The number of transactions detailed on this page are currently inaccurate for 04/24/2012 and 04/25/2012. There are currently no issues which would adversely impact customers.

Status Update: [na1] Salesforce Mobile - Performance Degradation - Resolved

Sun, 22 Apr 2012 17:01:00 GMT

The salesforce.com Technology Team has resolved a performance degradation that was affecting Salesforce Mobile. Customers using this service may have experienced delays in syncing or activating devices. The problem began at 11:26 UTC and was resolved as of 16:53 UTC. We apologize for any inconvenience this may have caused you.

Status Update: [na1] Salesforce Mobile - Performance Degradation

Sun, 22 Apr 2012 15:49:00 GMT

The salesforce.com Technology Team is working to isolate a performance degradation affecting Salesforce Mobile. Customers using this service may experience delays in syncing or activating devices. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] Email to Case Performance Degradation - Update #4

Thu, 19 Apr 2012 20:27:00 GMT

The salesforce.com Technology Team continues to work on isolating the performance degradation issue regarding Email to Case. Some customers might be experiencing delays with the Email to Case Service. Please check the status of Trust frequently for updates regarding this issue. Thank you for your continued patience as we work to resolve this issue.

Status Update: [na1] NA1 Performance Degradation - Search - Resolved

Fri, 13 Apr 2012 21:54:00 GMT

Alert: [na1] The salesforce.com Technology Team resolved a performance degradation issue affecting the NA1 instance. The problem began on April 13, 2012 at 15:30 UTC and was resolved by 16:00 UTC. During this time, some customers may have experienced slow page response times and a small subset of customers may have experienced errors while trying to access the Salesforce service.

Fri, 13 Apr 2012 21:01:00 GMT

The root cause of the incident was isolated to a database procedure call made by a single customer organization which had unexpected results. Additionally, these database procedure calls were resource intensive and arrived while our system was operating during a period of significant demand. This period of extreme demand on our systems resulted in delays in processing some sub-sets of salesforce.com components.

Actions to Prevent Future Incidents - The salesforce.com Technology Team - - Is developing an application patch to fix this issue

Status Update: [na1] NA1 Performance Degradation ~ Resolved

Fri, 13 Apr 2012 16:02:00 GMT

The salesforce.com Technology Team has resolved the performance degradation issue on the NA1 instance. The problem began at 15:30 UTC and was resolved as of 16:00 UTC. We apologize for any inconvenience this may have caused you.

Status Update: [na1] NA1 Performance Degradation

Fri, 13 Apr 2012 15:46:00 GMT

The salesforce.com Technology Team is working to isolate a performance degradation issue on the NA1 instance. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Alert: [na1] The salesforce.com Technology Team has resolved a performance degradation issue affecting Search on the NA1 instance. The problem began on April 8, 2012 at 14:07 UTC and was resolved on April 13, 2012. During this time, customers on the NA1 instance may have experienced incomplete Search results. We apologize for any inconvenience this may be causing you.

Fri, 13 Apr 2012 07:46:00 GMT

The problem was a result of the NA1 maintenance rollback on April 8, 2012. After the rollback, several Search indexes were not usable by the NA1 Search tier. We restored all indexes to the pre-maintenance state and re-indexed all data added or changed since that point.

Actions to Prevent Future Incidents: The salesforce.com Technology Team - - Is reviewing the rollback process for improvements to prevent similar impact in future activities

Status Update: [na1] NA1 Performance Degradation - Search - Update #28

Fri, 13 Apr 2012 07:01:00 GMT

To resolve a previous issue, at 4:17pm PT April 9, 2012, the Technology team restored the search index from an original copy made at 7:00pm PT April 7, 2012. This process then required re-indexing all records added or changed since the time the original copy was made. This re-indexing began at 4:19pm PT April 9, 2012, and at the time there were 69,800 unique organization-objects in need of re-indexing. There are a small number of large entities which are still being processed at this time. We will provide additional information when the re-indexing process is completed. Re-indexing is proceeding and progress is being made as quickly as possible. It is important that customers do not try to reload their data in an effort to expedite their search capabilities. Doing so will further increase the number of records that need re-indexing, and adversely impact the speed at which we will be able to restore full search indexing. Please note that indexing is expected to proceed more slowly during peak hours than during off-peak hours. Ensuring your success is our top priority at salesforce.com, and we are focused on solving this issue as well as preventing any recurrences. Thank you for continued business and your patience during this situation.

Alert: [na1] The salesforce.com Technology Team resolved a performance degradation issue affecting the NA1 instance. The problem began on April 12, 2012 at 21:05 UTC and was resolved by 21:25 UTC. During this time, some customers may have experienced slow page response times and a small subset of customers may have experienced errors while trying to access Salesforce service.

Fri, 13 Apr 2012 05:43:00 GMT

Status Update: [na1] NA1 Performance Degradation ~ Resolved

Thu, 12 Apr 2012 21:30:00 GMT

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

Status Update: [na1] NA1 Performance Degradation

Thu, 12 Apr 2012 21:20:00 GMT

Alert: [na1] The salesforce.com Technology Team has resolved a performance degradation issue affecting Search on the NA1 instance. The problem began on April 8, 2012 at 14:07 UTC and was resolved on April 13, 2012. During this time, customers on the NA1 instance may have experienced incomplete Search results. We apologize for any inconvenience this may be causing you.

Thu, 12 Apr 2012 07:16:00 GMT

Actions to Prevent Future Incidents: The salesforce.com Technology Team - - Is reviewing the rollback process for improvements to prevent similar impact in future activities

Status Update: [na1] NA1 Performance Degradation - Search - Update #27

Thu, 12 Apr 2012 07:01:00 GMT

Status Update: [na1] NA1 Performance Degradation - Search - Update #26

Wed, 11 Apr 2012 16:01:00 GMT

Status Update: [na1] NA1 Performance Degradation - Search - Update #25

Wed, 11 Apr 2012 15:00:00 GMT

To resolve a previous issue, at 4:17pm PT April 9, 2012, the Technology team restored the search index from an original copy made at 7:00pm PT April 7, 2012. This process then required re-indexing all records added or changed since the time the original copy was made. This re-indexing began at 4:19pm PT April 9, 2012, and at the time there were 69,800 unique organization-objects in need of re-indexing. There are currently 563 unique organization-objects left. Re-indexing is proceeding and progress is being made as quickly as possible. It is important that customers do not try to reload their data in an effort to expedite their search capabilities. Doing so will further increase the number of records that need re-indexing, and adversely impact the speed at which we will be able to restore full search indexing. Please note that indexing is expected to proceed more slowly during peak hours than during off-peak hours. Ensuring your success is our top priority at salesforce.com, and we are focused on solving this issue as well as preventing any recurrences. Thank you for continued business and your patience during this situation.

Alert: [na1] The salesforce.com Technology Team has resolved a performance degradation issue affecting Search on the NA1 instance. The problem began on April 8, 2012 at 14:07 UTC and was resolved on April 13, 2012. During this time, customers on the NA1 instance may have experienced incomplete Search results. We apologize for any inconvenience this may be causing you.

Wed, 11 Apr 2012 07:01:00 GMT

Actions to Prevent Future Incidents: The salesforce.com Technology Team - - Is reviewing the rollback process for improvements to prevent similar impact in future activities

Alert: [na1] The salesforce.com Technology Team resolved a performance degradation issue affecting the NA1 instance. The problem began on April 10, 2012 at 21:59 UTC and was resolved by 22:03 UTC. During this time, customers on the NA1 instance may have experienced slow performance while using the Salesforce application.

Wed, 11 Apr 2012 01:45:00 GMT

The problem was isolated to a resource contention within the NA1 database tier. The resource contention cleared without direct intervention and performance returned to normal. 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 investigating the source of the resource contention

Status Update: [na1] NA1 Performance Degradation - Resolved

Tue, 10 Apr 2012 22:40:00 GMT

The salesforce.com Technology Team has identified a performance degradation that would have affected customers on the NA1 instance starting at 21:59 UTC and ending at 22:03 UTC. During this period, some customers may have experienced slowness or received errors when logging into the Salesforce service. We apologize for any inconvenience this may have caused you.

Alert: [na1] The salesforce.com Technology Team has resolved a performance degradation issue affecting Search on the NA1 instance. The problem began on April 8, 2012 at 14:07 UTC and was resolved on April 13, 2012. During this time, customers on the NA1 instance may have experienced incomplete Search results. We apologize for any inconvenience this may be causing you.

Tue, 10 Apr 2012 17:24:00 GMT

Actions to Prevent Future Incidents: The salesforce.com Technology Team - - Is reviewing the rollback process for improvements to prevent similar impact in future activities

Alert: [na1] The salesforce.com Technology Team has resolved a performance degradation issue affecting Search on the NA1 instance. The problem began on April 8, 2012 at 14:07 UTC and was resolved on April 13, 2012. During this time, customers on the NA1 instance may have experienced incomplete Search results. We apologize for any inconvenience this may be causing you.

Mon, 09 Apr 2012 23:59:00 GMT

Actions to Prevent Future Incidents: The salesforce.com Technology Team - - Is reviewing the rollback process for improvements to prevent similar impact in future activities

Status Update: [na1] NA1 Performance Degradation-Search - Update #3

Mon, 09 Apr 2012 23:21:00 GMT

NA1 Search indexing has resumed as of 4/9/2012, 4:17 PM PT. All data indexed before 7:00pm PT April 7, 2012 should be searchable soon after this time, and all search results will be fully indexed and available by 5:00am PT April 10, 2012. Data entered after 7:00pm PT April 7, 2012 through 5:00am PT April 10, 2012 may not be searchable until the data is fully indexed, which is currently projected to complete by 5:00am PT April 10, 2012.

Ensuring your success is our top priority at salesforce.com, and we are focused on solving this issue as well as preventing any recurrences. Thank you for continued business and your patience during this situation.

Status Update: [na1] NA1 Performance Degradation - Search - Update #2

Mon, 09 Apr 2012 22:05:00 GMT

The salesforce.com Technology Team has identified a fix for the performance degradation issue affecting Search on the NA1 instance. This issue affects some customers' ability to retrieve complete search results for data entered prior to April 7, 2012 at 7:00pm PT. No data has been lost.

To resolve this issue, the Technology team is restoring the search index from an original copy made at 7:00pm PT April 7, 2012. This will require that search indexing for all NA1 customers will be suspended, beginning at 3:00pm PT. We will resume search indexing at 6:00pm PT. All data indexed before 7:00pm PT April 7, 2012 should be searchable soon after this time, and all search results will be fully indexed and available by 5:00am PT April 10, 2012. Data entered after 7:00pm PT April 7, 2012 through 5:00am PT April 10, 2012 may not be searchable until the data is fully indexed, which is currently projected to complete by 5:00am PT April 10, 2012.

Status Update: [na1] NA1 Performance Degradation - Search - Update #1

Mon, 09 Apr 2012 19:56:00 GMT

The salesforce.com Technology Team continues to work on resolving a performance degradation issue affecting Search on the NA1 instance. Some customers may be experiencing incomplete search results at this time. No data is lost, but some records may not currently be available to Search. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] NA1 Performance Degradation - Search

Mon, 09 Apr 2012 16:50:00 GMT

The salesforce.com Technology Team is working to isolate a performance degradation issue affecting Search on the NA1 instance. Some customers may be experiencing incomplete search results at this time. No data is lost, but some records may not currently be available to Search. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] NA1 Search Performance Degradation - RESOLVED

Mon, 09 Apr 2012 02:13:00 GMT

The salesforce.com Technology Team has resolved a performance degradation issue related to Search on the NA1 instance. We apologize for any inconvenience this may be causing you.

Alert: [na1] The salesforce.com Technology has resolved a performance degradation issue affecting Search on the NA1 instance. The problem began on April 8, 2012 at 14:07 UTC and was resolved on April 13, 2012. During this time, customers on the NA1 instance may have experienced incomplete Search results. We apologize for any inconvenience this may be causing you.

Sun, 08 Apr 2012 23:59:00 GMT

Actions to Prevent Future Incidents: The salesforce.com Technology Team - - Is reviewing the rollback process for improvements to prevent similar impact in future activities

Status Update: [na1] Incident Summary: NA1 Maintenance Window Reschedule

Sun, 08 Apr 2012 21:15:00 GMT

At salesforce.com, ensuring customer success through trusted system availability, performance, and reliability is our top priority. With these values in mind, the salesforce.com Technology team made the decision to reschedule the migration of a subset of customers currently on the NA1 instance to the NA13 instance. During the course of the NA1 maintenance window, we encountered a network issue that extended that window. These issues were resolved at 8:38pm PT, and NA1 maintenance activities resumed. We subsequently identified a separate issue that prevented us from completing the migration of some NA1 customers to the NA13 instance. The issue was associated with testing and monitoring resources, resulting in the inability to verify and monitor the operation and performance of these instances. We actively pursued multiple, parallel avenues to resolve this issue. The maintenance window was extended by 2 1/2 hours, and was targeted for completion at 4:30am PT. Despite best efforts, the Technology team was not able to complete the planned migration and rolled back the changes to restore NA1 to its previous state at 7:07am PT. Customers scheduled to migrate from NA1 to NA13 remain on the NA1 instance at this time. Customers may experience a delay in searching data entered from April 7, 2012 at 7:00pm PT through April 8, 2012 at 12:45am PT, until the data is fully indexed. We expect complete resolution of this delay within 24 hours. We will update these customers of the rescheduled migration window no later than Thursday, April 12, 2012. We are committed to upholding the transparency customers have come to expect from salesforce.com. As part of our standard process, we will perform a full root cause analysis for this issue and provide our customers with the details once they are available. We appreciate your patience and apologize for any inconvenience this change has caused you and your organization.

Status Update: [na1] NA1 Search Performance Degradation

Sun, 08 Apr 2012 16:55:00 GMT

The salesforce.com Technology Team is working to resolve a performance degradation issue related to Search on the NA1 instance. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Alert: [na1] The salesforce.com Technology team experienced a network issue on other instances that delayed activities in the NA1 maintenance window. These issues were resolved at 8:38pm PT and the NA1 maintenance activities resumed. We subsequently identified a separate issue that prevented verification of the NA1 and the NA13 instances. Due to the inability to complete full verification across both instances, the decision was made to resolve these issues and not continue with the migration activities. The maintenance window was planned for April 8, 2012 02:00 UTC to 09:00 UTC. Service was restored for the NA1 instance at April 8, 2012 14:07 UTC.

Sun, 08 Apr 2012 15:30:00 GMT

The salesforce.com technology team has completed the activities required to revert NA1 to its original state ahead of schedule. The NA1 instance is now accessible by users. All customers who were scheduled migrate to the NA13 instance remain on the NA1 instance at this time. Customers on the NA1 instance and customers targeted to migrate to the NA13 instance will be notified of the rescheduled window as soon as more information becomes available. We appreciate your patience and apologize for any inconvenience this change has caused your organization.

Status Update: [na1] NA1 salesforce.com Scheduled Maintenance Update

Sun, 08 Apr 2012 14:32:00 GMT

The salesforce.com Technology Team has completed the activities required to revert NA1 to its original state ahead of schedule. The NA1 instance is now accessible by users. All customers who were scheduled migrate to the NA13 instance remain on the NA1 instance at this time. Customers on the NA1 instance and customers targeted to migrate to the NA13 instance will be notified of the rescheduled window as soon as more information becomes available. We appreciate your patience and apologize for any inconvenience this change has caused your organization.

Status Update: [na1] NA1 salesforce.com Scheduled Maintenance Update

Sun, 08 Apr 2012 12:10:00 GMT

At salesforce.com, ensuring customer success through trusted system availability, performance, and reliability are our top priorities. With these values in mind, the salesforce.com technology team has made the decision to postpone the migration of a subset of NA1 organizations to the NA13 instance. As a result, the scheduled maintenance window has been extended by 4 more hours, and is now targeted for completion at 09:00 AM PT. The salesforce.com Technology team experienced a network issue on other instances that delayed activities in the NA1 maintenance window. The team wanted to ensure the root cause of the network issues was resolved prior to starting the NA1 maintenance activities. We subsequently identified an issue with the ability to complete verification the NA1 and the NA13 instances. Due to the inability to complete full verification across both instances, the decision was made to resolve these issues before executing this migration. Customers on the NA1 instance will be notified of the rescheduled window as soon as more information becomes available. We appreciate your patience and apologize for any inconvenience this change has caused your organization.

Status Update: [na1] NA1 salesforce.com Scheduled Maintenance Update

Sun, 08 Apr 2012 10:24:00 GMT

At salesforce.com, ensuring customer success through trusted system availability, performance, and reliability are our top priorities. With these values in mind, we have made the decision to extend the NA1 maintenance window. We have identified an issue with the ability to complete verification on the NA1 and NA13 instances, and have made the decision to extend the window to complete these activities. The updated NA1 maintenance window is: Saturday April 7, 2012 at 7:00pm PT to Sunday, April 8, 2012 at 4:30 AM PT We appreciate your patience and apologize for any inconvenience this change has caused your organization.

Status Update: [na1] NA1 salesforce.com Scheduled Maintenance Update

Sun, 08 Apr 2012 08:12:00 GMT

At salesforce.com, ensuring customer success through trusted system availability, performance and reliability are our top priorities. With these values in mind, we have made the decision to extend the NA1 maintenance window. The salesforce.com Technology team experienced a network issue on other instances that impacted the start of the previously communicated NA1 maintenance window. The team wanted to ensure the root cause of the network issues was resolved prior to starting the NA1 maintenance activities. The updated NA1 maintenance window is: Saturday April 7, 2012 at 7:00pm PT to Sunday, April 8, 2012 3:30am PT We appreciate your patience and apologize for any inconvenience this change has caused your organization.

Alert: [na1] The salesforce.com Technology Team resolved a performance degradation issue affecting the NA1 instance. The problem began on April 3, 2012 at 14:52 UTC and was resolved by 17:24 UTC. During this time, customers on the NA1 instance may have experienced slow performance while using the application. We apologize for any inconvenience this may have caused you.

Wed, 04 Apr 2012 00:03:00 GMT

The problem was isolated to contention within the storage tier shared by the NA1 and NA5 instances. The contention was caused by a database resiliency feature running concurrently with storage work preparing for the upcoming NA1 maintenance. Actions to Prevent Future Incidents - The salesforce.com Technology Team - - Is investigating changes to storage procedures to prevent this scenario - Is reviewing improvements to storage performance monitoring

Status Update: [na1] NA1 Performance Degradation - Resolved

Tue, 03 Apr 2012 17:35:00 GMT

The salesforce.com Technology Team has resolved the performance degradation issue on the NA1 instance. The problem began at 14:52 UTC and was resolved as of 17:24 UTC. We apologize for any inconvenience this may have caused you

Status Update: [na1] NA1 Performance Degradation ~ Update

Tue, 03 Apr 2012 16:50:00 GMT

The Salesforce.com Technology Team continues to work on isolating the performance degradation issue on the NA1 instance. Customers on this instance may experience slow performance when using the application. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] NA1 Performance Degradation

Tue, 03 Apr 2012 15:16:00 GMT

The salesforce.com Technology Team is working to isolate a performance degradation issue on theNA1 instance. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Alert: [na1] The salesforce.com Technology Team resolved a performance degradation issue affecting the NA1 instance. The problem began on March 27, 2012 at 00:11 UTC and was resolved by 00:13 UTC. During this time, customers on the NA1 instance may have experienced inability to login to the NA1 instance and slower than normal page response times while using the Salesforce application.

Tue, 27 Mar 2012 00:30:00 GMT

The root cause of the problem was isolated to a contention within the NA1 database tier. The cause of the database contention is under investigation.

Alert: [na1] The salesforce.com Technology Team resolved a performance degradation issue affecting Search on the NA1 instance. The problem began on March 14, 2012 at 05:00 UTC and was resolved by 17:45 UTC. During this time, customers on the NA1 instance may have experienced slow Search performance or incomplete Search results. We apologize for any inconvenience this may have caused you.

Wed, 14 Mar 2012 23:17:00 GMT

The Problem was caused by invalid cache data on the NA1 search tier. Once the affected data was identified, the related cache objects were refreshed.

Actions to Prevent Future Incidents: The salesforce.com Technology Team - -Is investigating improvements to monitoring systems to better detect this kind of Search event in the future -Is investigating improvements to Search to detect and self-resolve cache events of this nature

Status Update: [na1] NA1 Performance Degradation - Search - Resolved

Wed, 14 Mar 2012 22:10:00 GMT

The salesforce.com Technology Team has resolved the performance degradation issue affecting Search on the NA1 instance. The problem began at 05:00 UTC and was resolved as of 17:45 UTC. During this period, some customers may have experienced intermittent slow search performance or incomplete search results. We continue to closely monitor for any further impacting events. We apologize for any inconvenience this may have caused you.

Status Update: [na1] NA1 Performance Degradation - Search - Update #3

Wed, 14 Mar 2012 20:03:00 GMT

The salesforce.com Technology Team continues to work on isolating the performance degradation issue affecting Search on the NA1 instance. At this time, some customers may be experiencing intermittent slow search performance or incomplete search results. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] NA1 Performance Degradation - Search - Update #2

Wed, 14 Mar 2012 19:04:00 GMT

Status Update: [na1] NA1 Performance Degradation - Search - Update #1

Wed, 14 Mar 2012 17:58:00 GMT

Status Update: [na1] NA1 Performance Degradation - Search

Wed, 14 Mar 2012 16:45:00 GMT

The salesforce.com Technology Team is working to isolate a performance degradation affecting Search on the NA1 instance. At this time, some customers may be experiencing intermittent slow search performance or incomplete search results. Subsequent investigation has identified that customers may have experienced similar impact on March 13, 2012 between the times of 13:30 UTC and 19:00 UTC. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Alert: [na1] The salesforce.com Technology Team resolved a performance degradation issue affecting Search on the NA1 instance. The problem began on March 13, 2012 at 13:30 UTC and was resolved by 19:00 UTC. During this time, customers on the NA1 instance may have experienced slow Search performance or incomplete Search results. We apologize for any inconvenience this may have caused you.

Tue, 13 Mar 2012 23:33:00 GMT

The problem was caused by invalid cache data on the NA1 Search tier. Once the affected data was identified, the related cache objects were refreshed.

Actions to Prevent Future Incidents: The salesforce.com Technology Team - - Investigating improvements to monitoring systems to better detect this kind of Search event in the future - is investigating improvements to Search to detect and self-resolve cache events of this nature

Alert: [na1] On February 24, 2012 the salesforce.com Technology Team resolved a performance degradation impacting the NA1 instance. The problem began at 3:29:00 UTC and was resolved by 12:08: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: [na1] On February 24, 2012 the salesforce.com Technology Team resolved a performance degradation impacting the NA1 instance. The problem began at 3:29:00 UTC and was resolved by 12:08: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.

Thu, 23 Feb 2012 09:05:00 GMT

Status Update: [na1] Inbound Mail Queue Performance Degradation - Resolved

Sun, 12 Feb 2012 17:45:00 GMT

The salesforce.com Technology Team has resolved the performance degradation issue affecting Inbound Email services on all instances. The problem began at 06:17 UTC and was resolved as of 17:58 UTC. We apologize for any inconvenience this may have caused you.

Status Update: [na1] Inbound Mail Queue Performance Degradation - Update 1

Sun, 12 Feb 2012 15:40:00 GMT

The salesforce.com Technology Team continues to work on isolating a performance degradation issue affecting Inbound Email services on all instances. During this time, customers may be experiencing delays in processing of Email to Apex, Email to Case, and Email to Salesforce requests. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Alert: [na1] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the NA1 instance. The problem began on February 3, 2012 and was resolved for most customers by 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. A small subset of customers were further impacted until February 11, 2012. We apologize for any inconvenience this may have caused.

Sat, 11 Feb 2012 23:49:00 GMT

The problem was 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 an application update that resolved the root issue for most customers on NA1 at 02:19 UTC February 10, 2012. Another application update resolved the remaining issues at 10:37 UTC February 11, 2012.

Next Actions: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Status Update: [na1] NA1 Time Based Workflow Performance Degradation - Resolved

Sat, 11 Feb 2012 19:51:00 GMT

The salesforce.com Technology Team has resolved the performance degradation affecting Time Based Workflow on the NA1 instance. The issue was resolved as of 10:37 UTC February 11, 2012. We apologize for any inconvenience this may have caused you.

Status Update: [na1] Sandbox CS2 salesforce.com Scheduled Upgrade Update

Sat, 11 Feb 2012 19:15:00 GMT

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

Status Update: [na1] Sandbox CS8/CS10 salesforce.com Scheduled Upgrade ~ Update

Sat, 11 Feb 2012 19:10:00 GMT

The Spring '12 release is now live for the CS8/CS10 instance. The CS8/CS10 should be generally available as we continue to perform upgrade activities including feature enablement. We will update Trust once these activities are complete.

Status Update: [na1] AP0 salesforce.com Scheduled Upgrade Beginning

Sat, 11 Feb 2012 18:05:00 GMT

The scheduled upgrade for AP0 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 Spring '12.

Status Update: [na1] Sandbox CS1/CS6 salesforce.com Scheduled Upgrade Beginning

Sat, 11 Feb 2012 18:00:00 GMT

The scheduled upgrade for CS1/ CS6 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 Spring '12.

Status Update: [na1] NA1 Time Based Workflow Performance Degradation - Update

Fri, 10 Feb 2012 22:57:00 GMT

The salesforce.com Technology Team is continuing to investigate a performance degradation affecting Time Based Workflows on the NA1 instance. A small subset of customers may experience delays in Time Based Workflow processing. Additional diagnostic logging is being enabled to support the investigation effort. Updated information regarding this issue will be posted by 12:00pm PST on Saturday, February 11, 2012. We apologize for any inconvenience this may have caused.

Status Update: [na1] Spring '12 Time Based Workflow Performance Degradation

Fri, 10 Feb 2012 16:20:00 GMT

The salesforce.com Technology Team is investigating a performance degradation affecting Time Based Workflows on the NA1 instance. A small subset of customers may experience delays in Time Based Workflow processing. Updated information will be posted once it is available. We apologize for any inconvenience this may have caused.

Alert: [na1] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the NA1 instance. The problem began on February 3, 2012 and was resolved for most customers by 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. However, for a small subset of customers, the issue still persists and we are actively continuing our investigation. We apologize for any inconvenience this may have caused.

Fri, 10 Feb 2012 13:10:00 GMT

Next Actions: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Alert: [na1] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the NA1 instance. The problem began on February 3, 2012 and was resolved for most customers by 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. A small subset of customers were further impacted until February 11, 2012. We apologize for any inconvenience this may have caused.

Thu, 09 Feb 2012 13:10:00 GMT

Next Actions: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Alert: [na1] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the NA1 instance. The problem began on February 3, 2012 and was resolved for most customers by 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. However, for a small subset of customers, the issue still persists and we are actively continuing our investigation. We apologize for any inconvenience this may have caused.

Wed, 08 Feb 2012 13:09:00 GMT

Next Actions: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Alert: [na1] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the NA1 instance. The problem began on February 3, 2012 and was resolved for most customers by 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. A small subset of customers were further impacted until February 11, 2012. We apologize for any inconvenience this may have caused.

Tue, 07 Feb 2012 13:08:00 GMT

Next Actions: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Alert: [na1] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the NA1 instance. The problem began on February 3, 2012 and was resolved for most customers by 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. A small subset of customers were further impacted until February 11, 2012. We apologize for any inconvenience this may have caused.

Mon, 06 Feb 2012 13:05:00 GMT

Next Actions: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Alert: [na1] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the NA1 instance. The problem began on February 3, 2012 and was resolved for most customers by 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. A small subset of customers were further impacted until February 11, 2012. We apologize for any inconvenience this may have caused.

Sun, 05 Feb 2012 13:00:00 GMT

Next Actions: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Alert: [na1] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the NA1 instance. The problem began on February 3, 2012 and was resolved for most customers by 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. A small subset of customers were further impacted until February 11, 2012. We apologize for any inconvenience this may have caused.

Sat, 04 Feb 2012 13:00:00 GMT

Next Actions: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Status Update: [na1] Spring 12 NA1 Release ~ Complete

Sat, 04 Feb 2012 07:02:00 GMT

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

Status Update: [na1] Spring 12 NA1 Release ~ Update

Sat, 04 Feb 2012 04:18:00 GMT

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

Status Update: [na1] Spring 12 NA1 Release ~ Start

Sat, 04 Feb 2012 04:00:00 GMT

The scheduled upgrade for NA1 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 Spring '12.

Status Update: [na1] Help & Training Portal Degradation

Fri, 03 Feb 2012 19:45:00 GMT

The salesforce.com Technology Team is working to resolve an issue affecting the Help & Training Portal. Customers may not be able to view courses in the course catalog, but can still take courses through the training gadgets on the home page. Updated information will be posted when the issue is resolved. We apologize for any inconvenience this may have caused you.

Alert: [na1] On February 10, 2012 the salesforce.com Technology Team resolved a performance degradation affecting Time Based Workflow on the NA1 instance. The problem began on February 3, 2012 and was resolved for most customers by 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. A small subset of customers were further impacted until February 11, 2012. We apologize for any inconvenience this may have caused.

Fri, 03 Feb 2012 12:00:00 GMT

Next Actions: The salesforce.com Technology Team is - - Improving testing procedures to better identify and address issues like this in the future

Alert: [na1] The salesforce.com Technology Team has resolved the performance degradation issue on the NA1 instance. The problem began at 14.40 UTC and was resolved as of 14.49 UTC. During this time customers may have experienced slower than normal login times and performance response times. We apologize for any inconvenience this may have caused you.

Wed, 01 Feb 2012 17:38:00 GMT

The problem was caused by an over-utilization of the storage functionality. As the event occurred manual steps were taken to alleviate the over-utilization. These steps restored normal performance to the instance. Actions to Prevent Future Incidents: The salesforce.com Technology Team is - -Working with storage vendors on a permanent solution. -Reviewing storage monitoring procedures.

Status Update: [na1] NA1 - Performance Degradation Resolved.

Wed, 01 Feb 2012 16:25:00 GMT

The salesforce.com Technology Team has resolved the performance degradation issue on the NA1 instance. The problem began at 14.40 UTC and was resolved as of 14.49 UTC. During this time customers may have experienced slower than normal login times and performance response times. We apologize for any inconvenience this may have caused you.

Status Update: [na1] AP1 Performance Degradation - Content Search - Update

Thu, 26 Jan 2012 09:40:00 GMT

The salesforce.com Technology Team is aware of a performance degradation issue affecting content search on the AP1 instance. The problem began at 03:35 hrs UTC on January 26, 2012. The root cause of the incident was isolated to an anomaly in the content search index store. To address the problem, the Technology Team performed a check and fix procedure which is designed to intelligently isolate the problem areas and move them away from the main content search index store. As a result, some customer might be experiencing issues with search ability of older content. However any new content should be searchable. The Technology Team is currently in the process of rebuilding the content search index problem areas. No data or content is being lost in the process. We sincerely apologize for any inconvenience this may be causing you. Please check the status at trust.salesforce.com for frequent updates.

Status Update: [na1] AP0 Performance Degradation - Resolved

Tue, 24 Jan 2012 05:40:00 GMT

The salesforce.com Technology Team has resolved the performance degradation issue affecting the Search functionality on the AP0 instance. The problem began at 24 Jan 2012 04:11 UTC and was resolved as of 24 Jan 2012 05:40 UTC. We apologize for any inconvenience this may have caused you.

Status Update: [na1] Inbound Email Delays ~ Resolved

Fri, 20 Jan 2012 00:55:00 GMT

The inbound mail issue between salesforce.com and the specific email service provider has been resolved. However, messages are queued on the service provider side, and may take some time to process. We apologize for any inconvenience this may have caused you.

Status Update: [na1] Inbound Email Delays

Fri, 20 Jan 2012 00:00:00 GMT

At this time we have identified an issue with inbound email to our application from a specific public “free” email service provider. We are actively working with this service provider and our technology team to remediate the condition. Customers impacted by this event will be unable to utilize email to case, email to Apex ,email workflow approval and reply to Chatter until we resolve this issue with this service provider. Please check back every hour for a status update regarding our progress on resolving this issue. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] CS12 Performance Degradation - Resolved

Mon, 16 Jan 2012 19:43:00 GMT

The salesforce.com Technology Team has identified a performance degradation issue on the CS12 instance. The problem began at 19:30 UTC and was resolved as of 19:33 UTC. During this period customers may have experienced slowness or an inability to log in to the Salesforce service. We apologize for any inconvenience this may have caused you.

Status Update: [na1] All Instances - Informational Message - Update #1

Sun, 15 Jan 2012 09:50:00 GMT

The salesforce.com Technology Team are actively working to resolve an issue on the trust.salesforce.com environment. The number of transactions detailed on this page are currently inaccurate for 01/14/2012 and 01/15/2012. Data shown for 01/10/2012, 01/11/2012, 01/12/2012 and 01/13/2012 have been corrected. There are currently no issues which would adversely impact customers.

Status Update: [na1] AP0 Scheduled Maintenance Update#1

Sat, 14 Jan 2012 17:05:00 GMT

The salesforce.com Technology team continues to work on the AP0 migration, and we continue to make progress. Thank you for your continued patience as we complete these migration activities. For additional information, please visit http://www.trust.salesforce.com

- salesforce.com Premier Support

Status Update: [na1] All Instances - Informational Message - Update #1

Sat, 14 Jan 2012 09:09:00 GMT

The salesforce.com Technology Team are actively working to resolve an issue on the trust.salesforce.com environment. The number of transactions detailed on this page are currently inaccurate for 01/12/2012. Data shown for 01/10/2012 and 01/11/2012 have been corrected. There are currently no issues which would adversely impact customers.

Status Update: [na1] All Instances - Informational Message - Update #1

Fri, 13 Jan 2012 17:15:00 GMT

The salesforce.com Technology Team are actively working to resolve an issue on the trust.salesforce.com environment. The number of transactions detailed on this page are currently inaccurate for 01/11/2012 and 01/12/2012. Data shown for 01/10/2012 has been corrected. There are currently no issues which would adversely impact customers.

Status Update: [na1] CS12 Service Disruption - Update 2

Wed, 11 Jan 2012 19:25:00 GMT

The salesforce.com Technology Team has isolated the service availability issue on the CS12 instance. The problem began at 18:32 UTC. At this time we have identified the issue and believe customers should begin to see normal performance return. We will continue to monitor until we are certain that we are all clear. We apologize for any inconvenience this may have caused you.

Status Update: [na1] Salesforce.com mobile

Wed, 28 Dec 2011 08:01:00 GMT

As part of salesforce.com's effort to provide the best service to customers, the Technology Team performed an upgrade to the Salesforce Mobile infrastructure. The upgrade was performed on December 28, 2011 between 01:20 and 04:21 UTC. As a result of the upgrade, some customers using Single Sign On (SSO) with Salesforce Mobile may have begun to experience authentication errors due to a minor configuration inconsistency between the old and new systems. Please reach out to salesforce.com's Support Team if you encounter any authentication issues with SSO and Salesforce Mobile. We sincerely apologize for any inconvenience this may have caused you.

Status Update: [na1] Salesforce.com mobile

Wed, 28 Dec 2011 05:06:00 GMT

Alert: [na1] On December 16, 2011 beginning at 19:11 UTC and ending at 19:19 UTC, the salesforce.com Technology Team resolved a performance degradation impacting the NA1 instance. During this time, customers may have experienced slow performance or intermittent errors while trying to access or use the Salesforce application. We apologize for any inconvenience this may have caused you.

Fri, 16 Dec 2011 22:04:00 GMT

The cause is still unknown. However, investigations thus far suggest that it is possibly due to a contention issue within our database tier. The salesforce.com Technology Team is actively continuing the investigation of this incident.

Status Update: [na1] NA1 Performance Degradation - Resolved

Fri, 16 Dec 2011 19:27:00 GMT

The salesforce.com Technology Team has resolved the performance degradation issue affecting the NA1 instance. The problem began at 19:11 UTC and was resolved as of 19:19 UTC. During this time, customers on the NA1 instance may have experienced intermittent slowness or issues logging into the Salesforce service. We apologize for any inconvenience this may have caused you.

Status Update: [na1] CS6 Sandbox Scheduled Maintenance Beginning

Mon, 05 Dec 2011 15:55:00 GMT

The maintenance activity for the CS6 Sandbox instance is beginning at 8:00am PST. During this time, the salesforce.com service will not be available. We appreciate your patience during this maintenance window.

Status Update: [na1] AP1 salesforce.com Scheduled Maintenance Update

Sat, 03 Dec 2011 20:51:00 GMT

At salesforce.com, ensuring customer success through trusted system availability, performance, and reliability are top priorities. We are nearing completing of the AP1 migration, but experienced an unexpected delay with our data replication process that has impacted the previously communicated AP1 migration maintenance window. To ensure the highest level of quality for this migration, we have made the decision to extend the AP1 migration window. This will ensure that customers continue to have the best possible experience with our service.

The updated AP1 migration window is: December 3, 2011 4:00 am PST - December 3, 2011 3:30 pm PST

Ensuring your success is our top priority at salesforce.com, and we are focused on mitigating these issues moving forward.

Thank you for your continued business and patience as we complete these migration activities.

Best regards, Salesforce.com Premier Support

Alert: [na1] On November 30, 2011 the salesforce.com Technology Team resolved a performance degradation issue on the NA1, NA2, NA5, NA6, AP0, CS0, CS1, CS3 and CS12 instances. The problem began at 15:47 UTC and was resolved as of 16:18 UTC. For the duration of the event, customers may have experienced intermittent inability to access salesforce.com services. We apologize for any inconvenience this may have caused you.

Thu, 01 Dec 2011 06:54:00 GMT

The root cause of the problem was isolated to a configuration issue on our network load balancer. The configuration exposed the device to a vendor bug that resulted in heavy load on its CPU and it stopped accepting new requests. Our service provider detected the problem and automatically routed the traffic through another active network device. Our network architecture which is designed to be resilient for most failure scenarios experienced a double failure. The automatic failover that was performed resulted in excessive load on the network firewalls. The salesforce.com Technology Team had to intervene to restore normal connectivity. During this time, a subset of incoming network requests may have failed, and the subsequent retries may have succeeded. Actions to prevent future incidents: The salesforce.com Technology Team: - has corrected the configuration issue on our network load balancers. - is working with our network vendor to establish better collaboration and testing of device configurations. - will work to implement greater level of monitoring around our network devices.

Status Update: [na1] NA1, NA2, NA5, NA6, AP0, CS0, CS1, CS3, CS12 ~ Resolved

Wed, 30 Nov 2011 16:25:00 GMT

The Salesforce.com Technology Team has resolved the performance degradation issue on the NA1, NA2, NA5, NA6, AP0, CS0, CS1, CS3, CS12 instances. The problem began at 15:47 UTC and was resolved as of 16:18 UTC. The root cause is under investigation. However, we believe an anomaly on our network tier impacted our monitoring system and may not have impacted our customers on these instances. We apologize for any inconvenience this may have caused you.

Status Update: [na1] NA1, NA2, NA5, NA6, AP0, CS0, CS1, CS3, CS12

Wed, 30 Nov 2011 16:00:00 GMT

The Salesforce.com Technology Team is working to isolate a performance degradation issue on NA1, NA2, NA5, NA6, AP0, CS0, CS1, CS3, CS12 instances. Customers on these instances maybe experiencing issues logging in. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] Data.com Scheduled Maintenance Activity

Sun, 27 Nov 2011 08:00:00 GMT

The salesforce.com Technology Team will be performing scheduled maintenance for the Data.com service at the following time:

Sunday, November 27th, 2011 from 8:00PM PST to 10:00PM PST

During this time, the salesforce.com Data.com service will be unavailable. Users attempting to search the Data.com/Jigsaw data via search or Clean records using Data.com will be prompted with an error message stating the unavailability of Data.com. We appreciate your patience during this maintenance window.

Status Update: [na1] NA12 salesforce.com system status

Sat, 26 Nov 2011 09:42:00 GMT

The salesforce.com NA12 instance is currently experiencing performance degradation. Additional information will be posted to www.trust.salesforce.com as it becomes available. Thank you for your patience. - salesforce.com Premier Support

Status Update: [na1] Data.com Scheduled Maintenance Activity

Fri, 25 Nov 2011 08:01:00 GMT

The salesforce.com Technology Team will be performing scheduled maintenance for the Data.com service at the following time:

Sunday, November 27th, 2011 from 8:00PM PST to 10:00PM PST

Status Update: [na1] Data.com Scheduled Maintenance Activity

Thu, 24 Nov 2011 08:01:00 GMT

The salesforce.com Technology Team will be performing scheduled maintenance for the Data.com service at the following time:

Sunday, November 27th, 2011 from 8:00PM PST to 10:00PM PST

Status Update: [na1] Data.com Scheduled Maintenance Activity

Wed, 23 Nov 2011 08:01:00 GMT

The salesforce.com Technology Team will be performing scheduled maintenance for the Data.com service at the following time:

Sunday, November 27th, 2011 from 8:00PM PST to 10:00PM PST

Alert: [na1] On November 16th, 2011 starting at 05:14 UTC, the salesforce.com Technology Team became aware of a performance degradation affecting customers on the NA1/NA2/NA5/NA6/AP0/CS0/CS1/CS3/CS12 instances. The issue was cleared at 05:52 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 20:31: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

Alert: [na1] On November 12th, 2011 starting at 01:18 UTC the salesforce.com Technology Team became aware of a performance degradation affecting customers on the NA1 instance. The issue was cleared at 02:49 UTC. During the incident some customers may have experienced slower than normal page response times for their requests, sporadic error on pages and intermittent login failures. We sincerely apologize for any inconvenience this may have caused you.

Sat, 12 Nov 2011 06:29:00 GMT

The salesforce.com Technology Team identified the issue to be the result of a contention at the database layer and a complete root cause of the incident is under investigation.

Status Update: [na1] NA1 Performance Degradation - Resolved

Sat, 12 Nov 2011 02:50:00 GMT

The salesforce.com Technology Team has resolved the performance degradation affecting the NA1 instance. The problem was resolved as of 02:50 UTC. We will provide more information regarding this event in the Incident posting. We apologize for any inconvenience this may have caused you.

Status Update: [na1] NA1 Performance Degradation

Sat, 12 Nov 2011 01:52:00 GMT

Alert: [na1] Between 13:05 UTC and 13:23 UTC there was a performance degradation affecting the NA1 instance.

Fri, 04 Nov 2011 14:17:00 GMT

This was caused by a scheduled release running into EST hours. During this period, customers on the NA1 instance may have experienced slow performance. We apologize for any inconvenience this may have caused you.

Status Update: [na1] NA1- Performance degradation - Resolved

Fri, 04 Nov 2011 14:09:00 GMT

Between 13:05 UTC and 13:23 UTC there was a performance degradation affecting the NA1 instance. The NA1 salesforce.com services are now fully operational. We will provide you with an additional update once we have completed the root cause analysis. We appreciate your patience and apologize for the inconvenience to you, your employees, customers, and partners.

Alert: [na1] The salesforce.com Technology Team is aware of a performance degradation issue that impacted the AP0, NA1, NA2, NA5, NA6, CS0, CS1, CS3 and CS12 instances. The problem began on October 31, 2011 at 19:43 UTC and was resolved by 20:25 UTC. Customers on these instances may have experienced slower than normal performance, and a small subset of customers may have experienced intermittent ability to log into the Salesforce application. We apologize for any inconvenience this may have caused you.

Mon, 31 Oct 2011 19:25:00 GMT

The root cause of this incident was isolated to an issue in our network tier that caused a significant increase in traffic utilization. This increase resulted in contention of resources that degraded performance of inbound customer requests. Actions to prevent future incidents: The salesforce.com Technology Team: - Has implemented a work around in our network tier to mitigate this should it happen again. - Is investigating ways to better detect such increases in utilization before it becomes a problem.

Status Update: [na1] NA1 Service Disruption - Resolved

Mon, 17 Oct 2011 23:52:00 GMT

The salesforce.com Technology Team has resolved the service availability issue on the NA1 instance. We apologize for any inconvenience this may have caused you. The root cause of this incident is under investigation.

Status Update: [na1] NA1 Service Disruption - Update #1

Mon, 17 Oct 2011 23:25:00 GMT

The salesforce.com Technology Team continues to work on isolating the service availability issue on the NA1 instance. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] NA1 Service Disruption

Mon, 17 Oct 2011 23:05:00 GMT

Status Update: [na1] NA1 Service Disruption - Resolved

Mon, 17 Oct 2011 22:31:00 GMT

The salesforce.com Technology Team has resolved the service availability issue on the NA1 instance. The problem was resolved as of 22:30 UTC. We apologize for any inconvenience this may have caused you.

Status Update: [na1] NA1 Service Disruption - Update #1

Mon, 17 Oct 2011 22:07:00 GMT

Status Update: [na1] NA1 Performance Degradation

Mon, 17 Oct 2011 21:50:00 GMT

Status Update: [na1] NA1/NA6 - Maintenance Completed

Sun, 16 Oct 2011 02:48:00 GMT

The scheduled maintenance for the NA1 and NA6 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.

Status Update: [na1] NA8/NA9 - Maintenance Beginning

Sun, 16 Oct 2011 02:34:00 GMT

The maintenance for the NA8 and NA9 instances is beginning at 8:00 PM PDT. During this time, the salesforce.com service will not be available. We appreciate your patience during this maintenance window.

Status Update: [na1] NA1/NA6 - Maintenance Beginning

Sun, 16 Oct 2011 01:38:00 GMT

The maintenance for the NA1 and NA6 instances is beginning at 7:00 PM PDT. During this time, the salesforce.com service will not be available. We appreciate your patience during this maintenance window.

Status Update: [na1] NA1 Performance Degradation - Resolved

Tue, 11 Oct 2011 18:50:00 GMT

The Salesforce.com Technology Team has resolved the service disruption on the NA1 instance. The problem began at 15:56 UTC and was resolved as of 18:32 UTC. We apologize for any inconvenience this may have caused you.

Status Update: [na1] NA1 Service Disruption - Update #7

Tue, 11 Oct 2011 18:23:00 GMT

The salesforce.com Technology Team continues to work on isolating the service availability issue on the NA1 instance. Thus far the issue has been mitigated for most customers. The Team will continue to work on resolving this for all customers. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] NA1 Service Disruption - Update #6

Tue, 11 Oct 2011 17:45:00 GMT

Status Update: [na1] NA1 Service Disruption - Update #5

Tue, 11 Oct 2011 17:30:00 GMT

Status Update: [na1] NA1 Service Disruption - Update #4

Tue, 11 Oct 2011 17:10:00 GMT

Status Update: [na1] NA1 Service Disruption - Update #3

Tue, 11 Oct 2011 16:55:00 GMT

Status Update: [na1] NA1 Performance Degradation - Update #2

Tue, 11 Oct 2011 16:48:00 GMT

The salesforce.com Technology Team continues to work on isolating the performance degradation issue on the NA1 instance. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] NA1 Performance Degradation - Update #1

Tue, 11 Oct 2011 16:30:00 GMT

Status Update: [na1] NA1 Performance Degradation

Tue, 11 Oct 2011 16:11:00 GMT

Status Update: [na1] What To Expect During the Winter '12 Release

Sat, 08 Oct 2011 07:06:00 GMT

The Salesforce service will be generally available during the major release upgrade for the Winter '12 release. Your organization should expect to experience a disruption of up to five (5) minutes during the release window. Please reference the Winter '12 Specific Release Maintenance Windows below for timing information. Users will receive an error message informing them that the service is momentarily unavailable while we upgrade it to the latest relaese, and will be prompted to log back in momentarily.

Status Update: [na1] NA1- Scheduled Upgrade Complete

Sat, 08 Oct 2011 07:03:00 GMT

The upgrade activities for the NA1 instance are now complete.

Status Update: [na1] NA1 Sandbox - Scheduled Upgrade Complete

Sat, 08 Oct 2011 06:56:00 GMT

The upgrade activities for the NA1 instance are now complete.

Alert: [na1] On October 08, 2011 beginning at 04:06 hrs UTC the salesforce.com Technology Team detected a service disruption issue affecting the NA1 instance. Normal service was restored at 04:27 hrs UTC. During this period, customers may have experienced an inability to log in to the NA1 instance. We apologize for any inconvenience this may have caused you.

Sat, 08 Oct 2011 06:15:00 GMT

The root cause of this incident is under investigation.

Status Update: [na1] Winter 12 NA1 Update

Sat, 08 Oct 2011 04:38:00 GMT

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

Status Update: [na1] NA1 - Service Restored

Sat, 08 Oct 2011 04:30:00 GMT

On October 08, 2011 beginning at 04:06 hrs UTC the salesforce.com Technology Team detected a service disruption issue affecting the NA1 instance. Normal service was restored at 04:27 hrs UTC. During this period, customers may have experienced an inability to log in to the NA1 instance. We apologize for any inconvenience this may have caused you. The root cause of this incident is under investigation.

Status Update: [na1] NA1 - Service Disruption

Sat, 08 Oct 2011 04:10:00 GMT

The Salesforce.com Technology Team is working to isolate a service availability issue on the NA1 instance. Please check the status of Trust frequently for updates regarding this issue. We apologize for any inconvenience this may be causing you.

Status Update: [na1] Winter 12 NA1 Deployment Start

Sat, 08 Oct 2011 03:06:00 GMT

Status Update: [na1] NA1 Performance Degradation - Search - Update #6

Thu, 01 Jan 1970 00:00:00 GMT

To resolve a previous issue, at 4:17pm PT April 9, 2012, the Technology team restored the search index from an original copy made at 7:00pm PT April 7, 2012. This process then required re-indexing all records added or changed since the time the original copy was made. This re-indexing began at 4:19pm PT April 9, 2012, and at the time there were 69,800 unique organization-objects in need of re-indexing. There are currently 18,609 unique organization-objects left. Re-indexing is proceeding and progress is being made as quickly as possible. It is important that customers do not try to reload their data in an effort to expedite their search capabilities. Doing so will further increase the number of records that need re-indexing, and adversely impact the speed at which we will be able to restore full search indexing. Please note that indexing is expected to proceed more slowly during peak hours than during off-peak hours. Ensuring your success is our top priority at salesforce.com, and we are focused on solving this issue as well as preventing any recurrences. Thank you for continued business and your patience during this situation.