| Updated 11/7/2009 5:36 am PST |
 |
System Status
|
 |
|
|
|
| 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 |
10/24/09 |
10/23/09 |
10/22/09 |
10/21/09 |
10/20/09 |
10/19/09 |
10/18/09 |
10/17/09 |
10/16/09 |
10/15/09 |
10/14/09 |
10/13/09 |
10/12/09 |
10/11/09 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 49,731,770 |
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 |
90,582,103 |
205,505,825 |
231,027,959 |
230,932,306 |
235,309,334 |
228,477,227 |
79,138,280 |
82,753,309 |
212,561,170 |
225,345,410 |
227,960,893 |
228,082,670 |
202,105,376 |
73,415,976 |
| 0.300 |
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 |
0.269 |
0.304 |
0.288 |
0.296 |
0.286 |
0.328 |
0.246 |
0.252 |
0.288 |
0.304 |
0.302 |
0.297 |
0.270 |
0.229 |
|
| |
| |
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
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
Service Disruption
Time: 10/14/09 11:20 am PDT
Detail: NA0(SSL) Service Disruption
Root cause: On 10/15 starting at 0547 UTC, the Salesforce.com Technology team became aware of a service disruption affecting the NA0(SSL) instance. The disruption was caused by a problem in the routine release deployment. The issue was resolved by 0619 10/15 UTC. We apologize for any inconvenience this may have caused 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/23/09 7:05 am PDT
Detail: NA1 Performance Degradation
Root cause: On 10/23 starting at 13:54 UTC, tthe Salesforce.com Technology team became aware of a service disruption. This was caused by a database resource contention issue. The problem was resolved by 14:05 UTC on 10/23. 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
Service Disruption
Time: 10/14/09 11:20 am PDT
Detail: NA3 Service Disruption
Root cause: On 10/15 starting at 0543 UTC, the Salesforce.com Technology team became aware of a service disruption affecting the NA3 instance. The disruption was caused by a problem in the routine release deployment. The issue was resolved by 0600 10/15 UTC. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Informational Message
Time: 10/22/09 11:16 am PDT
Detail: NA4 Service Disruption
Root cause: On 10/23 starting at 06:08 UTC, the Salesforce.com Technology team became aware of a service disruption affecting the NA4 instance. The problem was isolated to complications experienced while implementing a routine maintenance on the database, and was resolved by 10/23 06:11 UTC. We apologize for any inconvenience this may have caused you.
Informational Message
Time: 10/22/09 11:15 am PDT
Detail: NA4 Service Disruption
Root cause: On 10/23 starting at 05:24 UTC, the Salesforce.com Technology team became aware of a service disruption affecting the NA4 instance. The problem was isolated to complications experienced while implementing a routine maintenance on the database, and was resolved by 10/23 05:25 UTC. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Service Disruption
Time: 10/14/09 11:20 am PDT
Detail: NA4 Service Disruption
Root cause: On 10/15 starting at 0544 UTC, the Salesforce.com Technology team became aware of a service disruption affecting the NA4 instance. The disruption was caused by a problem in the routine release deployment. The issue was resolved by 0604 10/15 UTC. We apologize for any inconvenience this may have caused you.
|
|
| |
| |
| |
Incident Report
Informational Message
Time: 10/15/09 12:07 am PDT
Detail: NA5 Service Disruption
Root cause: On 10/15 starting at 0700 UTC, the Salesforce.com Technology team became aware of a service disruption affecting the NA5 instance. The disruption was caused by a problem in the routine release deployment. The issue was resolved by 0705 10/15 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
Service Disruption
Time: 10/20/09 5:30 pm PDT
Detail: NA6 Service Disruption
Root cause: On 10/20/2009 starting at 2219 hrs UTC, the salesforce.com Technology team became aware of a service availability issue affecting the NA6 instance. Customers may have received occasional maintenance redirects and login failures. The salesforce.com Technology team worked to isolate the issue and service was restored at 10/21/2009 0014 hrs UTC.
Although the salesforce.com Technology team is still working to understand what could have caused the issue, we have in place temporary mechanisms that should avoid further occurrence of the problem. Corrective actions will be taken when the cause is fully understood to ensure that it is addressed appropriately. We apologize for any inconvenience caused.
|
|
| |
| |
| |
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.
|
|
| |
|
Informational message
Status not available