Saturday July 5, 2008 | 10:51 am PDT

10:00 am PDT : AP0 Maintenance Commencing
The scheduled work for AP0 has begun.
|
Service Performance History †

|
Date
|
Number of Transactions
|
Avg. Speed*
(seconds)
|
|
| 07/04/08
|
78,349,072
|
0.283
|
|
|
|
|
|
|
|
|
| 07/03/08
|
128,097,409
|
0.301
|
|
|
|
|
|
|
|
|
| 07/02/08
|
140,644,049
|
0.322
|
|
|
|
|
|
|
|
|
| 07/01/08
|
144,232,223
|
0.325
|
|
|
|
|
|
|
|
|
| 06/30/08
|
142,865,237
|
0.332
|
|
|
|
|
|
|
|
|
| 06/29/08
|
50,382,788
|
0.204
|
|
|
|
|
|
|
|
|
| 06/28/08
|
41,830,928
|
0.207
|
| |
| |
Incident Report
 Service Disruption
Time: 6/28/08 8:52 am PDT
Detail: Salesforce.com Service Disruption from 15:32 UTC to 15:52 UTC on June 28th, 2008
Root cause: On June 28th, 2008 from 15:32 UTC to 15:52 UTC the Salesforce.com Technology team isolated a service availability issue which affected AP0. During this period users may have been unable to log in to the service. The problem has been isolated to an issue with the database clustering software. The technology team is performing a review of the incident and will take any corrective action needed. We apologize for any inconvenience this may have caused you.
|
|
| |
|
|
|
|
|
|
|
|
| 06/27/08
|
120,917,162
|
0.306
|
|
|
|
|
|
|
|
|
| 06/26/08
|
140,498,248
|
0.351
|
|
|
|
|
| |
| |
Incident Report
 Informational Message
Time: 6/26/08 12:01 pm PDT
Detail: NA2 intermittent service unavailable messages from 7:30AM PDT to 8:46AM PDT
Root cause: On June 26, 2008 7:30AM PDT to 8:46AM PDT users of the NA2 instance may have seen intermittent "internal server error" messages when accessing accounts or contacts. This error was caused by memory errors experienced on a single server and this server was removed and restored to working condition at 8:46AM PDT. The Salesforce Technology team is continuing to investigate the source of the memory errors to prevent recurrence in the future. We apologize for any inconvenience this may have caused you.
|
|
| |
|
|
|
| |
| |
Incident Report
 Service Disruption
Time: 6/26/08 1:51 pm PDT
Detail: Salesforce.com Service Disruption from 20:51 UTC to 21:04 UTC June 26, 2008
Root cause: Salesforce.com Service Disruption from 20:51 UTC to 21:04 UTC June 26, 2008 On June 26, 2008 from 20:51 UTC to 21:04 UTC, customers may not have been able to log into the application. The root cause of this issue was hardware failure at the database level. The faulty system was isolated from service and log in was fully restored by 21:04 UTC. The failed component was replaced and service was restored to full capacity at 05:42 UTC on June 27, 2008. We apologize for any inconvenience this may have caused you. NA5 Service Degradation Search Function from 01:20 UTC to 18:49 UTC June 26, 2008 On June 26, 2008 at 1:20 UTC, a configuration issue introduced during capacity expansion maintenance introduced performance degradation and intermittent unavailability of Search functions for NA5 users. No other Salesforce.com services were impacted by this event. The Salesforce.com technology team worked to isolate the issue and restored the service at 18:49 UTC. We apologize for any inconvenience this may have caused you.
|
|
| |
|
| 06/25/08
|
142,507,929
|
0.317
|
|
|
|
|
|
|
|
|
| 06/24/08
|
144,292,657
|
0.302
|
|
|
|
|
|
|
|
|
| 06/23/08
|
145,573,832
|
0.316
|
|
|
|
|
|
|
|
|
| 06/22/08
|
50,958,757
|
0.201
|
|
|
|
|
|
|
|
|
| 06/21/08
|
50,583,179
|
0.185
|
|
|
|
| |
| |
Incident Report
 Service Disruption
Time: 6/21/08 9:30 am PDT
Detail: NA1 Service Disruption - Extended Maintenance
Root cause: On 6/22/2008 07:00 UTC, users on the NA1 instance experienced an extended down time due to our need to extend the 6/22/2008 02:00 to 07:00 planned maintenance. The maintenance ran over by 2 hours, service was available by 09:00 UTC on 6/22/2008. Users would not have been able to login to the NA1 or NA6 instances during this time. We apologize for any inconvenience this may have caused you.
|
|
| |
|
|
|
|
|
| 06/20/08
|
122,867,317
|
0.300
|
|
|
|
|
|
|
|
|
| 06/19/08
|
139,126,895
|
0.328
|
|
|
|
|
|
|
|
|
| 06/18/08
|
141,757,356
|
0.320
|
|
|
|
|
|
|
|
|
| 06/17/08
|
142,950,189
|
0.341
|
|
|
|
|
|
|
|
|
| 06/16/08
|
144,536,039
|
0.349
|
|
|
|
|
|
|
|
|
| 06/15/08
|
58,893,385
|
0.224
|
|
|
|
|
|
|
|
|
| 06/14/08
|
49,362,197
|
0.201
|
|
|
|
|
|
|
|
|
| 06/13/08
|
124,578,940
|
0.305
|
|
|
|
|
|
|
|
|
| 06/12/08
|
144,769,131
|
0.300
|
|
|
|
|
|
|
|
|
| 06/11/08
|
145,409,035
|
0.313
|
|
|
|
|
| |
| |
Incident Report
 Informational Message
Time: 6/11/08 9:24 am PDT
Detail: Performance Degradation
Root cause: On 6/11/2008 at 19:46 UTC, a power issue caused a shutdown for some of our NA2 query systems. While this resulted in a performance degradation for sidebar search and Content accessibility for the NA2 users, no other Salesforce services were impacted by this event. During the 72 minutes of degradation, we were systematically bringing back, testing and validating server configurations. All systems were fully operational at 20:58 UTC.
|
|
| |
|
|
| |
| |
Incident Report
 Informational Message
Time: 6/11/08 9:26 am PDT
Detail: Performance Degradation
Root cause: On 6/11/2008 at 19:46 UTC, a power issue caused a shutdown for some of our NA4 query systems. While this resulted in a performance degradation for sidebar search for the NA4 users, no other Salesforce services were impacted by this event. During the 72 minutes of degradation, we were systematically bringing back, testing and validating server configurations. All systems were fully operational at 20:58 UTC.
|
|
| |
|
|
| 06/10/08
|
147,394,816
|
0.303
|
|
|
|
|
|
|
|
|
| 06/09/08
|
147,693,435
|
0.302
|
|
|
|
|
|
|
|
|
| 06/08/08
|
54,156,516
|
0.216
|
|
|
|
|
|
|
|
|
| 06/07/08
|
49,116,730
|
0.209
|
|
|
|
|
|
|
|
|
 |
 |
|
Instance available |
|
 |
|
Performance issues |
|
 |
|
Service disruption |
|
 |
|
Informational message |
|
 |
|
Status not available |
|
 |
|
|