Salesforce Outage History
200 incidents recorded over the last 365 days, 200 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Salesforce Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 10, 2026 | Degradation StartedIncident Resolved | 14 min | Resolved |
| Oct 10, 2026 | Degradation StartedIncident Resolved | 6 min | Resolved |
| Oct 9, 2026 | UpdateWe’ve investigated and confirmed resolution of a third party performance degradation that impacted multiple Salesforce instances. Impacted customers may have experienced latency and errors. We apologize for how this… | 37 min | Resolved |
| Oct 8, 2026 | UpdateInvestigations 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… | 1h 56m | Resolved |
| Oct 8, 2026 | Degradation StartedIncident Resolved | 1h 19m | Resolved |
| Oct 8, 2026 | UpdateWe’ve resolved an issue affecting CRM Analytics recipe runs for a number of customers, preventing recipes from completing successfully. We rolled back the affected service to a prior stable version, and recipe runs have… | 14h 21m | Resolved |
| Oct 7, 2026 | Degradation StartedIncident Resolved | 59 min | Resolved |
| Oct 6, 2026 | UpdateThe Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any… | 1 min | Resolved |
| Oct 6, 2026 | Degradation StartedIncident Resolved | 15 min | Resolved |
| Oct 6, 2026 | UpdateThe cached metadata has now been cleared. After a period of monitoring, we have confirmed that access to Data Lake Objects is restored for all affected customers. We apologize for the impact on our customers and their… | 39h 45m | Resolved |
| Oct 5, 2026 | UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. | 12 min | Resolved |
| Oct 5, 2026 | Degradation StartedIncident Resolved | 6 min | Resolved |
| Oct 4, 2026 | UpdateWe increased capacity on the affected internal services and restarted them, which restored normal operation at 00:25 UTC on October 5, 2026. CRM Analytics recipe runs and Data 360 segmentation tasks are running… | 12h 45m | Resolved |
| Oct 2, 2026 | UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. | 7 min | Resolved |
| Oct 2, 2026 | UpdateIncident Resolved | 43 min | Resolved |
| Oct 1, 2026 | UpdateThe issue affecting .mil network connectivity to some Salesforce GovCloud environments was resolved as of 14:50 UTC on October 2, 2026. Connectivity has remained stable during monitoring, and affected customers are no… | 18h 18m | Resolved |
| Oct 1, 2026 | Degradation StartedIncident Resolved | 7h 32m | Resolved |
| Sep 30, 2026 | Degradation StartedIncident Resolved | 16 min | Resolved |
| Sep 29, 2026 | UpdateThe issue affecting Data 360 streaming ingestion in a subset of environments has been resolved, after the service's capacity was increased. We apologize for how this incident affected you and your business. We'll… | 2h 10m | Resolved |
| Sep 28, 2026 | Degradation StartedIncident Resolved | 6 min | Resolved |
| Sep 28, 2026 | Degradation StartedIncident Resolved | 10 min | Resolved |
| Sep 25, 2026 | UpdateBetween 20:55 UTC on September 25 and 18:46 UTC on September 26, customers using the Microsoft Teams connector may have been unable to authenticate or maintain their connection. Our team traced the issue to an expired… | 21h 51m | Resolved |
| Sep 25, 2026 | UpdateUpon 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… | 4h 38m | Resolved |
| Sep 23, 2026 | Degradation StartedIncident Resolved | 6 min | Resolved |
| Sep 22, 2026 | Degradation StartedIncident Resolved | 6 min | Resolved |
| Sep 22, 2026 | Degradation StartedIncident Resolved | 39 min | Resolved |
| Sep 21, 2026 | UpdateAll previously impacted instances recovered and performance returned to normal levels. We identified increased database session activity as the trigger and remapped the impacted instances to a newly scaled cache cluster… | 2h 19m | Resolved |
| Sep 19, 2026 | UpdateWe’ve confirmed that the solution implemented to mitigate the issue causing the feature disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no… | 14h 11m | Resolved |
| Sep 18, 2026 | UpdateDuring our investigation we’ve identified some instances to have a different scope of impact as initially understood and communicated in the supplemental Trust post: https://status.salesforce.com/incidents/20004434. As… | -3726 min | Resolved |
| Sep 18, 2026 | UpdateDuring our investigation we’ve identified some instances to have a different scope of impact as initially understood and communicated in the supplemental Trust post: https://status.salesforce.com/incidents/20004434… | -3706 min | Resolved |
| Sep 17, 2026 | Degradation StartedIncident Resolved | -13 min | Resolved |
| Sep 16, 2026 | UpdateIncident Resolved | -79 min | Resolved |
| Sep 16, 2026 | UpdateWe have observed that the impact on service health has decreased from a disrupted to a degraded state. We have amended the posting to reflect this and have highlighted the approximate timings of this transition. | -234 min | Resolved |
| Sep 16, 2026 | UpdateAs our teams investigated the incident further, we discovered that sandboxes were not impacted. To accurately reflect impact, we have updated this post to remove these instances. We apologize for any confusion this may… | 6h 53m | Resolved |
| Sep 16, 2026 | Degradation StartedIncident Resolved | -30 min | Resolved |
| Sep 14, 2026 | Degradation StartedIncident Resolved | -17 min | Resolved |
| Sep 14, 2026 | Degradation StartedIncident Resolved | -15 min | Resolved |
| Sep 9, 2026 | Degradation StartedIncident Resolved | -7 min | Resolved |
| Sep 9, 2026 | Degradation StartedIncident Resolved | -35 min | Resolved |
| Sep 8, 2026 | UpdateUpon further investigation, we've determined that the start and end 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… | -2644 min | Resolved |
| Sep 8, 2026 | UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. | -30 min | Resolved |
| Sep 8, 2026 | UpdateWe applied manual fixes across all known affected environments, restoring transaction processing by 05:24 UTC. We also tested an automated, fleet-wide update to fully resolve the issue for the remaining affected… | 45 min | Resolved |
| Sep 8, 2026 | UpdateWe've resolved an issue that prevented Revenue Cloud customers from adding new products and saving quotes. We developed a fix, validated that it resolved the issue, and deployed it to all impacted instances. This… | -133 min | Resolved |
| Sep 8, 2026 | UpdateWe've resolved an issue that prevented Revenue Cloud customers from adding new products and saving quotes. We developed a fix, validated that it resolved the issue, and deployed it to all impacted instances. This… | -110 min | Resolved |
| Sep 8, 2026 | UpdateWe've resolved an issue that prevented Revenue Cloud customers from adding new products and saving quotes. We developed a fix, validated that it resolved the issue, and deployed it to all impacted instances. This… | -166 min | Resolved |
| Sep 8, 2026 | UpdateWe've resolved an issue that prevented Revenue Cloud customers from adding new products and saving quotes. We developed a fix, validated that it resolved the issue, and deployed it to all impacted instances. This… | -222 min | Resolved |
| Sep 8, 2026 | UpdateWe've resolved an issue that prevented Revenue Cloud customers from adding new products and saving quotes. We developed a fix, validated that it resolved the issue, and deployed it to all impacted instances. This… | -295 min | Resolved |
| Sep 7, 2026 | UpdateWe've resolved an issue that prevented Revenue Cloud customers from adding new products and saving quotes. We developed a fix, validated that it resolved the issue, and deployed it to all impacted instances. This… | -101 min | Resolved |
| Sep 7, 2026 | UpdateWe've resolved an issue that prevented Revenue Cloud customers from adding new products and saving quotes. We developed a fix, validated that it resolved the issue, and deployed it to all impacted instances. This… | -203 min | Resolved |
| Sep 7, 2026 | UpdateWe've resolved an issue that prevented Revenue Cloud customers from adding new products and saving quotes. We developed a fix, validated that it resolved the issue, and deployed it to all impacted instances. This… | -296 min | Resolved |
| Sep 7, 2026 | UpdateIncident Resolved | 1h 33m | Resolved |
| Sep 7, 2026 | UpdateThe Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical… | 18h 59m | Resolved |
| Sep 5, 2026 | Degradation StartedIncident Resolved | -40 min | Resolved |
| Sep 5, 2026 | UpdateAt 11: 11 UTC, on September 05, 2026, the team declared an all-clear after validating the services and performing the health checks. We apologize for how you and your business may have been affected by this incident. | 7h 15m | Resolved |
| Sep 4, 2026 | UpdateWe identified an issue impacting scheduled jobs where a user without the “View Setup” permission would receive a permissions error message when attempting to run a scheduled job. We performed a configuration change, and… | 9 min | Resolved |
| Sep 4, 2026 | UpdateIncident Resolved | 6h 19m | Resolved |
| Sep 4, 2026 | UpdateAs of 17:58 UTC, September 2, a subset of customers using Data Cloud services may have been impacted by an issue when using batch transforms, and may have seen completed jobs remain in an outdated status in the user… | -100 min | Resolved |
| Sep 3, 2026 | UpdateWe've resolved this issue. We developed an updated fix addressing both the original regression and the additional impact. We deployed the updated fix and confirmed that jobs queued during the incident resumed processing… | 6h 39m | Resolved |
| Sep 3, 2026 | UpdateThe Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any… | -70 min | Resolved |
| Sep 3, 2026 | UpdateWe investigated an issue affecting a subset of Industries Cloud customers using OmniStudio in production and sandbox environments. Affected customers couldn’t load or save changes in OmniScripts and FlexCards… | -56 min | Resolved |
| Sep 3, 2026 | UpdateWe investigated an issue affecting a subset of Industries Cloud customers using OmniStudio in production and sandbox environments. Affected customers couldn’t load or save changes in OmniScripts and FlexCards… | -136 min | Resolved |
| Sep 3, 2026 | UpdateUpon further investigation, we've determined that rolling back to the previous state has resolved this issue for all affected production and sandbox instances as of 17:50 UTC. OmniScripts and FlexCards are now loading… | 8h 18m | Resolved |
| Sep 3, 2026 | UpdateAs of 01:33 UTC on September 3, 2026, we deployed the fix and resolved the Standard Coupon Code component issue affecting Commerce Store (Lightning Web Runtime, LWR). Guest users on these instances can now see and apply… | -238 min | Resolved |
| Sep 2, 2026 | UpdateWe’ve resolved the issue affecting a subset of sandbox and production environments where users experienced their sessions expiring shortly after signing in, requiring them to authenticate again. We deployed a… | 18 min | Resolved |
| Sep 2, 2026 | UpdateWe’ve resolved an issue affecting Agentforce Contact Center where transcriptions for calls routed to human agents were unavailable. Calls, call recordings, and bot-transcriptions for Agentforce-handled conversations… | -116 min | Resolved |
| Sep 2, 2026 | Degradation StartedIncident Resolved | 1h 53m | Resolved |
| Sep 1, 2026 | UpdateWe identified an issue affecting the standard coupon code component on B2B Commerce Store pages, where guest users could not see it on the Cart page. We've completed deploying a fix across all affected instances. The… | 124h 58m | Resolved |
| Sep 1, 2026 | UpdateThe issue affecting Record-Triggered Flows calling Agentforce agents in impacted sandbox environments was resolved as of 19:00 UTC. Following successful validation of the Emergency Release, we completed the phased… | 8h 24m | Resolved |
| Sep 1, 2026 | Degradation StartedIncident Resolved | -73 min | Resolved |
| Sep 1, 2026 | Degradation StartedIncident Resolved | -19 min | Resolved |
| Aug 30, 2026 | UpdateIncident Resolved | 16h 21m | Resolved |
| Aug 28, 2026 | Degradation StartedIncident Resolved | -42 min | Resolved |
| Aug 23, 2026 | Degradation StartedIncident Resolved | -18 min | Resolved |
| Aug 21, 2026 | UpdateIncident Resolved | 56 min | Resolved |
| Aug 21, 2026 | Degradation StartedIncident Resolved | -2 min | Resolved |
| Aug 21, 2026 | Degradation StartedIncident Resolved | -9 min | Resolved |
| Aug 21, 2026 | UpdateRollback has been completed and customers using chatbots, custom agents, or Salesforce agents connecting through the Salesforce MCP Server, are no longer experiencing errors when their agent tries to query or update… | 17 min | Resolved |
| Aug 21, 2026 | UpdateWe investigated an issue affecting Private Connect services that caused degraded connectivity to Salesforce services for some customers. We identified a recent change as the likely trigger. We implemented the required… | -48 min | Resolved |
| Aug 20, 2026 | UpdateWe’ve completed the site switch and, after a period of monitoring, can confirm that services have been restored with an out of impact time of 00:22 UTC, August 21. This is the final update for this incident. | 43 min | Resolved |
| Aug 20, 2026 | UpdateWe have completed the deployment addressing intermittent timeouts for Private Connect inbound calls across all impacted instances. The normal call behavior has been restored for the affected customers. We apologize for… | 62h 18m | Resolved |
| Aug 20, 2026 | UpdateWe’ve resolved the issue affecting Revenue Cloud. We applied the remediation across affected environments, restoring functionality for customers who experienced 400 errors when performing actions such as quoting… | 4h 6m | Resolved |
| Aug 20, 2026 | Degradation StartedIncident Resolved | -22 min | Resolved |
| Aug 19, 2026 | UpdateIncident Resolved | 33 min | Resolved |
| Aug 19, 2026 | Degradation StartedIncident Resolved | -26 min | Resolved |
| Aug 18, 2026 | UpdateWe’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information. | 2h 36m | Resolved |
| Aug 18, 2026 | Degradation StartedIncident Resolved | 14 min | Resolved |
| Aug 18, 2026 | UpdateWe’ve resolved the issue affecting Data 360 provisioning in sandbox environments. After validating the corrected configuration in an affected environment, we deployed the update more broadly and confirmed that sandbox… | 6h 37m | Resolved |
| Aug 17, 2026 | UpdateRolling restarts completed for all impacted instances at 19:54 UTC, and we have verified that the issue affecting Proactive Monitoring limit alerts has been resolved. We apologize for how you and your business may have… | 1h 45m | Resolved |
| Aug 17, 2026 | UpdateThe issue affecting some Salesforce Industries customers using OmniStudio deployment tooling was resolved as of 16:08 UTC on August 16. Customers may have experienced failures when deploying, importing, or exporting… | -1450 min | Resolved |
| Aug 17, 2026 | Degradation StartedIncident Resolved | -24 min | Resolved |
| Aug 15, 2026 | Degradation StartedIncident Resolved | -18 min | Resolved |
| Aug 14, 2026 | Degradation StartedIncident Resolved | 52 min | Resolved |
| Aug 14, 2026 | Degradation StartedIncident Resolved | -24 min | Resolved |
| Aug 12, 2026 | UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. | -8 min | Resolved |
| Aug 12, 2026 | UpdateThe issue impacting global search and login availability has been resolved. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the… | 3h 13m | Resolved |
| Aug 12, 2026 | Degradation StartedIncident Resolved | -18 min | Resolved |
| Aug 6, 2026 | UpdateThe Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical… | 1h 51m | Resolved |
| Aug 6, 2026 | UpdateThe impacted services have returned to normal functionality following a restart of the affected host. Engineering teams have confirmed that we are now out of impact. We apologize for how this incident affected you and… | 3h 9m | Resolved |
| Aug 4, 2026 | UpdateThe Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any… | -131 min | Resolved |
| Aug 4, 2026 | UpdateWe’ve resolved an issue affecting Einstein Bots where event log data was unavailable in Report Explorer for a subset of customers. Following rolling restarts of all impacted instances, the Einstein bot service is… | 2h 54m | Resolved |
| Aug 3, 2026 | Degradation StartedIncident Resolved | -18 min | Resolved |
| Aug 3, 2026 | UpdateThe Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any… | -939 min | Resolved |
| Jul 31, 2026 | UpdateThe Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any… | -950 min | Resolved |
| Jul 31, 2026 | UpdateAs of 11:50 UTC on August 4, no recurrence has been observed for more than 48 hours, confirming third-party integration tools are stable following service restarts. A long term fix is scheduled for deployment during… | 6 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -8316 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -8190 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -8027 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -7939 min | Resolved |
| Jul 30, 2026 | Degradation StartedIncident Resolved | 11 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -7844 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -7707 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -7689 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -7676 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -7665 min | Resolved |
| Jul 30, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -7656 min | Resolved |
| Jul 29, 2026 | UpdateWhile we previously indicated this issue was resolved after deploying an update, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively… | -7101 min | Resolved |
| Jul 29, 2026 | UpdateAt 20:01 UTC on July 24, 2026, a feature degradation began impacting Lightning report exports. Customers with the Report Export Transaction Security Policy enabled encountered a repeated authentication loop when… | 66h 38m | Resolved |
| Jul 28, 2026 | Degradation StartedIncident Resolved | -7 min | Resolved |
| Jul 28, 2026 | Degradation StartedIncident Resolved | 0 min | Resolved |
| Jul 27, 2026 | Degradation StartedIncident Resolved | -24 min | Resolved |
| Jul 27, 2026 | Degradation StartedIncident Resolved | -59 min | Resolved |
| Jul 26, 2026 | Degradation StartedIncident Resolved | -67 min | Resolved |
| Jul 26, 2026 | UpdateWe have resolved the Performance Degradation that began at 06:25 UTC, July 26, 2026, impacting customers on USA364 instance. The issue was caused by a faulty infrastructure node, which affected caching services and led… | -62 min | Resolved |
| Jul 26, 2026 | Degradation StartedIncident Resolved | -32 min | Resolved |
| Jul 24, 2026 | Degradation StartedIncident Resolved | -31 min | Resolved |
| Jul 24, 2026 | Degradation StartedIncident Resolved | -9 min | Resolved |
| Jul 24, 2026 | Disruption StartedIncident Resolved | -11 min | Resolved |
| Jul 23, 2026 | UpdateWe can confirm that the email log retrieval issue has been resolved. Between 05:18 UTC and 11:50 UTC on July 23, 2026, a subset of customers may have been unable to retrieve email logs, with requests failing with… | 18 min | Resolved |
| Jul 22, 2026 | Degradation StartedIncident Resolved | -45 min | Resolved |
| Jul 21, 2026 | Degradation StartedIncident Resolved | 5 min | Resolved |
| Jul 21, 2026 | Degradation StartedIncident Resolved | 1h 17m | Resolved |
| Jul 21, 2026 | Degradation StartedIncident Resolved | -16 min | Resolved |
| Jul 21, 2026 | Degradation StartedIncident Resolved | -26 min | Resolved |
| Jul 20, 2026 | UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. | -14 min | Resolved |
| Jul 20, 2026 | UpdateIncident Resolved | 34 min | Resolved |
| Jul 20, 2026 | Degradation StartedIncident Resolved | -17 min | Resolved |
| Jul 20, 2026 | UpdateThe maintenance activity is complete, and service has been restored. All validations are complete, and services are operating as expected. We apologize for how this incident affected you and your business. We'll… | 4h 15m | Resolved |
| Jul 20, 2026 | Degradation StartedIncident Resolved | 21 min | Resolved |
| Jul 20, 2026 | Degradation StartedIncident Resolved | -18 min | Resolved |
| Jul 17, 2026 | Disruption StartedIncident Resolved | -15 min | Resolved |
| Jul 16, 2026 | Degradation StartedIncident Resolved | -38 min | Resolved |
| Jul 16, 2026 | Degradation StartedIncident Resolved | -42 min | Resolved |
| Jul 16, 2026 | Degradation StartedIncident Resolved | -15 min | Resolved |
| Jul 16, 2026 | UpdateWe're aware of an issue that affected a subset of customers where search index builds triggered between 21:45 UTC on July 14 and 00:32 UTC on July 16 are stuck in the ‘submitted’ status. We've implemented a fix to… | -65 min | Resolved |
| Jul 15, 2026 | UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information. | -12 min | Resolved |
| Jul 15, 2026 | Degradation StartedIncident Resolved | 1h 6m | Resolved |
| Jul 15, 2026 | Degradation StartedIncident Resolved | -10 min | Resolved |
| Jul 15, 2026 | Degradation StartedIncident Resolved | -12 min | Resolved |
| Jul 14, 2026 | UpdateA fix to disable routing to the degraded speech recognition endpoint was deployed to the impacted environments. We've confirmed service has been restored after monitoring performance and completing all health checks… | 1h 50m | Resolved |
| Jul 14, 2026 | Degradation StartedIncident Resolved | -23 min | Resolved |
| Jul 14, 2026 | Degradation StartedIncident Resolved | 23 min | Resolved |
| Jul 14, 2026 | Degradation StartedIncident Resolved | 11h 39m | Resolved |
| Jul 10, 2026 | UpdateThe rollback has been completed on all production impacted instances and services have been restored. The incident start time has been updated on Trust to reflect the revised timeline identified during our… | 3h 1m | Resolved |
| Jul 9, 2026 | UpdateWe investigated an issue where multiple Salesforce instances were temporarily impacted. This issue resulted from necessary remediation efforts for a separate ongoing incident (Trust link… | -21 min | Resolved |
| Jul 9, 2026 | UpdateAfter monitoring performance and completing health checks, the team has confirmed that services have been restored, following the successful deployment of the fix that was identified as the trigger for the… | 40h 28m | Resolved |
| Jul 9, 2026 | UpdateFurther investigations have confirmed that JPN4S, JPN8S, JPN24S, JPN154S, JPN172S, JPN182S, JPN184S, and KOR4S weren't impacted by this incident. We are removing these instances from the Trust post and apologize for any… | 1h 27m | Resolved |
| Jul 8, 2026 | UpdateOn July 8, 2026, beginning at 21:17 UTC, we became aware of an issue impacting Salesforce services in our European region. During the impact window, customers may have experienced delays when accessing their instances… | -13 min | Resolved |
| Jul 8, 2026 | UpdateThe Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any… | 1h 12m | Resolved |
| Jul 8, 2026 | Degradation StartedIncident Resolved | -24 min | Resolved |
| Jul 8, 2026 | UpdateCustomers using Salesforce Lightning via the latest versions of Chrome and Microsoft Edge experienced an issue where primary field values weren't rendering in the Dynamic Highlights Panel on record pages. This prevented… | -1486 min | Resolved |
| Jul 8, 2026 | UpdateCustomers using Salesforce Lightning via the latest versions of Chrome and Microsoft Edge experienced an issue where primary field values weren't rendering in the Dynamic Highlights Panel on record pages. This prevented… | -595 min | Resolved |
| Jul 8, 2026 | UpdateCustomers using Salesforce Lightning via the latest versions of Chrome and Microsoft Edge experienced an issue where primary field values weren't rendering in the Dynamic Highlights Panel on record pages. This prevented… | -935 min | Resolved |
| Jul 8, 2026 | UpdateCustomers using Salesforce Lightning via the latest versions of Chrome and Microsoft Edge experienced an issue where primary field values weren't rendering in the Dynamic Highlights Panel on record pages. This prevented… | -760 min | Resolved |
| Jul 8, 2026 | UpdateCustomers using Salesforce Lightning via the latest versions of Chrome and Microsoft Edge experienced an issue where primary field values weren't rendering in the Dynamic Highlights Panel on record pages. This prevented… | -544 min | Resolved |
| Jul 8, 2026 | UpdateCustomers using Salesforce Lightning via the latest versions of Chrome and Microsoft Edge experienced an issue where primary field values weren't rendering in the Dynamic Highlights Panel on record pages. This prevented… | -642 min | Resolved |
| Jul 8, 2026 | UpdateCustomers using Salesforce Lightning via the latest versions of Chrome and Microsoft Edge experienced an issue where primary field values weren't rendering in the Dynamic Highlights Panel on record pages. This prevented… | -1535 min | Resolved |
| Jul 8, 2026 | UpdateCustomers using Salesforce Lightning via the latest versions of Chrome and Microsoft Edge experienced an issue where primary field values weren't rendering in the Dynamic Highlights Panel on record pages. This prevented… | -875 min | Resolved |
| Jul 8, 2026 | UpdateCustomers using Salesforce Lightning via the latest versions of Chrome and Microsoft Edge experienced an issue where primary field values weren't rendering in the Dynamic Highlights Panel on record pages. This prevented… | -1650 min | Resolved |
| Jul 8, 2026 | UpdateWe’ve successfully completed the rollout of the fix to all affected GovCloud environments. We have validated that this has resolved the issue and customers should see the Agentforce agent functioning as expected. We… | 20h 41m | Resolved |
| Jul 8, 2026 | Degradation StartedIncident Resolved | -16 min | Resolved |
| Jul 8, 2026 | Degradation StartedIncident Resolved | 11 min | Resolved |
| Jul 7, 2026 | Degradation StartedIncident Resolved | -36 min | Resolved |
| Jul 7, 2026 | Degradation StartedIncident Resolved | -29 min | Resolved |
| Jul 7, 2026 | UpdateIncident Resolved | 4h 50m | Resolved |
| Jul 7, 2026 | Degradation StartedIncident Resolved | 1h 40m | Resolved |
| Jul 7, 2026 | UpdateIncident Resolved | 26h 17m | Resolved |
| Jul 7, 2026 | Degradation StartedIncident Resolved | 2h 53m | Resolved |
| Jul 6, 2026 | Degradation StartedIncident Resolved | -53 min | Resolved |
| Jul 6, 2026 | UpdateAs of 23:35 UTC, July 3, 2026, we have completed the rollback across all impacted instances and validated remediation efforts. We apologize for how this incident affected you and your business. We will undertake a full… | 4h 48m | Resolved |
| Jul 6, 2026 | Disruption StartedIncident Resolved | 21 min | Resolved |
| Jul 6, 2026 | UpdateThe rollback has been completed successfully. After monitoring performance and completing health checks, the team has confirmed that services have been restored as of 11:00 UTC, for all impacted instances. We'll… | 3h 41m | Resolved |
| Jul 6, 2026 | Degradation StartedIncident Resolved | -7 min | Resolved |
| Jul 4, 2026 | Degradation StartedIncident Resolved | -24 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -174 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -331 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -361 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -414 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -479 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -534 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -676 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -708 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -825 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -911 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -958 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -1018 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -1087 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -1130 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -1182 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -1240 min | Resolved |
| Jul 3, 2026 | UpdateWe’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully… | -1290 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Salesforce incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Salesforce Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Salesforce acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Salesforce outage in this window ran 5d 4h, against a mean recovery of 7h 42m. If you depend on Salesforce in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.