Salesforce outage history and live incidents

We’ve confirmed that the solution implemented to mitigate the issue causing the performance degradation was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident. Update: We’ve confirmed that the solution implemented to mitigate the issue causing the performance degradation was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.

Please note the previous updates to the incident refer the status page here :https://status.salesforce.com/incidents/20004512

We have resolved an issue that prevented users from logging in. We identified an issue with a recent release that prevented login sessions from being created. We deployed a fix forward, and access is now restored. Users can log in and open their orgs again. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. The fix-forward deployment continues to progress across the remaining instance. Users on instance awaiting the fix may continue to experience issues logging in or accessing their orgs. We will provide our next update in 30 minutes, or sooner if additional information becomes available. The fix-forward deployment continues to progress across the remaining instances. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available. The fix-forward deployment continues to progress well, bringing additional impacted instances closer to recovery. Our teams remain focused on completing the rollout across the remaining instances. We're continuing to provide recovery confirmation and accurate resolved timestamps for instances via separate postings. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available. We have verified that instances IND116, USA326, USA938s, and USA1230 were not affected by this incident and have removed it from the list of impacted instances. As a result, these instances will no longer receive incident-related communications. We will continue to provide updates for the remaining impacted instances as we work toward full recovery. We apologize for any confusion caused by the earlier inclusion of this instance. The fix-forward deployment continues to progress well, bringing additional impacted instances closer to recovery. Our teams remain focused on completing the rollout across the remaining instances and validating that users can successfully log in and access their orgs. As we confirm recovery, we continue to update the incident scope and remove recovered instances from the main incident post to accurately reflect their respective impact end times. We will communicate recovery through instance-specific updates. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available. We continue to make steady progress with the fix-forward deployment across the remaining impacted instances. Our teams are actively rolling out the fix-forward and verifying that users can successfully log in and access their orgs as each instance recovers. As we confirm recovery, we are removing the affected instances from the main incident post to accurately reflect their respective impact end times. We will continue to share instance-specific updates as we validate recovery. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. Although the deployment is progressing as expected, we do not yet have an estimated time for full recovery. Restoring access across all remaining impacted instances remains our highest priority. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Our investigation has confirmed that the scope of impact is narrower than initially identified. We have verified that instance USA594 was not affected by this incident and have removed it from the list of impacted instances. As a result, this instance will no longer receive incident-related communications. We will continue to provide updates for the remaining impacted instances as we work toward full recovery. We apologize for any confusion caused by the earlier inclusion of this instance. The fix-forward deployment is progressing well across the remaining impacted instances, and our teams continue to prioritize restoring access as quickly as possible. We are closely monitoring the rollout and validating recovery as each instance receives the updated version. We have removed recovered instances from the main incident post to accurately reflect their respective impact end times. We will continue to provide instance-specific recovery updates as deployment progresses. Users on instances that have not yet received the fix may continue to experience issues logging in or accessing their orgs. While deployment is progressing, we do not yet have an estimated time for full recovery. We will provide our next update in 30 minutes, or sooner if additional information becomes available. We continue to prioritize restoring access across all remaining impacted instances. We are actively deploying the identified fix across multiple instances, with the fix-forward deployment remaining our path to full recovery. The rollout is still in progress, and we are closely monitoring deployment progress and validating recovery as each instance receives the updated version. While we are working to complete the rollout as quickly as possible, we do not yet have an estimated time for full recovery. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs .We will post separate updates as each impacted instance recovers and provide our next update in 30 minutes, or sooner if additional information becomes available. We have identified the fix-forward deployment as our path to full recovery and are expediting its rollout across all remaining impacted instances. Deployment is currently underway across multiple instances, and we do not yet have an estimated time for completion. Users on instances that have not received the updated version may continue to experience issues logging in or accessing their orgs. We will post separate updates as each impacted instance recovers and provide our next update in 30 minutes, or sooner if additional information becomes available. We confirmed that a fix forward has restored access on the second impacted instance USA1072 at 04:11 UTC. We're now preparing to deploy this fix forward to the remaining impacted instances. Users on the remaining impacted instances may continue to experience login failures or be unable to access their orgs. We'll post a separate Trust update for each instance that receives the fix, so each shows an accurate end time We'll provide an update in 30 minutes or sooner if additional information becomes available. We confirmed that we restored access on one impacted instance by rolling back a recent application update. At 03:57 UTC, we began deploying a newer version to a second impacted instance to validate the fix. Once validation is complete, we plan to roll out the fix to the remaining impacted instances. Users on the remaining impacted instances may continue to experience login failures or be unable to access their orgs. We’ll provide the next update within 30 minutes, or sooner if new information becomes available. Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. We’ve identified a mismatch between a recent application update and a database change, stopping users from logging in. We’re planning to roll back the update across impacted instances. We’re also preparing to test a newer version on one of impacted instance to validate whether it restores user access. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. Affected users can't log in, and attempts to open orgs return an internal server error. We're continuing to investigate the trigger. We'll provide an update in 30 minutes or sooner if additional information becomes available. Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. We've confirmed that affected users can't log in to their org and see an error message. We began restarting our servers in stages to restore access. We're continuing to investigate the cause. We'll provide an update in 30 minutes, or sooner if additional information becomes available. Update: We have resolved an issue that prevented users from logging in. We identified an issue with a recent release that prevented login sessions from being created. We deployed a fix forward, and access is now restored. Users can log in and open their orgs again. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: The fix-forward deployment continues to progress across the remaining instance. Users on instance awaiting the fix may continue to experience issues logging in or accessing their orgs. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Update: The fix-forward deployment continues to progress across the remaining instances. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Update: The fix-forward deployment continues to progress well, bringing additional impacted instances closer to recovery. Our teams remain focused on completing the rollout across the remaining instances. We're continuing to provide recovery confirmation and accurate resolved timestamps for instances via separate postings. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Update: We have verified that instances IND116, USA326, USA938s, and USA1230 were not affected by this incident and have removed it from the list of impacted instances. As a result, these instances will no longer receive incident-related communications. We will continue to provide updates for the remaining impacted instances as we work toward full recovery. We apologize for any confusion caused by the earlier inclusion of this instance. Update: The fix-forward deployment continues to progress well, bringing additional impacted instances closer to recovery. Our teams remain focused on completing the rollout across the remaining instances and validating that users can successfully log in and access their orgs. As we confirm recovery, we continue to update the incident scope and remove recovered instances from the main incident post to accurately reflect their respective impact end times. We will communicate recovery through instance-specific updates. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. While we are making consistent progress toward full recovery, we do not yet have an estimated time for completion. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Update: We continue to make steady progress with the fix-forward deployment across the remaining impacted instances. Our teams are actively rolling out the fix-forward and verifying that users can successfully log in and access their orgs as each instance recovers. As we confirm recovery, we are removing the affected instances from the main incident post to accurately reflect their respective impact end times. We will continue to share instance-specific updates as we validate recovery. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs. Although the deployment is progressing as expected, we do not yet have an estimated time for full recovery. Restoring access across all remaining impacted instances remains our highest priority. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Update: Our investigation has confirmed that the scope of impact is narrower than initially identified. We have verified that instance USA594 was not affected by this incident and have removed it from the list of impacted instances. As a result, this instance will no longer receive incident-related communications. We will continue to provide updates for the remaining impacted instances as we work toward full recovery. We apologize for any confusion caused by the earlier inclusion of this instance. Update: The fix-forward deployment is progressing well across the remaining impacted instances, and our teams continue to prioritize restoring access as quickly as possible. We are closely monitoring the rollout and validating recovery as each instance receives the updated version. We have removed recovered instances from the main incident post to accurately reflect their respective impact end times. We will continue to provide instance-specific recovery updates as deployment progresses. Users on instances that have not yet received the fix may continue to experience issues logging in or accessing their orgs. While deployment is progressing, we do not yet have an estimated time for full recovery. We will provide our next update in 30 minutes, or sooner if additional information becomes available. Update: We continue to prioritize restoring access across all remaining impacted instances. We are actively deploying the identified fix across multiple instances, with the fix-forward deployment remaining our path to full recovery. The rollout is still in progress, and we are closely monitoring deployment progress and validating recovery as each instance receives the updated version. While we are working to complete the rollout as quickly as possible, we do not yet have an estimated time for full recovery. Users on instances awaiting the fix may continue to experience issues logging in or accessing their orgs .We will post separate updates as each impacted instance recovers and provide our next update in 30 minutes, or sooner if additional information becomes available. Update: We have identified the fix-forward deployment as our path to full recovery and are expediting its rollout across all remaining impacted instances. Deployment is currently underway across multiple instances, and we do not yet have an estimated time for completion. Users on instances that have not received the updated version may continue to experience issues logging in or accessing their orgs. We will post separate updates as each impacted instance recovers and provide our next update in 30 minutes, or sooner if additional information becomes available. Update: We confirmed that a fix forward has restored access on the second impacted instance USA1072 at 04:11 UTC. We're now preparing to deploy this fix forward to the remaining impacted instances. Users on the remaining impacted instances may continue to experience login failures or be unable to access their orgs. We'll post a separate Trust update for each instance that receives the fix, so each shows an accurate end time We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: We confirmed that we restored access on one impacted instance by rolling back a recent application update. At 03:57 UTC, we began deploying a newer version to a second impacted instance to validate the fix. Once validation is complete, we plan to roll out the fix to the remaining impacted instances. Users on the remaining impacted instances may continue to experience login failures or be unable to access their orgs. We’ll provide the next update within 30 minutes, or sooner if new information becomes available. Update: Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. Update: We’ve identified a mismatch between a recent application update and a database change, stopping users from logging in. We’re planning to roll back the update across impacted instances. We’re also preparing to test a newer version on one of impacted instance to validate whether it restores user access. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: Affected users can't log in, and attempts to open orgs return an internal server error. We're continuing to investigate the trigger. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: We've confirmed that affected users can't log in to their org and see an error message. We began restarting our servers in stages to restore access. We're continuing to investigate the cause. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

