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.

Live Salesforce status100.00% uptime history

Every Recorded Salesforce Incident

Salesforce incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 23, 2026Degradation StartedIncident Resolved-18 minResolved
Aug 21, 2026UpdateIncident Resolved56 minResolved
Aug 21, 2026Degradation StartedIncident Resolved-2 minResolved
Aug 21, 2026Degradation StartedIncident Resolved-9 minResolved
Aug 21, 2026UpdateRollback 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 minResolved
Aug 21, 2026UpdateWe 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 minResolved
Aug 20, 2026UpdateWe’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 minResolved
Aug 20, 2026UpdateWe 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 18mResolved
Aug 20, 2026UpdateWe’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 6mResolved
Aug 20, 2026Degradation StartedIncident Resolved-22 minResolved
Aug 19, 2026UpdateIncident Resolved33 minResolved
Aug 19, 2026Degradation StartedIncident Resolved-26 minResolved
Aug 18, 2026UpdateWe’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 36mResolved
Aug 18, 2026Degradation StartedIncident Resolved14 minResolved
Aug 18, 2026UpdateWe’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 37mResolved
Aug 17, 2026UpdateRolling 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 45mResolved
Aug 17, 2026UpdateThe 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 minResolved
Aug 17, 2026Degradation StartedIncident Resolved-24 minResolved
Aug 15, 2026Degradation StartedIncident Resolved-18 minResolved
Aug 14, 2026Degradation StartedIncident Resolved52 minResolved
Aug 14, 2026Degradation StartedIncident Resolved-24 minResolved
Aug 12, 2026UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.-8 minResolved
Aug 12, 2026UpdateThe 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 13mResolved
Aug 12, 2026Degradation StartedIncident Resolved-18 minResolved
Aug 6, 2026UpdateThe 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 51mResolved
Aug 6, 2026UpdateThe 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 9mResolved
Aug 4, 2026UpdateThe 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 minResolved
Aug 4, 2026UpdateWe’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 54mResolved
Aug 3, 2026Degradation StartedIncident Resolved-18 minResolved
Aug 3, 2026UpdateThe 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 minResolved
Jul 31, 2026UpdateThe 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 minResolved
Jul 31, 2026UpdateAs 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 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 30, 2026Degradation StartedIncident Resolved11 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 30, 2026UpdateWhile 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 minResolved
Jul 29, 2026UpdateWhile 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 minResolved
Jul 29, 2026UpdateAt 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 38mResolved
Jul 28, 2026Degradation StartedIncident Resolved-7 minResolved
Jul 28, 2026Degradation StartedIncident Resolved0 minResolved
Jul 27, 2026Degradation StartedIncident Resolved-24 minResolved
Jul 27, 2026Degradation StartedIncident Resolved-59 minResolved
Jul 26, 2026Degradation StartedIncident Resolved-67 minResolved
Jul 26, 2026UpdateWe 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 minResolved
Jul 26, 2026Degradation StartedIncident Resolved-32 minResolved
Jul 24, 2026Degradation StartedIncident Resolved-31 minResolved
Jul 24, 2026Degradation StartedIncident Resolved-9 minResolved
Jul 24, 2026Disruption StartedIncident Resolved-11 minResolved
Jul 23, 2026UpdateWe 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 minResolved
Jul 22, 2026Degradation StartedIncident Resolved-45 minResolved
Jul 21, 2026Degradation StartedIncident Resolved5 minResolved
Jul 21, 2026Degradation StartedIncident Resolved1h 17mResolved
Jul 21, 2026Degradation StartedIncident Resolved-16 minResolved
Jul 21, 2026Degradation StartedIncident Resolved-26 minResolved
Jul 20, 2026UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.-14 minResolved
Jul 20, 2026UpdateIncident Resolved34 minResolved
Jul 20, 2026Degradation StartedIncident Resolved-17 minResolved
Jul 20, 2026UpdateThe 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 15mResolved
Jul 20, 2026Degradation StartedIncident Resolved21 minResolved
Jul 20, 2026Degradation StartedIncident Resolved-18 minResolved
Jul 17, 2026Disruption StartedIncident Resolved-15 minResolved
Jul 16, 2026Degradation StartedIncident Resolved-38 minResolved
Jul 16, 2026Degradation StartedIncident Resolved-42 minResolved
Jul 16, 2026Degradation StartedIncident Resolved-15 minResolved
Jul 16, 2026UpdateWe'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 minResolved
Jul 15, 2026UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.-12 minResolved
Jul 15, 2026Degradation StartedIncident Resolved1h 6mResolved
Jul 15, 2026Degradation StartedIncident Resolved-10 minResolved
Jul 15, 2026Degradation StartedIncident Resolved-12 minResolved
Jul 14, 2026UpdateA 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 50mResolved
Jul 14, 2026Degradation StartedIncident Resolved-23 minResolved
Jul 14, 2026Degradation StartedIncident Resolved23 minResolved
Jul 14, 2026Degradation StartedIncident Resolved11h 39mResolved
Jul 10, 2026UpdateThe 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 1mResolved
Jul 9, 2026UpdateWe 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 minResolved
Jul 9, 2026UpdateAfter 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 28mResolved
Jul 9, 2026UpdateFurther 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 27mResolved
Jul 8, 2026UpdateOn 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 minResolved
Jul 8, 2026UpdateThe 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 12mResolved
Jul 8, 2026Degradation StartedIncident Resolved-24 minResolved
Jul 8, 2026UpdateCustomers 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 minResolved
Jul 8, 2026UpdateCustomers 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 minResolved
Jul 8, 2026UpdateCustomers 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 minResolved
Jul 8, 2026UpdateCustomers 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 minResolved
Jul 8, 2026UpdateCustomers 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 minResolved
Jul 8, 2026UpdateCustomers 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 minResolved
Jul 8, 2026UpdateCustomers 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 minResolved
Jul 8, 2026UpdateCustomers 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 minResolved
Jul 8, 2026UpdateCustomers 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 minResolved
Jul 8, 2026UpdateWe’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 41mResolved
Jul 8, 2026Degradation StartedIncident Resolved-16 minResolved
Jul 8, 2026Degradation StartedIncident Resolved11 minResolved
Jul 7, 2026Degradation StartedIncident Resolved-36 minResolved
Jul 7, 2026Degradation StartedIncident Resolved-29 minResolved
Jul 7, 2026UpdateIncident Resolved4h 50mResolved
Jul 7, 2026Degradation StartedIncident Resolved1h 40mResolved
Jul 7, 2026UpdateIncident Resolved26h 17mResolved
Jul 7, 2026Degradation StartedIncident Resolved2h 53mResolved
Jul 6, 2026Degradation StartedIncident Resolved-53 minResolved
Jul 6, 2026UpdateAs 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 48mResolved
Jul 6, 2026Disruption StartedIncident Resolved21 minResolved
Jul 6, 2026UpdateThe 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 41mResolved
Jul 6, 2026Degradation StartedIncident Resolved-7 minResolved
Jul 4, 2026Degradation StartedIncident Resolved-24 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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 minResolved
Jul 3, 2026UpdateWe’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…-1348 minResolved
Jul 3, 2026UpdateWe’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…-1406 minResolved
Jul 3, 2026UpdateWe’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…-1476 minResolved
Jul 3, 2026UpdateWe’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…-1526 minResolved
Jul 3, 2026UpdateWe’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…-1582 minResolved
Jul 3, 2026UpdateWe’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…-1637 minResolved
Jul 3, 2026UpdateWe’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…-1695 minResolved
Jul 3, 2026UpdateWe’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…-1774 minResolved
Jul 3, 2026UpdateWe’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…-1811 minResolved
Jul 3, 2026UpdateWe’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…-1869 minResolved
Jul 3, 2026UpdateWe’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…-1930 minResolved
Jul 3, 2026UpdateWe’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…-1985 minResolved
Jul 3, 2026UpdateWe’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…-2044 minResolved
Jul 3, 2026UpdateWe’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…-2103 minResolved
Jul 3, 2026UpdateWe’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…-2161 minResolved
Jul 3, 2026UpdateWe’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…-2226 minResolved
Jul 3, 2026UpdateWe’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…-2275 minResolved
Jul 3, 2026UpdateWe’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…-2335 minResolved
Jul 3, 2026UpdateWe’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…-2393 minResolved
Jul 3, 2026UpdateWe’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…-2449 minResolved
Jul 3, 2026UpdateWe’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…-2508 minResolved
Jul 3, 2026UpdateWe’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…-2555 minResolved
Jul 3, 2026UpdateWe’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…-2600 minResolved
Jul 3, 2026UpdateWe’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…-2654 minResolved
Jul 3, 2026Degradation StartedIncident Resolved-15 minResolved
Jul 3, 2026UpdateRolling restarts have completed, and after a period of monitoring, we can confirm that the incident is resolved as of 01:56 UTC. Users should no longer experience delays or error messages. We apologize for any…1h 32mResolved
Jul 2, 2026Disruption StartedIncident Resolved-19 minResolved
Jul 2, 2026UpdateWe’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…27h 22mResolved
Jul 1, 2026UpdateUpon 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…7h 45mResolved
Jul 1, 2026Degradation StartedIncident Resolved4h 39mResolved
Jun 30, 2026UpdateThe backlog of Event Log Files has successfully been processed to within normal service parameters. The service is now fully operational, and customers should no longer experience abnormal delays in receiving Event Log…16h 10mResolved
Jun 30, 2026Degradation StartedIncident Resolved-38 minResolved
Jun 29, 2026Degradation StartedIncident Resolved-12 minResolved
Jun 29, 2026Degradation StartedIncident Resolved6 minResolved
Jun 26, 2026UpdateAfter further validations and health checks, the issue is now resolved. The team has confirmed that we are out of impact as of 00:08 UTC. We have also revised the start time of the issue to capture the most accurate…10h 56mResolved
Jun 26, 2026UpdateInvestigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about…7 minResolved
Jun 26, 2026Degradation StartedIncident Resolved-15 minResolved
Jun 25, 2026UpdateWe've completed the remediation steps as of 12:00 UTC. After monitoring and validating the service, we can confirm that all affected customers have been brought out of impact. We apologize for how this incident may…3h 41mResolved
Jun 24, 2026Degradation StartedIncident Resolved-35 minResolved
Jun 23, 2026UpdateField Service Mobile customers using Android devices may have received an erroneous message campaign notification from Salesforce. This was a result of internal testing performed by Salesforce which was accidentally…-97 minResolved
Jun 22, 2026UpdateThe 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…29 minResolved
Jun 22, 2026UpdateWe’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.-15 minResolved
Jun 22, 2026Degradation StartedIncident Resolved-39 minResolved
Jun 21, 2026Degradation StartedIncident Resolved-15 minResolved
Jun 20, 2026UpdateIncident Resolved3h 1mResolved
Jun 20, 2026Degradation StartedIncident Resolved-15 minResolved
Jun 20, 2026Degradation StartedIncident Resolved31 minResolved
Jun 19, 2026UpdateThe 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…4h 22mResolved
Jun 19, 2026UpdateThe ability to run Calculated Insights queries is restored. Customers can attempt a manual run of their previously failed scheduled queries or opt to wait for the next scheduled time. We apologize for how you and your…2h 58mResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-164 minResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-171 minResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-145 minResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-130 minResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-149 minResolved
Jun 19, 2026Degradation StartedIncident Resolved-11 minResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-102 minResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-97 minResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-162 minResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-71 minResolved
Jun 19, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-136 minResolved
Jun 19, 2026UpdateWe resolved an issue that was causing Platform Events and Change Data Capture (CDC) events to not be published intermittently on select Salesforce instances. All affected services are now fully operational, and…-130 minResolved
Jun 19, 2026UpdateWe resolved an issue that was causing Platform Events and Change Data Capture (CDC) events to not be published intermittently on select Salesforce instances. All affected services are now fully operational, and…0 minResolved
Jun 19, 2026UpdateWe resolved an issue that was causing Platform Events and Change Data Capture (CDC) events to not be published intermittently on select Salesforce instances. All affected services are now fully operational, and…-107 minResolved
Jun 19, 2026UpdateWe resolved an issue that was causing Platform Events and Change Data Capture (CDC) events to not be published intermittently on select Salesforce instances. All affected services are now fully operational, and…0 minResolved
Jun 19, 2026UpdateWe've resolved an issue impacting Data Cloud CRM Connector Streams containing custom date fields ‌for Data Cloud and Marketing Cloud. The trigger for the issue was traced to a code change introduced in a recent release…4h 7mResolved
Jun 18, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…0 minResolved
Jun 18, 2026Degradation StartedIncident Resolved-40 minResolved
Jun 18, 2026UpdateRestoration efforts with our third-party infrastructure provider continue to move forward. Current information on restoration timelines, milestones, and permanent remediation suggests that completion is expected within…1103h 11mResolved
Jun 18, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-7 minResolved
Jun 18, 2026UpdateSome customers may have experienced an issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and resolved the…-3 minResolved
Jun 18, 2026UpdateWe have identified the trigger that was causing the intermittent timeout issue as a resource constraint. Our teams have increased the necessary resources which has alleviated the impact and mitigated this issue…7 minResolved
Jun 18, 2026UpdateWe have resolved the issue with Service Cloud where agents encountered unexpected pop-ups while working on record pages, disrupting normal agent workflows. We identified the trigger and deployed an updated release to…11h 23mResolved

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 45d 23h, against a mean recovery of 23h 44m. 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.