Time: 8/26/08 3:45 am PDT

Detail: NA1 Internal Server Errors between 2137 UTC and 2245 UTC

Root cause: Starting on August 26, 2008 at 2137 UTC, customers on the NA1 instance may have experienced intermittent service disruptions. Users may have experienced trouble logging in or received internal server error messages. An issue in the system cache required a system restart. All systems were fully operational at 22:45 UTC.

Time: 8/25/08 11:32 pm PDT

Detail: NA1 Service Disruption from 0632 UTC to 0636 UTC on August 26th, 2008

Root cause: Starting on August 26th at 0632 UTC, customers on the NA1 instance experienced a service disruption lasting 4 minutes. The issue was determined to be a process failure causing the NA1 database to stop accepting transactions. Automated redundancy mechanisms worked to isolate the issue and restored normal service at 0636 UTC.
We apologize for any inconvenience this may have caused you.

Time: 8/22/08 5:42 pm PDT

Detail: NA4 Internal Server Errors between 0042 UTC to 0138 UTC on Saturday August 23, 2008.


Root cause: On 8/23/2008 at 0042 UTC, a very small subset of users on the NA4 instance may have experienced intermittent internal server error messages. Login and other services were available during this time. An issue in the system cache required a system restart. All systems were fully operational at 0138 UTC.

Time: 8/21/08 6:42 pm PDT

Detail: NA5 Internal Server Errors between 0142 UTC to 0247 UTC on Friday August 22, 2008.


Root cause: On 8/22/2008 at 0142 UTC, a very small subset of users on the NA5 instance may have experienced intermittent internal server error messages. Login and other services were available during this time. An issue in the system cache required a system restart. All systems were fully operational at 0247 UTC.

Time: 8/20/08 4:22 pm PDT

Detail: NA2 Intermittent Performance Degradation from 2322 UTC to 2327 UTC on Wednesday August 20, 2008.


Root cause: On 8/20/2008 at 2222 UTC, users on the NA2 instance may have experienced a performance degradation or login issues. A memory problem in the application tier required server restarts. Further root cause analysis is pending. All systems were fully operational at 2327 UTC.

Time: 8/16/08 7:00 pm PDT

Detail: AP0 (Japan) Performance Degradation from 02:00 UTC to 06:00 UTC.

Root cause: Starting at 02:00 UTC on August 17th, 2008, search indexing on the AP0 (Japan) instance was delayed resulting in users not seeing new data or data changes reflected in search results until 06:00 UTC due to a configuration error during the scheduled maintenance on the NA1 and NA6 instances. All new data and data changes were successfully indexed after 06:00 UTC and available in search results.

Time: 7/31/08 8:24 pm PDT

Detail: NA0 Search Performance Degradation from 15:24 UTC to 16:17 UTC on July 31, 2007

Root cause: On 7/31/2008 at 15:24 UTC, power issues resulted in the shutdown for some of our NA0 query systems. While this resulted in performance degradation for sidebar search for the NA0 users, no other Salesforce services were impacted by this event. During the 53 minutes of degradation, we were systematically bringing back, testing and validating server configurations. All systems were fully operational at 16:17 UTC.

Time: 7/31/08 8:24 pm PDT

Detail: NA6 Search Performance Degradation from 15:24 UTC to 16:17 UTC on July 31, 2007

Root cause: On 7/31/2008 at 15:24 UTC, power issues resulted in the shutdown for some of our NA6 query systems. While this resulted in performance degradation for sidebar search for the NA6 users, no other Salesforce services were impacted by this event. During the 53 minutes of degradation, we were systematically bringing back, testing and validating server configurations. All systems were fully operational at 16:17 UTC.