Please note the previous updates to the incident refer the status page here :https://status.salesforce.com/incidents/20004512

Please note the previous updates to the incident refer the status page here :https://status.salesforce.com/incidents/20004512

Please note the previous updates to the incident refer the status page here :https://status.salesforce.com/incidents/20004512

Please note the previous updates to the incident refer the status page here :https://status.salesforce.com/incidents/20004512

Please note the previous updates to the incident refer the status page here :https://status.salesforce.com/incidents/20004512

Please note the previous updates to the incident refer the status page here :https://status.salesforce.com/incidents/20004512

Please note the previous updates to the incident refer the status page here :https://status.salesforce.com/incidents/20004512

Please refer to the following post for updates during the course of this impact:https://status.salesforce.com/incidents/20004512

Please refer to the following post for updates during the course of this impact:https://status.salesforce.com/incidents/20004512

Scheduled jobs for some Government Cloud customers, which were running about 7 hours later than configured, are now running at their configured times. The issue was linked to a time zone setting on the affected servers. We corrected the setting and restarted the affected servers, and validation confirmed the fix. Some customers may see duplicate runs of scheduled jobs caused by the restarts. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We're aware of an issue affecting Runtime Manager in the Government Cloud environment. Schedules for some customers are running about 7 hours later than configured. The issue is linked to a time zone setting on the affected servers. We have corrected the time zone settings and are restarting the affected servers. We're monitoring to confirm schedules return to their configured times and will provide an update in 60 minutes or as more information becomes available. Update: Scheduled jobs for some Government Cloud customers, which were running about 7 hours later than configured, are now running at their configured times. The issue was linked to a time zone setting on the affected servers. We corrected the setting and restarted the affected servers, and validation confirmed the fix. Some customers may see duplicate runs of scheduled jobs caused by the restarts. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: We're aware of an issue affecting Runtime Manager in the Government Cloud environment. Schedules for some customers are running about 7 hours later than configured. The issue is linked to a time zone setting on the affected servers. We have corrected the time zone settings and are restarting the affected servers. We're monitoring to confirm schedules return to their configured times and will provide an update in 60 minutes or as more information becomes available.

