| Updated 11/21/2009 10:27 pm PST |
 |
System Status
|
 |
|
|
|
| 11/21/09 |
11/20/09 |
11/19/09 |
11/18/09 |
11/17/09 |
11/16/09 |
11/15/09 |
11/14/09 |
11/13/09 |
11/12/09 |
11/11/09 |
11/10/09 |
11/09/09 |
11/08/09 |
11/07/09 |
11/06/09 |
11/05/09 |
11/04/09 |
11/03/09 |
11/02/09 |
11/01/09 |
10/31/09 |
10/30/09 |
10/29/09 |
10/28/09 |
10/27/09 |
10/26/09 |
10/25/09 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 88,946,152 |
222,543,678 |
236,173,371 |
236,421,952 |
241,098,613 |
231,564,240 |
77,350,467 |
88,074,403 |
225,425,642 |
236,693,421 |
231,758,308 |
241,062,927 |
235,089,421 |
78,778,228 |
92,051,601 |
225,601,826 |
235,775,520 |
232,596,949 |
229,061,507 |
229,759,167 |
82,504,501 |
95,108,965 |
222,117,865 |
227,335,429 |
231,895,026 |
226,809,664 |
231,829,079 |
82,555,895 |
| 0.265 |
0.298 |
0.334 |
0.331 |
0.331 |
0.321 |
0.256 |
0.259 |
0.293 |
0.325 |
0.323 |
0.304 |
0.335 |
0.296 |
0.289 |
0.313 |
0.306 |
0.356 |
0.343 |
0.338 |
0.274 |
0.301 |
0.318 |
0.300 |
0.327 |
0.307 |
0.309 |
0.259 |
|
| |
| |
Informational Report
Informational Message
Detail: No incidents to report.
|
|
| |
| |
| |
What System Are You Using?
The instance your organization uses is indicated in the browser's Address bar, shown
highlighted below.
|
|
| |
Service Performance History is updated four times daily. Today's date may reflect partial day's data.
Salesforce.com service transaction speed. Your on-site page load times may vary based on your
bandwidth and network latency. |
|
|
In the Service Performance History matrix, each indicator will be blue with a white "i"
for issues that last longer than 10 minutes,
and red for disruptions that last longer than 30 minutes.
For incidents of less than 10 minutes, please click on the i for more information.
|
| |
| |
Incident Report
Performance Degradation
Time: 11/12/09 11:30 pm PST
Detail: EU0 Performance Degradation
Root cause: On 11/12/2009 starting at 18:05 UTC, the Salesforce.com Technology team became aware of a performance degradation affecting the EU0 instance. The root cause is under investigation at this time. The degradation was resolved by 18:19 UTC. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Informational Message
Time: 10/28/09 4:34 am PDT
Detail: EMEA Performance Degradation
Root cause: The Salesforce.com Technology Team has resolved the performance degradation issue on the EMEA instance. The problem began at 09:40 PDT and was resolved as of 10:58 PDT. We apologize for any inconvenience this may be causing you.
|
|
| |
| |
| |
Incident Report
Informational Message
Time: 10/27/09 10:10 am PDT
Detail: NA1 Service Disruption
Root cause: On 10/27 at 1710 UTC, the Salesforce.com Technology team became aware of a service disruption. The problem was resolved at 1713 UTC. This was caused by a database resource contention issue. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Informational Message
Time: 10/26/09 5:50 am PDT
Detail: NA3 Performance Degradation
Root cause: On 10/26 starting at 12:41 UTC, the Salesforce.com Technology team became aware of a performance degradation affecting the NA3 instance. The problem was resolved as of 12:49 UTC. During this time, some customers may have experienced slowness within the app, or difficulties logging in. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Performance Degradation
Time: 11/11/09 3:38 pm PST
Detail: NA6 Performance Degradation
Root cause: On 11/11/2009 starting at 17:30 UTC, the Salesforce.com Technology team became aware of a performance degradation affecting content, file attachment, and document operations for the NA6 instance. The root cause is under investigation at this time. The degradation was resolved by 20:40 UTC. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Performance Degradation
Time: 11/3/09 12:15 pm PST
Detail: NA6 Performance Degradation
Root cause: On 11/3 starting at 19:52 UTC, the Salesforce.com Technology team became aware of a performance degradation affecting the NA6 instance. During this event, customers may have experienced intermittent slowness or errors. The problem was resolved by 20:12 UTC. We apologize for any incovenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Performance Degradation
Time: 11/9/09 11:12 pm PST
Detail: NA7 Performance Degradation
Root cause: On 11/10/2009 at 02:36 UTC, the Salesforce.com Technology team became aware of a performance degradation affecting content, file attachment, and document operations for the NA7 instance. The problem was isolated to a configuration error and was resolved by 07:12 UTC. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Informational Message
Time: 11/10/09 4:01 pm PST
Detail: CS0 Performance Degradation
Root cause: On 11/11/2009 starting at 00:01 UTC, the Salesforce.com Technology team became aware of a performance degradation affecting the CS0 Sandbox instance. The root cause is under investigation at this time. The degradation was resolved by 00:06 UTC. We apologize for any inconvenience this may have caused you.
Performance Degradation
Time: 11/10/09 1:17 pm PST
Detail: CS0 Performance Degradation
Root cause: On 11/10/2009 starting at 19:19 UTC, the Salesforce.com Technology team became aware of a performance degradation affecting the CS0 Sandbox instance. The root cause is under investigation at this time. The degradation was resolved by 19:32 UTC. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Performance Degradation
Time: 10/28/09 10:42 am PDT
Detail: CS0 (Sandbox) Performance Degradation
Root cause: On 10/28 at 1738 UTC, the Salesforce.com Technology team became aware of a performance degradation. The problem was resolved at 1742 UTC. This was caused by a database resource contention issue. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Service Disruption
Time: 11/15/09 1:55 pm PST
Detail: CS1 scheduled maintenance extended
Root cause: On 11/15/2009 0500hrs UTC, service availability on the Sandbox (CS1) instances was affected due to a maintenance extension. The Salesforce.com Technology team worked to isolate the issue and service was restored for CS1 at 0605 hrs. We apologize for the maintenance extension and any inconvenience caused.
|
|
| |
| |
| |
Incident Report
Service Disruption
Time: 11/15/09 1:59 pm PST
Detail: CS3 scheduled maintenance extended
Root cause: On 11/15/2009 0500hrs UTC, service availability on the Sandbox (CS3) instance was affected due to a maintenance extension. The Salesforce.com Technology team worked to isolate the issue and service was restored for CS3 at 0541 hrs. We apologize for the maintenance extension and any inconvenience caused.
|
|
| |
|
Informational message
Status not available