We've resolved an incident where a subset of customers using certain third-party hosted artificial intelligence (AI) models in Prompt Builder and prompt templates received errors when submitting requests. Service has recovered, and these features are available again. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: We've resolved an incident where a subset of customers using certain third-party hosted artificial intelligence (AI) models in Prompt Builder and prompt templates received errors when submitting requests. Service has recovered, and these features are available again. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. Update: We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

Agentforce Coworker is now operating at normal service levels. Requests are completing successfully again. Error rates returned to normal after a third-party service provider recovered their services. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this. We're aware of an issue impacting Agentforce Coworker. A subset of customers may experience intermittent request failures, and conversations may stop partway through an answer without an error message. We engaged the third-party service provider, and we're seeing error rates decrease. We’ll provide an update in 30 minutes or sooner if additional information becomes available. Update: Agentforce Coworker is now operating at normal service levels. Requests are completing successfully again. Error rates returned to normal after a third-party service provider recovered their services. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this. Update: We're aware of an issue impacting Agentforce Coworker. A subset of customers may experience intermittent request failures, and conversations may stop partway through an answer without an error message. We engaged the third-party service provider, and we're seeing error rates decrease. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

During this time Agentforce Coworker may have been unresponsive for some customers. The issue was linked to reduced availability of a third-party service that Coworker relies on. That service has recovered, and Agentforce Coworker is now operating normally. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: During this time Agentforce Coworker may have been unresponsive for some customers. The issue was linked to reduced availability of a third-party service that Coworker relies on. That service has recovered, and Agentforce Coworker is now operating normally. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Marketing Cloud Engagement customers on the affected databases experienced a service disruption that prevented logins and access to features requiring database connectivity. We restarted the affected database servers to restore service, validated recovery, and rebalanced the databases to maintain stability We apologize for the impact this incident may have had on your customers and their businesses. We’ill complete a full investigation to confirm the technical trigger and underlying cause, and to identify actions that prevent a recurrence. Update: Marketing Cloud Engagement customers on the affected databases experienced a service disruption that prevented logins and access to features requiring database connectivity. We restarted the affected database servers to restore service, validated recovery, and rebalanced the databases to maintain stability We apologize for the impact this incident may have had on your customers and their businesses. We’ill complete a full investigation to confirm the technical trigger and underlying cause, and to identify actions that prevent a recurrence.

We restored email delivery by rolling back a recent change to an email service component. Customers now receive all new password reset and one-time passcode (OTP) emails. Some delayed emails remain queued, and we're flushing those queues so it delivers sooner. We'll perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident. We're investigating a login issue where customers aren't receiving any outbound emails, including password reset emails and one-time passcodes (OTPs). This is preventing logins. We've identified a recent change to an email service component as the likely trigger. We're reverting the change to restore email delivery. We'll provide an update in 30 minutes or sooner if additional information becomes available. Update: We restored email delivery by rolling back a recent change to an email service component. Customers now receive all new password reset and one-time passcode (OTP) emails. Some delayed emails remain queued, and we're flushing those queues so it delivers sooner. We'll perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident. Update: We're investigating a login issue where customers aren't receiving any outbound emails, including password reset emails and one-time passcodes (OTPs). This is preventing logins. We've identified a recent change to an email service component as the likely trigger. We're reverting the change to restore email delivery. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We’ve investigated and resolved an issue where Identity Resolution was not completing normally. Customers using the affected feature saw errors, and new data was not being populated in the unified profile table. Existing data remained usable. We traced the trigger to a recent release, and deployed a fix. Identity Resolution is now operating normally. We apologize for the impact this incident had on you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. Update: We’ve investigated and resolved an issue where Identity Resolution was not completing normally. Customers using the affected feature saw errors, and new data was not being populated in the unified profile table. Existing data remained usable. We traced the trigger to a recent release, and deployed a fix. Identity Resolution is now operating normally. We apologize for the impact this incident had on you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.