{"key":"USA1","location":"NA","environment":"production","releaseVersion":"Summer '26 Patch 14.19","releaseNumber":"262.14.19","status":"OK","isActive":true,"createdAt":"2020-08-14T20:23:30.280Z","updatedAt":"2026-09-20T08:45:23.625Z","city":"","stateName":"","stateCode":"","countryName":"","countryCode":"","maintenanceWindow":"Sundays 12:00 AM - 4:00 AM PST","Services":[{"key":"Agentforce","order":2,"isCore":false},{"key":"analytics","order":10,"isCore":false},{"key":"B2B2CCommerce","order":1400,"isCore":false},{"key":"B2BCommerce","order":1300,"isCore":false},{"key":"Communities","order":200,"isCore":false},{"key":"coreService","order":1,"isCore":true},{"key":"CPQandBilling","order":100,"isCore":false},{"key":"Customer360Audiences","order":500,"isCore":false},{"key":"EinsteinBots","order":110,"isCore":false},{"key":"liveAgent","order":20,"isCore":false},{"key":"MCGrowth","order":1600,"isCore":false},{"key":"PromptStudio","order":3,"isCore":false},{"key":"SalesforceCMS","order":1200,"isCore":false},{"key":"SALESFORCEORDERMANAGEMENT","order":1210,"isCore":false},{"key":"SalesforceUnifiedMessaging","order":1450,"isCore":false},{"key":"ServiceCloudMessagingChannels","order":1500,"isCore":false},{"key":"ServiceCloudVoice","order":600,"isCore":false},{"key":"FieldServiceMobile","order":1700,"isCore":false},{"key":"FieldServiceScheduling","order":1720,"isCore":false},{"key":"FieldServiceCorePlatform","order":1730,"isCore":false},{"key":"FieldServiceVRA","order":1750,"isCore":false},{"key":"search","order":7,"isCore":false},{"key":"AgentforceContactCenter","order":4,"isCore":false},{"key":"AgentforceVoice","order":5,"isCore":false}],"Products":[{"key":"Salesforce_Services","order":0,"isActive":true,"name":"Salesforce Services","altDisplayName":"Sales and Service","url":"/products/Salesforce_Services"}],"Incidents":[{"id":20004366,"externalId":"94329705","message":{"rootCause":null,"actionPlan":null,"pathToResolution":null},"additionalInformation":"","isCore":true,"affectsAll":true,"status":"Resolved","type":"Degradation","createdAt":"2026-08-20T12:58:43.749Z","updatedAt":"2026-08-20T18:17:30.920Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"IncidentImpacts":[{"id":20004695,"startTime":"2026-08-20T09:00:00.000Z","endTime":"2026-08-20T17:05:00.000Z","type":"featurePerfDegradation","severity":"minor","createdAt":"2026-08-20T12:58:43.920Z","updatedAt":"2026-08-20T18:17:30.891Z","startTimeCreatedAt":"2026-08-20T12:58:43.920Z","startTimeModifiedAt":"2026-08-20T14:06:09.229Z","endTimeCreatedAt":"2026-08-20T18:17:30.892Z","endTimeModifiedAt":null}],"IncidentEvents":[{"id":20005880,"type":"update","message":"We’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, ordering, and configuring products. \n\nWe 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.","createdAt":"2026-08-20T18:17:30.910Z","updatedAt":"2026-08-20T18:17:30.914Z"},{"id":20005879,"type":"update","message":"We’ve applied the remediation across the affected environments, and monitoring indicates that Revenue Cloud functionality is returning to normal. Customers may begin to see functionality restored and improvements in their experience as the remediation takes effect.\n\nWe’re completing remediation in additional environments as a precautionary measure and continuing to monitor and validate recovery.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T18:02:02.549Z","updatedAt":"2026-08-20T18:02:02.554Z"},{"id":20005878,"type":"update","message":"The configuration change we validated is restoring Revenue Cloud functionality, and we’ve now applied the remediation across multiple affected environments. We’re continuing remediation efforts across the remaining environments while monitoring recovery.\n\nWe'll provide an update in 60 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T17:26:35.006Z","updatedAt":"2026-08-20T17:26:35.010Z"},{"id":20005877,"type":"update","message":"We've successfully validated a configuration change that resolved the errors affecting Revenue Cloud functionality in a test environment. We're now applying this change across the remaining affected environments, with recovery progressing as the remediation is completed.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.\n","createdAt":"2026-08-20T16:51:54.554Z","updatedAt":"2026-08-20T16:51:54.557Z"},{"id":20005876,"type":"update","message":"Our investigation has identified a recent deployment to a related service as the likely trigger of the Revenue Cloud issue. We're preparing changes to restore the previous configuration across affected environments and are validating the remediation approach before proceeding.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T16:18:55.274Z","updatedAt":"2026-08-20T16:18:55.278Z"},{"id":20005875,"type":"update","message":"Reverting the configuration change didn't resolve the issue. However, we've identified another recent change that aligns with the start of the impact and are deploying an update on an affected environment to validate whether it restores Revenue Cloud functionality.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T15:51:09.920Z","updatedAt":"2026-08-20T15:51:09.925Z"},{"id":20005874,"type":"update","message":"We're testing changes to the configuration identified in our investigation to determine whether they restore affected Revenue Cloud functionality. In parallel, we're continuing to investigate other configuration changes that align with the start of the impact.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T15:24:09.437Z","updatedAt":"2026-08-20T15:24:09.442Z"},{"id":20005873,"type":"update","message":"Our investigation has highlighted that a recent configuration change seems to align with the start time of the impact. We're currently focused on testing if reverting the configuration change resolves the issue. \n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T14:54:06.159Z","updatedAt":"2026-08-20T14:54:06.164Z"},{"id":20005872,"type":"update","message":"The rollback of the recent release on a test instance has been completed. However,‌ the issue still persists. We're continuing to work with additional teams to check whether a recent configuration changes may instead be the trigger of the issue.  \n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T14:45:15.115Z","updatedAt":"2026-08-20T14:45:15.120Z"},{"id":20005871,"type":"update","message":"We’ve run into issues performing the rollback on test instances and are attempting to workaround these issues. Additional teams have joined the investigation and are analyzing whether their configurations may have resulted in the issue experienced by customers.\n \nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T14:30:53.506Z","updatedAt":"2026-08-20T14:30:53.511Z"},{"id":20005870,"type":"update","message":"We’re examining whether a separate configuration issue may be the trigger of the issue. The rollback of the recent change is still underway and we're continuing to monitor it’s progress.\n\nWe've also 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.\n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T14:06:09.235Z","updatedAt":"2026-08-20T14:06:09.241Z"},{"id":20005869,"type":"update","message":"We’re continuing to monitor the rollback of the recent release on the test instance. In parallel, we are investigating whether there are other actions that can be taken to bring customers out of impact, and additional teams are being engaged. \n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T13:53:10.098Z","updatedAt":"2026-08-20T13:53:10.103Z"},{"id":20005868,"type":"update","message":"The rollback of the recent release on a test instance is still underway. We're continuing to monitor the progress. If this proves successful, the release will be rolled back in all instances which received it. Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. \n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T13:30:19.013Z","updatedAt":"2026-08-20T13:30:19.019Z"},{"id":20005867,"type":"update","message":"We've identified a recent release which may be the trigger of the issue. We're in the process of rolling back the release on a test instance to see if this resolves the issue.\n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T13:08:54.172Z","updatedAt":"2026-08-20T13:08:54.176Z"},{"id":20005866,"type":"update","message":"We’re investigating a feature degradation impacting Revenue Cloud. Customers may receive 400 errors when performing actions such as quoting, ordering and configuring products. We're continuing to narrow down the scope of impact and will update our messaging to reflect this as we learn more. We're engaging additional teams, and we’ll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-08-20T13:00:11.455Z","updatedAt":"2026-08-20T13:00:11.460Z"}],"timeline":[{"title":"Update","content":"We’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, ordering, and configuring products. \n\nWe 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.","createdAt":"2026-08-20T18:17:30.910Z","updatedAt":"2026-08-20T18:17:30.914Z","entryType":"event","sourceId":20005880,"sourceType":"event"},{"title":"Resolved","content":"Incident Resolved","createdAt":"2026-08-20T18:17:30.892Z","updatedAt":null,"entryType":"impact_end","endTime":"2026-08-20T17:05:00.000Z","sourceId":20004695,"sourceType":"impact","impactStartTime":"2026-08-20T12:58:43.920Z"},{"title":"Update","content":"We’ve applied the remediation across the affected environments, and monitoring indicates that Revenue Cloud functionality is returning to normal. Customers may begin to see functionality restored and improvements in their experience as the remediation takes effect.\n\nWe’re completing remediation in additional environments as a precautionary measure and continuing to monitor and validate recovery.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T18:02:02.549Z","updatedAt":"2026-08-20T18:02:02.554Z","entryType":"event","sourceId":20005879,"sourceType":"event"},{"title":"Update","content":"The configuration change we validated is restoring Revenue Cloud functionality, and we’ve now applied the remediation across multiple affected environments. We’re continuing remediation efforts across the remaining environments while monitoring recovery.\n\nWe'll provide an update in 60 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T17:26:35.006Z","updatedAt":"2026-08-20T17:26:35.010Z","entryType":"event","sourceId":20005878,"sourceType":"event"},{"title":"Update","content":"We've successfully validated a configuration change that resolved the errors affecting Revenue Cloud functionality in a test environment. We're now applying this change across the remaining affected environments, with recovery progressing as the remediation is completed.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.\n","createdAt":"2026-08-20T16:51:54.554Z","updatedAt":"2026-08-20T16:51:54.557Z","entryType":"event","sourceId":20005877,"sourceType":"event"},{"title":"Update","content":"Our investigation has identified a recent deployment to a related service as the likely trigger of the Revenue Cloud issue. We're preparing changes to restore the previous configuration across affected environments and are validating the remediation approach before proceeding.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T16:18:55.274Z","updatedAt":"2026-08-20T16:18:55.278Z","entryType":"event","sourceId":20005876,"sourceType":"event"},{"title":"Update","content":"Reverting the configuration change didn't resolve the issue. However, we've identified another recent change that aligns with the start of the impact and are deploying an update on an affected environment to validate whether it restores Revenue Cloud functionality.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T15:51:09.920Z","updatedAt":"2026-08-20T15:51:09.925Z","entryType":"event","sourceId":20005875,"sourceType":"event"},{"title":"Update","content":"We're testing changes to the configuration identified in our investigation to determine whether they restore affected Revenue Cloud functionality. In parallel, we're continuing to investigate other configuration changes that align with the start of the impact.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-20T15:24:09.437Z","updatedAt":"2026-08-20T15:24:09.442Z","entryType":"event","sourceId":20005874,"sourceType":"event"},{"title":"Update","content":"Our investigation has highlighted that a recent configuration change seems to align with the start time of the impact. We're currently focused on testing if reverting the configuration change resolves the issue. \n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T14:54:06.159Z","updatedAt":"2026-08-20T14:54:06.164Z","entryType":"event","sourceId":20005873,"sourceType":"event"},{"title":"Update","content":"The rollback of the recent release on a test instance has been completed. However,‌ the issue still persists. We're continuing to work with additional teams to check whether a recent configuration changes may instead be the trigger of the issue.  \n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T14:45:15.115Z","updatedAt":"2026-08-20T14:45:15.120Z","entryType":"event","sourceId":20005872,"sourceType":"event"},{"title":"Update","content":"We’ve run into issues performing the rollback on test instances and are attempting to workaround these issues. Additional teams have joined the investigation and are analyzing whether their configurations may have resulted in the issue experienced by customers.\n \nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T14:30:53.506Z","updatedAt":"2026-08-20T14:30:53.511Z","entryType":"event","sourceId":20005871,"sourceType":"event"},{"title":"Update","content":"We’re examining whether a separate configuration issue may be the trigger of the issue. The rollback of the recent change is still underway and we're continuing to monitor it’s progress.\n\nWe've also 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.\n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T14:06:09.235Z","updatedAt":"2026-08-20T14:06:09.241Z","entryType":"event","sourceId":20005870,"sourceType":"event"},{"title":"Update","content":"We’re continuing to monitor the rollback of the recent release on the test instance. In parallel, we are investigating whether there are other actions that can be taken to bring customers out of impact, and additional teams are being engaged. \n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T13:53:10.098Z","updatedAt":"2026-08-20T13:53:10.103Z","entryType":"event","sourceId":20005869,"sourceType":"event"},{"title":"Update","content":"The rollback of the recent release on a test instance is still underway. We're continuing to monitor the progress. If this proves successful, the release will be rolled back in all instances which received it. Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. \n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T13:30:19.013Z","updatedAt":"2026-08-20T13:30:19.019Z","entryType":"event","sourceId":20005868,"sourceType":"event"},{"title":"Update","content":"We've identified a recent release which may be the trigger of the issue. We're in the process of rolling back the release on a test instance to see if this resolves the issue.\n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available. \n","createdAt":"2026-08-20T13:08:54.172Z","updatedAt":"2026-08-20T13:08:54.176Z","entryType":"event","sourceId":20005867,"sourceType":"event"},{"title":"Update","content":"We’re investigating a feature degradation impacting Revenue Cloud. Customers may receive 400 errors when performing actions such as quoting, ordering and configuring products. We're continuing to narrow down the scope of impact and will update our messaging to reflect this as we learn more. We're engaging additional teams, and we’ll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-08-20T13:00:11.455Z","updatedAt":"2026-08-20T13:00:11.460Z","entryType":"event","sourceId":20005866,"sourceType":"event"},{"title":"Degradation Started","content":"featurePerfDegradation","createdAt":"2026-08-20T12:58:43.920Z","updatedAt":"2026-08-20T14:06:09.229Z","entryType":"impact_start","startTime":"2026-08-20T09:00:00.000Z","sourceId":20004695,"sourceType":"impact","impactStartTime":"2026-08-20T12:58:43.920Z"}]},{"id":20004370,"externalId":"94379423","message":{"rootCause":null,"actionPlan":null,"pathToResolution":null},"additionalInformation":"","isCore":true,"affectsAll":true,"status":"Resolved","type":"Degradation","createdAt":"2026-08-21T11:01:10.770Z","updatedAt":"2026-08-21T11:54:56.392Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"IncidentImpacts":[{"id":20004699,"startTime":"2026-08-21T01:00:00.000Z","endTime":"2026-08-21T11:19:00.000Z","type":"featureServiceDisruption","severity":"minor","createdAt":"2026-08-21T11:01:10.945Z","updatedAt":"2026-08-21T11:54:56.374Z","startTimeCreatedAt":"2026-08-21T11:01:10.945Z","startTimeModifiedAt":"2026-08-21T11:35:57.724Z","endTimeCreatedAt":"2026-08-21T11:54:56.374Z","endTimeModifiedAt":null}],"IncidentEvents":[{"id":20005894,"type":"update","message":"Rollback 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 data in a Salesforce org. \n\nWe'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.","createdAt":"2026-08-21T11:54:56.383Z","updatedAt":"2026-08-21T11:54:56.388Z"},{"id":20005893,"type":"startTimeRevision","message":"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.","createdAt":"2026-08-21T11:35:59.937Z","updatedAt":"2026-08-21T11:36:02.856Z"},{"id":20005892,"type":"update","message":"We're rolling back the change that was identified as the likely trigger. Initial results confirm that connections are succeeding‌. We’re monitoring the progress of the rollback to full completion before confirming resolution. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-21T11:30:36.927Z","updatedAt":"2026-08-21T11:30:36.931Z"},{"id":20005891,"type":"update","message":"We're investigating an issue affecting some customers using chatbots or custom agents connected through the Salesforce Platform Model Context Protocol (MCP) Server. Customers are experiencing errors when their agent tries to query or update data in a Salesforce org. \n\nInitial investigations indicate a recent release as the likely trigger. We're planning to roll back to the last known good version. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-21T11:12:14.504Z","updatedAt":"2026-08-21T11:12:14.527Z"}],"timeline":[{"title":"Update","content":"Rollback 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 data in a Salesforce org. \n\nWe'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.","createdAt":"2026-08-21T11:54:56.383Z","updatedAt":"2026-08-21T11:54:56.388Z","entryType":"event","sourceId":20005894,"sourceType":"event"},{"title":"Resolved","content":"Incident Resolved","createdAt":"2026-08-21T11:54:56.374Z","updatedAt":null,"entryType":"impact_end","endTime":"2026-08-21T11:19:00.000Z","sourceId":20004699,"sourceType":"impact","impactStartTime":"2026-08-21T11:01:10.945Z"},{"title":"Update","content":"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.","createdAt":"2026-08-21T11:35:59.937Z","updatedAt":"2026-08-21T11:36:02.856Z","entryType":"event","sourceId":20005893,"sourceType":"event"},{"title":"Update","content":"We're rolling back the change that was identified as the likely trigger. Initial results confirm that connections are succeeding‌. We’re monitoring the progress of the rollback to full completion before confirming resolution. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-21T11:30:36.927Z","updatedAt":"2026-08-21T11:30:36.931Z","entryType":"event","sourceId":20005892,"sourceType":"event"},{"title":"Update","content":"We're investigating an issue affecting some customers using chatbots or custom agents connected through the Salesforce Platform Model Context Protocol (MCP) Server. Customers are experiencing errors when their agent tries to query or update data in a Salesforce org. \n\nInitial investigations indicate a recent release as the likely trigger. We're planning to roll back to the last known good version. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-08-21T11:12:14.504Z","updatedAt":"2026-08-21T11:12:14.527Z","entryType":"event","sourceId":20005891,"sourceType":"event"},{"title":"Degradation Started","content":"featureServiceDisruption","createdAt":"2026-08-21T11:01:10.945Z","updatedAt":"2026-08-21T11:35:57.724Z","entryType":"impact_start","startTime":"2026-08-21T01:00:00.000Z","sourceId":20004699,"sourceType":"impact","impactStartTime":"2026-08-21T11:01:10.945Z"}]},{"id":20004381,"externalId":"94674101","message":{"rootCause":null,"actionPlan":null,"pathToResolution":null},"additionalInformation":"","isCore":false,"affectsAll":false,"status":"Resolved","type":"Degradation","createdAt":"2026-08-28T19:46:08.988Z","updatedAt":"2026-08-28T19:46:09.094Z","instanceKeys":["USA1"],"serviceKeys":["EinsteinBots"],"IncidentImpacts":[{"id":20004711,"startTime":"2026-08-26T00:14:00.000Z","endTime":"2026-08-28T19:04:00.000Z","type":"einsteinBots","severity":"minor","createdAt":"2026-08-28T19:46:09.087Z","updatedAt":"2026-08-28T19:46:09.092Z","startTimeCreatedAt":"2026-08-28T19:46:09.088Z","startTimeModifiedAt":null,"endTimeCreatedAt":"2026-08-28T19:46:09.088Z","endTimeModifiedAt":null}],"IncidentEvents":[],"timeline":[{"title":"Resolved","content":"Incident Resolved","createdAt":"2026-08-28T19:46:09.088Z","updatedAt":null,"entryType":"impact_end","endTime":"2026-08-28T19:04:00.000Z","sourceId":20004711,"sourceType":"impact","impactStartTime":"2026-08-28T19:46:09.088Z"},{"title":"Degradation Started","content":"einsteinBots","createdAt":"2026-08-28T19:46:09.088Z","updatedAt":null,"entryType":"impact_start","startTime":"2026-08-26T00:14:00.000Z","sourceId":20004711,"sourceType":"impact","impactStartTime":"2026-08-28T19:46:09.088Z"}]},{"id":20004400,"externalId":"94930999","message":{"rootCause":null,"actionPlan":null,"pathToResolution":null},"additionalInformation":"","isCore":false,"affectsAll":false,"status":"Resolved","type":"Disruption","createdAt":"2026-09-03T15:01:08.676Z","updatedAt":"2026-09-03T15:24:47.509Z","instanceKeys":["USA1"],"serviceKeys":["B2B2CCommerce"],"IncidentImpacts":[{"id":20004731,"startTime":"2026-09-03T13:50:00.000Z","endTime":"2026-09-03T13:51:00.000Z","type":"serviceDisruption","severity":"major","createdAt":"2026-09-03T15:01:08.783Z","updatedAt":"2026-09-03T15:22:56.763Z","startTimeCreatedAt":"2026-09-03T15:01:08.783Z","startTimeModifiedAt":null,"endTimeCreatedAt":"2026-09-03T15:01:08.783Z","endTimeModifiedAt":"2026-09-03T15:22:56.763Z"}],"IncidentEvents":[{"id":20005993,"type":"correctionFalsePositive","message":"The 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 inconvenience caused by the false positive notification, and we will undertake a full investigation as we look to improve our impact alerting and assessment configurations.","createdAt":"2026-09-03T15:24:47.504Z","updatedAt":"2026-09-03T15:24:47.507Z"},{"id":20005991,"type":"update","message":"We resolved a service disruption affecting Commerce cloud sandbox storefronts. We restored access, and customers can now reach the affected storefronts as expected.\n\nWe apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.\n","createdAt":"2026-09-03T15:08:40.895Z","updatedAt":"2026-09-03T15:08:40.898Z"}],"timeline":[{"title":"Update","content":"The 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 inconvenience caused by the false positive notification, and we will undertake a full investigation as we look to improve our impact alerting and assessment configurations.","createdAt":"2026-09-03T15:24:47.504Z","updatedAt":"2026-09-03T15:24:47.507Z","entryType":"event","sourceId":20005993,"sourceType":"event"},{"title":"Update","content":"We resolved a service disruption affecting Commerce cloud sandbox storefronts. We restored access, and customers can now reach the affected storefronts as expected.\n\nWe apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.\n","createdAt":"2026-09-03T15:08:40.895Z","updatedAt":"2026-09-03T15:08:40.898Z","entryType":"event","sourceId":20005991,"sourceType":"event"},{"title":"Resolved","content":"Incident Resolved","createdAt":"2026-09-03T15:01:08.783Z","updatedAt":"2026-09-03T15:22:56.763Z","entryType":"impact_end","endTime":"2026-09-03T13:51:00.000Z","sourceId":20004731,"sourceType":"impact","impactStartTime":"2026-09-03T15:01:08.783Z"},{"title":"Disruption Started","content":"serviceDisruption","createdAt":"2026-09-03T15:01:08.783Z","updatedAt":null,"entryType":"impact_start","startTime":"2026-09-03T13:50:00.000Z","sourceId":20004731,"sourceType":"impact","impactStartTime":"2026-09-03T15:01:08.783Z"}]},{"id":20004403,"externalId":"94946410","message":{"rootCause":null,"actionPlan":null,"pathToResolution":null},"additionalInformation":"","isCore":false,"affectsAll":false,"status":"Resolved","type":"Degradation","createdAt":"2026-09-03T22:30:03.290Z","updatedAt":"2026-09-04T06:22:57.370Z","instanceKeys":["USA1"],"serviceKeys":["Customer360Audiences"],"IncidentImpacts":[{"id":20004734,"startTime":"2026-09-02T17:58:00.000Z","endTime":"2026-09-04T05:10:00.000Z","type":"featurePerfDegradation","severity":"minor","createdAt":"2026-09-03T22:30:03.521Z","updatedAt":"2026-09-04T06:22:57.349Z","startTimeCreatedAt":"2026-09-03T22:30:03.521Z","startTimeModifiedAt":null,"endTimeCreatedAt":"2026-09-04T06:22:57.350Z","endTimeModifiedAt":null}],"IncidentEvents":[{"id":20006003,"type":"update","message":"We've resolved this issue. We developed an updated fix addressing both the original regression and the additional impact.\nWe deployed the updated fix and confirmed that jobs queued during the incident resumed processing normally. \nWe apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.\n","createdAt":"2026-09-04T06:22:57.357Z","updatedAt":"2026-09-04T06:22:57.362Z"},{"id":20006001,"type":"update","message":"Due to a functional issue identified following the rollback, we’ve now paused this activity. We are creating a roll-forward fix to address both the original issue and the new functional impact. Users may now experience that their manual and scheduled transform runs fail to start. This was first identified at 20:10 UTC, September 3.\n\nWe will provide the next update once we can clarify how long the fix-forward will take to verify and deploy, or when new information becomes available. We apologize for any inconvenience this is causing to customers. ","createdAt":"2026-09-04T01:35:35.842Z","updatedAt":"2026-09-04T01:35:35.847Z"},{"id":20006000,"type":"update","message":"As we complete the rollback on individual instances, we will post instance-level updates to accurately reflect each instance’s impact end time. Once an instance has been rolled back, we will remove it from this main post.\n\nInstances where rollback is still in progress will continue to receive updates in this post until remediation is complete. ","createdAt":"2026-09-04T00:20:47.129Z","updatedAt":"2026-09-04T00:20:47.133Z"},{"id":20005998,"type":"update","message":"Data Cloud customers using batch transforms may see completed jobs remain in an outdated status in the user interface. Automated flows, subsequent transforms, or other downstream processes that depend on the status update may not initiate, potentially delaying downstream data processing. Transform jobs continue to complete successfully, and no impact to the processed data has been identified.\n\nWe have identified the trigger and initiated a roll back which is expected to remediate the issue. We will provide an update upon completion of the roll back, or sooner if more information becomes available. ","createdAt":"2026-09-03T22:40:32.607Z","updatedAt":"2026-09-03T22:47:38.999Z"}],"timeline":[{"title":"Update","content":"We've resolved this issue. We developed an updated fix addressing both the original regression and the additional impact.\nWe deployed the updated fix and confirmed that jobs queued during the incident resumed processing normally. \nWe apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.\n","createdAt":"2026-09-04T06:22:57.357Z","updatedAt":"2026-09-04T06:22:57.362Z","entryType":"event","sourceId":20006003,"sourceType":"event"},{"title":"Resolved","content":"Incident Resolved","createdAt":"2026-09-04T06:22:57.350Z","updatedAt":null,"entryType":"impact_end","endTime":"2026-09-04T05:10:00.000Z","sourceId":20004734,"sourceType":"impact","impactStartTime":"2026-09-03T22:30:03.521Z"},{"title":"Update","content":"Due to a functional issue identified following the rollback, we’ve now paused this activity. We are creating a roll-forward fix to address both the original issue and the new functional impact. Users may now experience that their manual and scheduled transform runs fail to start. This was first identified at 20:10 UTC, September 3.\n\nWe will provide the next update once we can clarify how long the fix-forward will take to verify and deploy, or when new information becomes available. We apologize for any inconvenience this is causing to customers. ","createdAt":"2026-09-04T01:35:35.842Z","updatedAt":"2026-09-04T01:35:35.847Z","entryType":"event","sourceId":20006001,"sourceType":"event"},{"title":"Update","content":"As we complete the rollback on individual instances, we will post instance-level updates to accurately reflect each instance’s impact end time. Once an instance has been rolled back, we will remove it from this main post.\n\nInstances where rollback is still in progress will continue to receive updates in this post until remediation is complete. ","createdAt":"2026-09-04T00:20:47.129Z","updatedAt":"2026-09-04T00:20:47.133Z","entryType":"event","sourceId":20006000,"sourceType":"event"},{"title":"Update","content":"Data Cloud customers using batch transforms may see completed jobs remain in an outdated status in the user interface. Automated flows, subsequent transforms, or other downstream processes that depend on the status update may not initiate, potentially delaying downstream data processing. Transform jobs continue to complete successfully, and no impact to the processed data has been identified.\n\nWe have identified the trigger and initiated a roll back which is expected to remediate the issue. We will provide an update upon completion of the roll back, or sooner if more information becomes available. ","createdAt":"2026-09-03T22:40:32.607Z","updatedAt":"2026-09-03T22:47:38.999Z","entryType":"event","sourceId":20005998,"sourceType":"event"},{"title":"Degradation Started","content":"featurePerfDegradation","createdAt":"2026-09-03T22:30:03.521Z","updatedAt":null,"entryType":"impact_start","startTime":"2026-09-02T17:58:00.000Z","sourceId":20004734,"sourceType":"impact","impactStartTime":"2026-09-03T22:30:03.521Z"}]},{"id":20004419,"externalId":"95079032","message":{"rootCause":null,"actionPlan":null,"pathToResolution":null},"additionalInformation":"","isCore":true,"affectsAll":true,"status":"Resolved","type":"Degradation","createdAt":"2026-09-08T00:49:08.280Z","updatedAt":"2026-09-08T00:49:08.409Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"IncidentImpacts":[{"id":20004750,"startTime":"2026-09-06T22:30:00.000Z","endTime":"2026-09-07T22:59:00.000Z","type":"featureServiceDisruption","severity":"minor","createdAt":"2026-09-08T00:49:08.396Z","updatedAt":"2026-09-08T00:49:08.401Z","startTimeCreatedAt":"2026-09-08T00:49:08.396Z","startTimeModifiedAt":null,"endTimeCreatedAt":"2026-09-08T00:49:08.396Z","endTimeModifiedAt":null}],"IncidentEvents":[{"id":20006041,"type":"update","message":"We'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 communication is intended to share the exact start and end time of impact. We apologize for how this issue may have affected you and your business.","createdAt":"2026-09-08T00:49:08.403Z","updatedAt":"2026-09-08T00:49:08.407Z"}],"timeline":[{"title":"Update","content":"We'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 communication is intended to share the exact start and end time of impact. We apologize for how this issue may have affected you and your business.","createdAt":"2026-09-08T00:49:08.403Z","updatedAt":"2026-09-08T00:49:08.407Z","entryType":"event","sourceId":20006041,"sourceType":"event"},{"title":"Resolved","content":"Incident Resolved","createdAt":"2026-09-08T00:49:08.396Z","updatedAt":null,"entryType":"impact_end","endTime":"2026-09-07T22:59:00.000Z","sourceId":20004750,"sourceType":"impact","impactStartTime":"2026-09-08T00:49:08.396Z"},{"title":"Degradation Started","content":"featureServiceDisruption","createdAt":"2026-09-08T00:49:08.396Z","updatedAt":null,"entryType":"impact_start","startTime":"2026-09-06T22:30:00.000Z","sourceId":20004750,"sourceType":"impact","impactStartTime":"2026-09-08T00:49:08.396Z"}]},{"id":20004433,"externalId":"95390343","message":{"rootCause":null,"actionPlan":null,"pathToResolution":null},"additionalInformation":"","isCore":true,"affectsAll":true,"status":"Resolved","type":"Disruption","createdAt":"2026-09-16T08:32:58.052Z","updatedAt":"2026-09-17T17:27:33.330Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"IncidentImpacts":[{"id":20004764,"startTime":"2026-09-16T07:50:00.000Z","endTime":"2026-09-16T15:26:00.000Z","type":"serviceDisruption","severity":"major","createdAt":"2026-09-16T08:32:58.217Z","updatedAt":"2026-09-16T18:59:57.866Z","startTimeCreatedAt":"2026-09-16T08:32:58.218Z","startTimeModifiedAt":"2026-09-16T08:33:44.453Z","endTimeCreatedAt":"2026-09-16T18:59:57.866Z","endTimeModifiedAt":null}],"IncidentEvents":[{"id":20006087,"type":"update","message":"As 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 have caused.","createdAt":"2026-09-17T17:16:45.133Z","updatedAt":"2026-09-17T17:16:45.138Z"},{"id":20006085,"type":"resolved","message":"The 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 trigger, the underlying cause, and preventive action to avoid a repeat in the future.","createdAt":"2026-09-16T18:59:57.881Z","updatedAt":"2026-09-16T18:59:57.885Z"},{"id":20006084,"type":"update","message":"The issue causing severe delays, intermittent errors, and difficulty accessing some Salesforce services or creating support cases across affected Hyperforce environments was resolved as of 15:26 UTC. A targeted mitigation restored service, and telemetry has remained healthy during extended validation.\n\nWe 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.","createdAt":"2026-09-16T18:59:57.875Z","updatedAt":"2026-09-16T18:59:57.879Z"},{"id":20006083,"type":"update","message":"Service telemetry remains healthy, and our review has not confirmed any ongoing customer impact related to this incident. Before declaring the issue resolved, we’re ensuring the existing mitigation remains active across all affected customer-facing Hyperforce environments.\n\nWe’re applying targeted updates where the automated process did not complete, helping maintain service stability and reduce the risk of impact returning. We’ll provide another update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T18:46:44.014Z","updatedAt":"2026-09-16T18:46:44.018Z"},{"id":20006082,"type":"update","message":"We continue to observe healthy service telemetry across customer-facing Hyperforce environments, and our review of recent customer reports has not confirmed ongoing impact related to this incident. We’re completing validation of one isolated report before declaring the issue resolved.\n\nThe mitigation remains active, and we’re adding preventive protections to related service paths to reduce the risk of recurrence. We’ll provide another update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T18:06:50.078Z","updatedAt":"2026-09-16T18:06:50.081Z"},{"id":20006081,"type":"update","message":"Service telemetry has remained healthy across customer-facing Hyperforce environments since 15:26 UTC. Our review of recent customer reports has not identified any confirmed ongoing impact related to this incident.\n\nThe mitigation remains active, and we’re applying additional preventive protections to related service paths while completing final validation. \n\nWe’ll provide another update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T17:29:47.885Z","updatedAt":"2026-09-16T17:29:47.889Z"},{"id":20006080,"type":"update","message":"Our telemetry is no longer showing active performance or availability impact across customer-facing Hyperforce environments. We’re validating recent customer reports against service health data and confirming the recovery time before declaring the issue resolved.\n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T17:00:42.220Z","updatedAt":"2026-09-16T17:00:42.225Z"},{"id":20006078,"type":"update","message":"We’ve completed applying the mitigation across the affected Hyperforce environments and are conducting fleetwide validation to confirm service recovery. Most customer-facing impact has cleared, while we work through a small number of remaining instances that require additional verification or targeted recovery actions.\n\nCustomers on any remaining affected instances may continue to experience severe delays, intermittent errors, or difficulty accessing some services and creating support cases.\n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T16:23:11.509Z","updatedAt":"2026-09-16T16:23:11.513Z"},{"id":20006077,"type":"impactRadiusDecrease","message":"Investigations 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 this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. ","createdAt":"2026-09-16T15:56:37.433Z","updatedAt":"2026-09-16T15:56:37.436Z"},{"id":20006076,"type":"update","message":"We’ve narrowed the remaining impact to a subset of Hyperforce instances. First-party environments were not impacted. The mitigation is now in place across nearly all affected instances, and we’re completing targeted restarts and manual recovery actions on the remaining affected instances.\n\nSome customers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T15:39:15.942Z","updatedAt":"2026-09-16T15:39:15.946Z"},{"id":20006075,"type":"update","message":"We're seeing signs of recovery and many customers are coming out of impact. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. We don't have a confirmed resolution time.  \n\nCustomers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T14:56:31.590Z","updatedAt":"2026-09-16T14:56:31.594Z"},{"id":20006073,"type":"update","message":"We've completed the next phase of the rollout to the remaining impacted instances. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. \n\nCustomers who are affected may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T14:27:19.693Z","updatedAt":"2026-09-16T14:27:19.698Z"},{"id":20006072,"type":"update","message":"We've completed the next phase of the rollout. We're manually restarting ‌instances where the automated fix didn't fully resolve the issue. We’ve received reports of scheduled jobs not running as expected for some customers who are now able to access the service. We're investigating this. \n\nInvestigations have highlighted that the impact radius is narrower than initially understood. We'll now remove any instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T14:00:35.660Z","updatedAt":"2026-09-16T14:01:59.287Z"},{"id":20006071,"type":"update","message":"We've determined that the rollout didn't fully complete for a number of instances, so some customers may still be experiencing the original issue. We're reapplying the fix now. Some customers may need to clear cached data or restart their session for full recovery. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.\n","createdAt":"2026-09-16T13:13:20.319Z","updatedAt":"2026-09-16T13:13:20.322Z"},{"id":20006070,"type":"update","message":"As the rollout is progressing region-wise, most instances are recovering. Some customers may still see errors accessing the service until we finish a manual restart on their instance. We don't have a confirmed resolution time.  \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T12:39:44.512Z","updatedAt":"2026-09-16T12:39:44.515Z"},{"id":20006069,"type":"update","message":"The rollout is progressing region-wise and services are returning to normal in regions that are completed. We're monitoring the rollout as it continues, and we're working on a permanent fix. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T12:13:10.420Z","updatedAt":"2026-09-16T12:13:10.424Z"},{"id":20006068,"type":"update","message":"The rollout is progressing region by region and we're seeing improvement. We don't have a confirmed time of completion. GovCloud customers have been confirmed to be out of impact. \n\nCustomers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T11:41:54.396Z","updatedAt":"2026-09-16T11:41:54.400Z"},{"id":20006067,"type":"update","message":"A fleetwide rollout is in progress and customers are starting to see their service return to normal. In parallel, we're working on a code-level permanent fix.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T11:19:04.428Z","updatedAt":"2026-09-16T11:19:04.431Z"},{"id":20006066,"type":"update","message":"We've validated the fix successfully on the test instance. We'll now roll out the fix fleetwide to all impacted instances. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T10:56:36.911Z","updatedAt":"2026-09-16T10:56:36.915Z"},{"id":20006065,"type":"update","message":"We're pursuing the fastest path to restore services. We're testing our fix on a test instance. Once the test is validated, we'll roll out the fix fleetwide. \n\nCustomers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T10:31:31.130Z","updatedAt":"2026-09-16T10:31:31.135Z"},{"id":20006064,"type":"update","message":"One of our core system components experienced increased load, which limited its capacity to process requests. We're working on a fix to resolve this issue and restore services. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T10:18:06.138Z","updatedAt":"2026-09-16T10:18:06.142Z"},{"id":20006063,"type":"update","message":"We're no longer pursuing restarts as a path to remediation. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T10:01:20.691Z","updatedAt":"2026-09-16T10:01:20.697Z"},{"id":20006062,"type":"update","message":"We believe that the issue is caused by an external dependency failure that's impacting the legacy login server. We're blocking the Application Programming Interface (API) endpoint as a potential mitigation step. We also engaged our third-party infrastructure provider to determine if there are any issues and they've confirmed that there are no issues with ‌third-party infrastructure. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T09:57:01.936Z","updatedAt":"2026-09-16T09:57:01.939Z"},{"id":20006061,"type":"update","message":"Investigations indicate that requests are stalling while waiting on a response from an internal login service, which is using up available server resources. Customers continue to experience severe delays, intermittent errors, and inability to access some services. This also affects support case creation.\n\nWe've attempted a rolling restart on one of the impacted instances to see if that resolves the issue.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T09:10:00.351Z","updatedAt":"2026-09-16T09:10:00.357Z"},{"id":20006060,"type":"update","message":"We're investigating an issue impacting multiple instances across all regions where customers may experience severe delays, intermittent errors, or an inability to access some services. Some customers are also unable to submit new support cases through the Help portal. We're investigating the issue.  \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T08:45:24.941Z","updatedAt":"2026-09-16T08:45:24.947Z"}],"timeline":[{"title":"Update","content":"As 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 have caused.","createdAt":"2026-09-17T17:16:45.133Z","updatedAt":"2026-09-17T17:16:45.138Z","entryType":"event","sourceId":20006087,"sourceType":"event"},{"title":"Update","content":"The 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 trigger, the underlying cause, and preventive action to avoid a repeat in the future.","createdAt":"2026-09-16T18:59:57.881Z","updatedAt":"2026-09-16T18:59:57.885Z","entryType":"event","sourceId":20006085,"sourceType":"event"},{"title":"Update","content":"The issue causing severe delays, intermittent errors, and difficulty accessing some Salesforce services or creating support cases across affected Hyperforce environments was resolved as of 15:26 UTC. A targeted mitigation restored service, and telemetry has remained healthy during extended validation.\n\nWe 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.","createdAt":"2026-09-16T18:59:57.875Z","updatedAt":"2026-09-16T18:59:57.879Z","entryType":"event","sourceId":20006084,"sourceType":"event"},{"title":"Resolved","content":"Incident Resolved","createdAt":"2026-09-16T18:59:57.866Z","updatedAt":null,"entryType":"impact_end","endTime":"2026-09-16T15:26:00.000Z","sourceId":20004764,"sourceType":"impact","impactStartTime":"2026-09-16T08:32:58.218Z"},{"title":"Update","content":"Service telemetry remains healthy, and our review has not confirmed any ongoing customer impact related to this incident. Before declaring the issue resolved, we’re ensuring the existing mitigation remains active across all affected customer-facing Hyperforce environments.\n\nWe’re applying targeted updates where the automated process did not complete, helping maintain service stability and reduce the risk of impact returning. We’ll provide another update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T18:46:44.014Z","updatedAt":"2026-09-16T18:46:44.018Z","entryType":"event","sourceId":20006083,"sourceType":"event"},{"title":"Update","content":"We continue to observe healthy service telemetry across customer-facing Hyperforce environments, and our review of recent customer reports has not confirmed ongoing impact related to this incident. We’re completing validation of one isolated report before declaring the issue resolved.\n\nThe mitigation remains active, and we’re adding preventive protections to related service paths to reduce the risk of recurrence. We’ll provide another update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T18:06:50.078Z","updatedAt":"2026-09-16T18:06:50.081Z","entryType":"event","sourceId":20006082,"sourceType":"event"},{"title":"Update","content":"Service telemetry has remained healthy across customer-facing Hyperforce environments since 15:26 UTC. Our review of recent customer reports has not identified any confirmed ongoing impact related to this incident.\n\nThe mitigation remains active, and we’re applying additional preventive protections to related service paths while completing final validation. \n\nWe’ll provide another update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T17:29:47.885Z","updatedAt":"2026-09-16T17:29:47.889Z","entryType":"event","sourceId":20006081,"sourceType":"event"},{"title":"Update","content":"Our telemetry is no longer showing active performance or availability impact across customer-facing Hyperforce environments. We’re validating recent customer reports against service health data and confirming the recovery time before declaring the issue resolved.\n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T17:00:42.220Z","updatedAt":"2026-09-16T17:00:42.225Z","entryType":"event","sourceId":20006080,"sourceType":"event"},{"title":"Update","content":"We’ve completed applying the mitigation across the affected Hyperforce environments and are conducting fleetwide validation to confirm service recovery. Most customer-facing impact has cleared, while we work through a small number of remaining instances that require additional verification or targeted recovery actions.\n\nCustomers on any remaining affected instances may continue to experience severe delays, intermittent errors, or difficulty accessing some services and creating support cases.\n\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T16:23:11.509Z","updatedAt":"2026-09-16T16:23:11.513Z","entryType":"event","sourceId":20006078,"sourceType":"event"},{"title":"Update","content":"Investigations 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 this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused. ","createdAt":"2026-09-16T15:56:37.433Z","updatedAt":"2026-09-16T15:56:37.436Z","entryType":"event","sourceId":20006077,"sourceType":"event"},{"title":"Update","content":"We’ve narrowed the remaining impact to a subset of Hyperforce instances. First-party environments were not impacted. The mitigation is now in place across nearly all affected instances, and we’re completing targeted restarts and manual recovery actions on the remaining affected instances.\n\nSome customers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T15:39:15.942Z","updatedAt":"2026-09-16T15:39:15.946Z","entryType":"event","sourceId":20006076,"sourceType":"event"},{"title":"Update","content":"We're seeing signs of recovery and many customers are coming out of impact. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. We don't have a confirmed resolution time.  \n\nCustomers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T14:56:31.590Z","updatedAt":"2026-09-16T14:56:31.594Z","entryType":"event","sourceId":20006075,"sourceType":"event"},{"title":"Update","content":"We've completed the next phase of the rollout to the remaining impacted instances. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. \n\nCustomers who are affected may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T14:27:19.693Z","updatedAt":"2026-09-16T14:27:19.698Z","entryType":"event","sourceId":20006073,"sourceType":"event"},{"title":"Update","content":"We've completed the next phase of the rollout. We're manually restarting ‌instances where the automated fix didn't fully resolve the issue. We’ve received reports of scheduled jobs not running as expected for some customers who are now able to access the service. We're investigating this. \n\nInvestigations have highlighted that the impact radius is narrower than initially understood. We'll now remove any instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T14:00:35.660Z","updatedAt":"2026-09-16T14:01:59.287Z","entryType":"event","sourceId":20006072,"sourceType":"event"},{"title":"Update","content":"We've determined that the rollout didn't fully complete for a number of instances, so some customers may still be experiencing the original issue. We're reapplying the fix now. Some customers may need to clear cached data or restart their session for full recovery. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.\n","createdAt":"2026-09-16T13:13:20.319Z","updatedAt":"2026-09-16T13:13:20.322Z","entryType":"event","sourceId":20006071,"sourceType":"event"},{"title":"Update","content":"As the rollout is progressing region-wise, most instances are recovering. Some customers may still see errors accessing the service until we finish a manual restart on their instance. We don't have a confirmed resolution time.  \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T12:39:44.512Z","updatedAt":"2026-09-16T12:39:44.515Z","entryType":"event","sourceId":20006070,"sourceType":"event"},{"title":"Update","content":"The rollout is progressing region-wise and services are returning to normal in regions that are completed. We're monitoring the rollout as it continues, and we're working on a permanent fix. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T12:13:10.420Z","updatedAt":"2026-09-16T12:13:10.424Z","entryType":"event","sourceId":20006069,"sourceType":"event"},{"title":"Update","content":"The rollout is progressing region by region and we're seeing improvement. We don't have a confirmed time of completion. GovCloud customers have been confirmed to be out of impact. \n\nCustomers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T11:41:54.396Z","updatedAt":"2026-09-16T11:41:54.400Z","entryType":"event","sourceId":20006068,"sourceType":"event"},{"title":"Update","content":"A fleetwide rollout is in progress and customers are starting to see their service return to normal. In parallel, we're working on a code-level permanent fix.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T11:19:04.428Z","updatedAt":"2026-09-16T11:19:04.431Z","entryType":"event","sourceId":20006067,"sourceType":"event"},{"title":"Update","content":"We've validated the fix successfully on the test instance. We'll now roll out the fix fleetwide to all impacted instances. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T10:56:36.911Z","updatedAt":"2026-09-16T10:56:36.915Z","entryType":"event","sourceId":20006066,"sourceType":"event"},{"title":"Update","content":"We're pursuing the fastest path to restore services. We're testing our fix on a test instance. Once the test is validated, we'll roll out the fix fleetwide. \n\nCustomers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T10:31:31.130Z","updatedAt":"2026-09-16T10:31:31.135Z","entryType":"event","sourceId":20006065,"sourceType":"event"},{"title":"Update","content":"One of our core system components experienced increased load, which limited its capacity to process requests. We're working on a fix to resolve this issue and restore services. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T10:18:06.138Z","updatedAt":"2026-09-16T10:18:06.142Z","entryType":"event","sourceId":20006064,"sourceType":"event"},{"title":"Update","content":"We're no longer pursuing restarts as a path to remediation. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T10:01:20.691Z","updatedAt":"2026-09-16T10:01:20.697Z","entryType":"event","sourceId":20006063,"sourceType":"event"},{"title":"Update","content":"We believe that the issue is caused by an external dependency failure that's impacting the legacy login server. We're blocking the Application Programming Interface (API) endpoint as a potential mitigation step. We also engaged our third-party infrastructure provider to determine if there are any issues and they've confirmed that there are no issues with ‌third-party infrastructure. \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T09:57:01.936Z","updatedAt":"2026-09-16T09:57:01.939Z","entryType":"event","sourceId":20006062,"sourceType":"event"},{"title":"Update","content":"Investigations indicate that requests are stalling while waiting on a response from an internal login service, which is using up available server resources. Customers continue to experience severe delays, intermittent errors, and inability to access some services. This also affects support case creation.\n\nWe've attempted a rolling restart on one of the impacted instances to see if that resolves the issue.\n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","createdAt":"2026-09-16T09:10:00.351Z","updatedAt":"2026-09-16T09:10:00.357Z","entryType":"event","sourceId":20006061,"sourceType":"event"},{"title":"Update","content":"We're investigating an issue impacting multiple instances across all regions where customers may experience severe delays, intermittent errors, or an inability to access some services. Some customers are also unable to submit new support cases through the Help portal. We're investigating the issue.  \n\nWe'll provide an update in 30 minutes or sooner if additional information becomes available. ","createdAt":"2026-09-16T08:45:24.941Z","updatedAt":"2026-09-16T08:45:24.947Z","entryType":"event","sourceId":20006060,"sourceType":"event"},{"title":"Disruption Started","content":"serviceDisruption","createdAt":"2026-09-16T08:32:58.218Z","updatedAt":"2026-09-16T08:33:44.453Z","entryType":"impact_start","startTime":"2026-09-16T07:50:00.000Z","sourceId":20004764,"sourceType":"impact","impactStartTime":"2026-09-16T08:32:58.218Z"}]},{"id":20004440,"externalId":"95528026","message":{"rootCause":null,"actionPlan":null,"pathToResolution":null},"additionalInformation":"","isCore":false,"affectsAll":false,"status":"Resolved","type":"Degradation","createdAt":"2026-09-19T23:13:47.660Z","updatedAt":"2026-09-20T05:46:44.408Z","instanceKeys":["USA1"],"serviceKeys":["Customer360Audiences"],"IncidentImpacts":[{"id":20004771,"startTime":"2026-09-19T11:30:00.000Z","endTime":"2026-09-20T01:11:00.000Z","type":"featureServiceDisruption","severity":"minor","createdAt":"2026-09-19T23:13:47.780Z","updatedAt":"2026-09-20T05:46:44.395Z","startTimeCreatedAt":"2026-09-19T23:13:47.780Z","startTimeModifiedAt":"2026-09-20T00:21:16.212Z","endTimeCreatedAt":"2026-09-20T05:46:44.396Z","endTimeModifiedAt":null}],"IncidentEvents":[{"id":20006106,"type":"resolvedFeatureDisruption","message":"We’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 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.","createdAt":"2026-09-20T05:46:44.401Z","updatedAt":"2026-09-20T05:46:44.405Z"},{"id":20006105,"type":"update","message":"We performed further review and analysis and noted that a few other instances may also be impacted as a result of this incident. We have added those instances to the list. \n\nMeanwhile, we're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.","createdAt":"2026-09-20T01:45:05.567Z","updatedAt":"2026-09-20T01:45:05.571Z"},{"id":20006104,"type":"update","message":"We've identified that the issue affecting Data Cloud activations stems from a third-party cloud storage service used in our Prod1 CDP1 environment. We applied a configuration change to that service to help address the errors, and we're preparing an alternate storage option as an additional measure. We're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.","createdAt":"2026-09-20T00:21:16.218Z","updatedAt":"2026-09-20T00:21:16.223Z"},{"id":20006103,"type":"update","message":"We're continuing to investigate the issue affecting Data Cloud activations for customers in the US-east-1 region on our Prod1-CDP1 environment. We've confirmed the issue stems from a third-party cloud storage service, and we're waiting on their team to trace the cause using system logs. Our engineers are preparing alternative options to reduce impact while this investigation continues. We'll provide an update if additional information becomes available.","createdAt":"2026-09-19T23:46:17.999Z","updatedAt":"2026-09-19T23:46:18.002Z"}],"timeline":[{"title":"Update","content":"We’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 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.","createdAt":"2026-09-20T05:46:44.401Z","updatedAt":"2026-09-20T05:46:44.405Z","entryType":"event","sourceId":20006106,"sourceType":"event"},{"title":"Resolved","content":"Incident Resolved","createdAt":"2026-09-20T05:46:44.396Z","updatedAt":null,"entryType":"impact_end","endTime":"2026-09-20T01:11:00.000Z","sourceId":20004771,"sourceType":"impact","impactStartTime":"2026-09-19T23:13:47.780Z"},{"title":"Update","content":"We performed further review and analysis and noted that a few other instances may also be impacted as a result of this incident. We have added those instances to the list. \n\nMeanwhile, we're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.","createdAt":"2026-09-20T01:45:05.567Z","updatedAt":"2026-09-20T01:45:05.571Z","entryType":"event","sourceId":20006105,"sourceType":"event"},{"title":"Update","content":"We've identified that the issue affecting Data Cloud activations stems from a third-party cloud storage service used in our Prod1 CDP1 environment. We applied a configuration change to that service to help address the errors, and we're preparing an alternate storage option as an additional measure. We're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.","createdAt":"2026-09-20T00:21:16.218Z","updatedAt":"2026-09-20T00:21:16.223Z","entryType":"event","sourceId":20006104,"sourceType":"event"},{"title":"Update","content":"We're continuing to investigate the issue affecting Data Cloud activations for customers in the US-east-1 region on our Prod1-CDP1 environment. We've confirmed the issue stems from a third-party cloud storage service, and we're waiting on their team to trace the cause using system logs. Our engineers are preparing alternative options to reduce impact while this investigation continues. We'll provide an update if additional information becomes available.","createdAt":"2026-09-19T23:46:17.999Z","updatedAt":"2026-09-19T23:46:18.002Z","entryType":"event","sourceId":20006103,"sourceType":"event"},{"title":"Degradation Started","content":"featureServiceDisruption","createdAt":"2026-09-19T23:13:47.780Z","updatedAt":"2026-09-20T00:21:16.212Z","entryType":"impact_start","startTime":"2026-09-19T11:30:00.000Z","sourceId":20004771,"sourceType":"impact","impactStartTime":"2026-09-19T23:13:47.780Z"}]}],"Tags":[],"GeneralMessages":[{"id":20000244,"subject":"Security Advisory: Protecting Experience Cloud Sites from Guest User Misconfigurations ","body":"Salesforce is actively monitoring threat activity targeting public-facing Experience Cloud sites, including attempts to take advantage of overly permissive guest user configurations.\n\nAt this time, we have not identified any vulnerability inherent to the Salesforce platform associated with this activity. These attempts are focused on customer configuration settings that, if not properly secured, may increase exposure.\n\nWe encourage customers to review their Experience Cloud guest user settings and take immediate recommended actions. For additional details and steps to help protect your org, please see our blog: https://www.salesforce.com/blog/protecting-your-data-essential-actions-to-secure-experience-cloud-guest-user-access/","incidentId":null,"publicView":true,"startDate":"2026-03-08T04:00:00.000Z","endDate":null,"createdAt":"2026-03-07T23:06:36.591Z","updatedAt":"2026-03-07T23:07:25.213Z","externalId":null,"isVisibleWhenClosed":false,"isVisible":true,"informationalMessageType":"informationalMessage","status":"Active","timeline":[{"title":"Update","content":"Salesforce is actively monitoring threat activity targeting public-facing Experience Cloud sites, including attempts to take advantage of overly permissive guest user configurations.\n\nWe have identified additional guidance for customers to help protect their orgs. Please see our updated blog for recommended actions: https://www.salesforce.com/blog/protecting-your-data-essential-actions-to-secure-experience-cloud-guest-user-access/\n\nAt this time, we have not identified any vulnerability inherent to the Salesforce platform associated with this activity.","createdAt":"2026-03-12T20:20:56.359Z","updatedAt":"2026-03-12T20:20:56.361Z","entryType":"informational_message_update","sourceId":20000406,"sourceType":"update"},{"title":"Security Advisory: Protecting Experience Cloud Sites from Guest User Misconfigurations ","content":"Salesforce is actively monitoring threat activity targeting public-facing Experience Cloud sites, including attempts to take advantage of overly permissive guest user configurations.\n\nAt this time, we have not identified any vulnerability inherent to the Salesforce platform associated with this activity. These attempts are focused on customer configuration settings that, if not properly secured, may increase exposure.\n\nWe encourage customers to review their Experience Cloud guest user settings and take immediate recommended actions. For additional details and steps to help protect your org, please see our blog: https://www.salesforce.com/blog/protecting-your-data-essential-actions-to-secure-experience-cloud-guest-user-access/","createdAt":"2026-03-07T23:06:36.591Z","updatedAt":"2026-03-07T23:07:25.213Z","entryType":"informational_message_created","sourceId":20000244,"sourceType":"message"}],"productKeys":[],"InformationalMessageUpdates":[{"id":20000406,"message":"Salesforce is actively monitoring threat activity targeting public-facing Experience Cloud sites, including attempts to take advantage of overly permissive guest user configurations.\n\nWe have identified additional guidance for customers to help protect their orgs. Please see our updated blog for recommended actions: https://www.salesforce.com/blog/protecting-your-data-essential-actions-to-secure-experience-cloud-guest-user-access/\n\nAt this time, we have not identified any vulnerability inherent to the Salesforce platform associated with this activity.","createdAt":"2026-03-12T20:20:56.359Z","updatedAt":"2026-03-12T20:20:56.361Z","GeneralMessageId":20000244}]},{"id":20000224,"subject":"Security Advisory: Ongoing Response to Social Engineering Threats","body":"We are aware of recent extortion attempts by threat actors, which we have investigated in partnership with external experts and authorities. Our findings indicate these attempts relate to past or unsubstantiated incidents, and we remain engaged with affected customers to provide support. At this time, there is no indication that the Salesforce platform has been compromised, nor is this activity related to any known vulnerability in our technology.\nOur security teams are actively working to protect customer environments and data, providing guidance and support. Customers identified as potentially affected have been notified directly. If you have not received a notification, we currently have no evidence suggesting any impact to your account. We continue to monitor the situation closely and encourage customers to remain vigilant against phishing and social engineering attempts, which remain common tactics used by threat actors.\n\nFor guidance, please review our blog post (https://www.salesforce.com/blog/protect-against-social-engineering), knowledge article (https://help.salesforce.com/s/articleView?id=005226734&type=1), and reach out through the Salesforce Help portal if you need support.","incidentId":null,"publicView":true,"startDate":"2025-10-02T14:50:00.000Z","endDate":null,"createdAt":"2025-10-02T15:58:29.023Z","updatedAt":"2025-10-17T11:49:26.040Z","externalId":null,"isVisibleWhenClosed":false,"isVisible":true,"informationalMessageType":"informationalMessage","status":"Active","timeline":[{"title":"Update","content":"Salesforce is monitoring social engineering campaigns targeting third-party identity providers (IdPs) across the industry. In these attacks, threat actors use fraudulent login pages or impersonate IT support through voice calls to steal credentials or MFA codes, or to trick users into authorizing malicious connected apps. If an IdP account is compromised, attackers may attempt to access connected applications.\n\nPlease note this issue does not stem from a vulnerability inherent to Salesforce; these attacks rely on social engineering and deceptive authentication prompts.\n\nOur security teams are actively working to protect customers and have notified potentially affected accounts. For guidance and mitigations, please review our blog post (https://www.salesforce.com/blog/protecting-salesforce-data-after-an-identity-compromise/) and knowledge article (https://help.salesforce.com/s/articleView?language=en_US&id=005226734&type=1). For support, contact Salesforce Customer Support via https://help.salesforce.com/s/?language=en_US.","createdAt":"2026-01-30T15:58:12.170Z","updatedAt":"2026-01-30T15:58:12.172Z","entryType":"informational_message_update","sourceId":20000402,"sourceType":"update"},{"title":"Security Advisory: Ongoing Response to Social Engineering Threats","content":"We are aware of recent extortion attempts by threat actors, which we have investigated in partnership with external experts and authorities. Our findings indicate these attempts relate to past or unsubstantiated incidents, and we remain engaged with affected customers to provide support. At this time, there is no indication that the Salesforce platform has been compromised, nor is this activity related to any known vulnerability in our technology.\nOur security teams are actively working to protect customer environments and data, providing guidance and support. Customers identified as potentially affected have been notified directly. If you have not received a notification, we currently have no evidence suggesting any impact to your account. We continue to monitor the situation closely and encourage customers to remain vigilant against phishing and social engineering attempts, which remain common tactics used by threat actors.\n\nFor guidance, please review our blog post (https://www.salesforce.com/blog/protect-against-social-engineering), knowledge article (https://help.salesforce.com/s/articleView?id=005226734&type=1), and reach out through the Salesforce Help portal if you need support.","createdAt":"2025-10-02T15:58:29.023Z","updatedAt":"2025-10-17T11:49:26.040Z","entryType":"informational_message_created","sourceId":20000224,"sourceType":"message"}],"productKeys":[],"InformationalMessageUpdates":[{"id":20000402,"message":"Salesforce is monitoring social engineering campaigns targeting third-party identity providers (IdPs) across the industry. In these attacks, threat actors use fraudulent login pages or impersonate IT support through voice calls to steal credentials or MFA codes, or to trick users into authorizing malicious connected apps. If an IdP account is compromised, attackers may attempt to access connected applications.\n\nPlease note this issue does not stem from a vulnerability inherent to Salesforce; these attacks rely on social engineering and deceptive authentication prompts.\n\nOur security teams are actively working to protect customers and have notified potentially affected accounts. For guidance and mitigations, please review our blog post (https://www.salesforce.com/blog/protecting-salesforce-data-after-an-identity-compromise/) and knowledge article (https://help.salesforce.com/s/articleView?language=en_US&id=005226734&type=1). For support, contact Salesforce Customer Support via https://help.salesforce.com/s/?language=en_US.","createdAt":"2026-01-30T15:58:12.170Z","updatedAt":"2026-01-30T15:58:12.172Z","GeneralMessageId":20000224}]},{"id":20000262,"subject":"Manage Connected Apps Feature Disruption","body":"Issue: On August 24, 2026, we became aware of a subset of customers who are experiencing timeout errors when trying to load the \"Manage Connected Apps\" page. This was caused by an authentication call introduced in version 264 and later backported to version 262.\n\nImpact: Some customers are unable to load the \"Manage Connected Apps\" page.\n\nNext Update: We will provide updated information and more details as soon as they become available.\n","incidentId":null,"publicView":true,"startDate":"2026-08-18T22:00:00.000Z","endDate":"2026-08-24T18:52:00.000Z","createdAt":"2026-08-24T17:11:09.572Z","updatedAt":"2026-08-24T18:54:19.763Z","externalId":"94489014","isVisibleWhenClosed":false,"isVisible":true,"informationalMessageType":"informationalMessage","status":"Resolved","timeline":[{"title":"Update","content":"We've resolved this issue by implementing a fix that disabled the impacted functionality. This restored the \"Manage Connected Apps\" page to normal operation. We apologize for how this incident may have affected your business. We will thoroughly investigate this incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.","createdAt":"2026-08-24T18:54:19.758Z","updatedAt":"2026-08-24T18:54:19.760Z","entryType":"informational_message_update","sourceId":20000453,"sourceType":"update"},{"title":"Update","content":"Update 1: \nUpon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of this Trust post to August 18, 2026 at 22:00 UTC, to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.\n\nWe identified the technical trigger and we're preparing to implement a fix to resolve the impact. Thank you for your patience while we work to implement a permanent fix for this issue. We'll provide an update in 2 hours or sooner if additional information becomes available.","createdAt":"2026-08-24T17:52:37.831Z","updatedAt":"2026-08-24T17:52:37.834Z","entryType":"informational_message_update","sourceId":20000452,"sourceType":"update"},{"title":"Manage Connected Apps Feature Disruption","content":"Issue: On August 24, 2026, we became aware of a subset of customers who are experiencing timeout errors when trying to load the \"Manage Connected Apps\" page. This was caused by an authentication call introduced in version 264 and later backported to version 262.\n\nImpact: Some customers are unable to load the \"Manage Connected Apps\" page.\n\nNext Update: We will provide updated information and more details as soon as they become available.\n","createdAt":"2026-08-24T17:11:09.572Z","updatedAt":"2026-08-24T18:54:19.763Z","entryType":"informational_message_created","sourceId":20000262,"sourceType":"message"}],"productKeys":[],"InformationalMessageUpdates":[{"id":20000452,"message":"Update 1: \nUpon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of this Trust post to August 18, 2026 at 22:00 UTC, to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.\n\nWe identified the technical trigger and we're preparing to implement a fix to resolve the impact. Thank you for your patience while we work to implement a permanent fix for this issue. We'll provide an update in 2 hours or sooner if additional information becomes available.","createdAt":"2026-08-24T17:52:37.831Z","updatedAt":"2026-08-24T17:52:37.834Z","GeneralMessageId":20000262},{"id":20000453,"message":"We've resolved this issue by implementing a fix that disabled the impacted functionality. This restored the \"Manage Connected Apps\" page to normal operation. We apologize for how this incident may have affected your business. We will thoroughly investigate this incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.","createdAt":"2026-08-24T18:54:19.758Z","updatedAt":"2026-08-24T18:54:19.760Z","GeneralMessageId":20000262}]},{"id":20000263,"subject":"Chrome 152 users may experience managed package applications or Lightning Components not functioning as expected","body":"We are aware of an issue affecting Salesforce customers using Chrome 152 that may prevent certain managed package applications or Lightning Components on the Salesforce Platform from functioning as expected. Salesforce engineering teams identified the issue and is working on an expedited fix for fleetwide deployment during the normal release windows, including both Sandbox and Production environments.\n\nCustomers experiencing this issue can refer to the existing Known Issue for additional details here: https://sfdc.co/b68l5w.\n","incidentId":"94940043","publicView":true,"startDate":"2026-09-04T01:42:00.000Z","endDate":"2026-09-06T07:00:00.000Z","createdAt":"2026-09-03T19:12:49.937Z","updatedAt":"2026-09-06T16:58:52.703Z","externalId":"94940043","isVisibleWhenClosed":false,"isVisible":true,"informationalMessageType":"informationalMessage","status":"Resolved","timeline":[{"title":"Update","content":"We identified an issue affecting Salesforce customers using Chrome 152 that prevented certain managed package applications and Lightning Components on the Salesforce Platform from functioning as expected. A fix has been fully deployed across Sandbox and Production environments, and the affected features are now restored. We apologize for how this incident affected you and your business.","createdAt":"2026-09-06T16:58:52.700Z","updatedAt":"2026-09-06T16:58:52.702Z","entryType":"informational_message_update","sourceId":20000456,"sourceType":"update"},{"title":"Update","content":"We have successfully deployed the fix across  across our fleet. Initial reports have indicated positive results.\nWe are in the process of completing additional validations and checks.\n\nWe’ll provide an update once the validation is completed, or sooner if additional information becomes available.","createdAt":"2026-09-06T14:12:03.971Z","updatedAt":"2026-09-06T14:12:03.973Z","entryType":"informational_message_update","sourceId":20000455,"sourceType":"update"},{"title":"Update","content":"We have verified a fix and begun deploying it across our fleet. We expect all environments to receive this update by September 6, 2026.\n\nCustomers using Chrome 152 may continue to experience issues with certain custom app features and page components until the fix reaches their environment. Please refer to the Known Issue article: https://sfdc.co/b68l5w for the workaround.\n\nWe'll provide our next update within 24 hours or sooner if there's new information.","createdAt":"2026-09-04T04:45:12.464Z","updatedAt":"2026-09-04T05:00:56.896Z","entryType":"informational_message_update","sourceId":20000454,"sourceType":"update"},{"title":"Chrome 152 users may experience managed package applications or Lightning Components not functioning as expected","content":"We are aware of an issue affecting Salesforce customers using Chrome 152 that may prevent certain managed package applications or Lightning Components on the Salesforce Platform from functioning as expected. Salesforce engineering teams identified the issue and is working on an expedited fix for fleetwide deployment during the normal release windows, including both Sandbox and Production environments.\n\nCustomers experiencing this issue can refer to the existing Known Issue for additional details here: https://sfdc.co/b68l5w.\n","createdAt":"2026-09-03T19:12:49.937Z","updatedAt":"2026-09-06T16:58:52.703Z","entryType":"informational_message_created","sourceId":20000263,"sourceType":"message"}],"productKeys":[],"InformationalMessageUpdates":[{"id":20000454,"message":"We have verified a fix and begun deploying it across our fleet. We expect all environments to receive this update by September 6, 2026.\n\nCustomers using Chrome 152 may continue to experience issues with certain custom app features and page components until the fix reaches their environment. Please refer to the Known Issue article: https://sfdc.co/b68l5w for the workaround.\n\nWe'll provide our next update within 24 hours or sooner if there's new information.","createdAt":"2026-09-04T04:45:12.464Z","updatedAt":"2026-09-04T05:00:56.896Z","GeneralMessageId":20000263},{"id":20000455,"message":"We have successfully deployed the fix across  across our fleet. Initial reports have indicated positive results.\nWe are in the process of completing additional validations and checks.\n\nWe’ll provide an update once the validation is completed, or sooner if additional information becomes available.","createdAt":"2026-09-06T14:12:03.971Z","updatedAt":"2026-09-06T14:12:03.973Z","GeneralMessageId":20000263},{"id":20000456,"message":"We identified an issue affecting Salesforce customers using Chrome 152 that prevented certain managed package applications and Lightning Components on the Salesforce Platform from functioning as expected. A fix has been fully deployed across Sandbox and Production environments, and the affected features are now restored. We apologize for how this incident affected you and your business.","createdAt":"2026-09-06T16:58:52.700Z","updatedAt":"2026-09-06T16:58:52.702Z","GeneralMessageId":20000263}]},{"id":20000264,"subject":"Intermittent UI Freezing on Salesforce in Chrome and Edge 153","body":"We’re aware of an issue affecting some customers using Chrome and Microsoft Edge version 153, where Salesforce pages may intermittently freeze or become unresponsive across multiple workflows. \n\nWe have identified this as a non-Salesforce issue. The incident was triggered by an external environmental change, specifically the auto-update of Chromium-based browsers (Chrome and Microsoft Edge) to version 153, which began around 2026-09-08.","incidentId":null,"publicView":true,"startDate":"2026-09-07T18:30:00.000Z","endDate":"2026-09-17T20:59:00.000Z","createdAt":"2026-09-11T19:58:39.772Z","updatedAt":"2026-09-17T22:57:58.384Z","externalId":"95258214","isVisibleWhenClosed":false,"isVisible":true,"informationalMessageType":"informationalMessage","status":"Resolved","timeline":[{"title":"Update","content":"The provider has released a fix in Chromium version 153.0.8010.52, which is now available for browser updates.\n\nChrome:\nTo update, select the three dots in the top-right corner of the browser, then go to Help → About. Restart the browser when prompted to apply the update.\n\nEdge:\nBrowser updates are managed by the vendor and are typically released on a two-week cadence. As of September 10, the current version is 153.0.4234.32. To check for and apply an update, select the three dots in the top-right corner of the browser, then go to Help and feedback → About. Restart the browser when prompted.\n\nFor more information regarding Edge browser update cadences, you can refer to the browser vendor's website for additional details and the latest stable channel release.","createdAt":"2026-09-17T22:57:58.381Z","updatedAt":"2026-09-17T22:57:58.382Z","entryType":"informational_message_update","sourceId":20000467,"sourceType":"update"},{"title":"Update","content":"The vendor has released a fix for the intermittent freezing issue affecting Chrome 153 version. Customers using Chrome should update to the latest available version, which resolves the issue.\n\nCustomers using Microsoft Edge 153 version may continue to experience intermittent freezing, as the fix for Edge browser is still pending.\n\nWe recommend that affected Chrome customers update their browser as soon as possible. Customers who cannot update immediately may continue to experience the issue. If freezing persists after updating to the latest Chrome version, please contact Salesforce Support.\n\nFor additional details about the Chrome fix, please refer to the KA: https://help.salesforce.com/s/articleView?id=005459650&type=1","createdAt":"2026-09-16T05:13:32.794Z","updatedAt":"2026-09-16T05:13:32.797Z","entryType":"informational_message_update","sourceId":20000466,"sourceType":"update"},{"title":"Update","content":"We are reopening this informational message to ensure that affected customers are provided with any information we have regarding this third-party issue.\n\nWe are continuing to receive reports of intermittent freezing on the Salesforce UI affecting a subset of customers using certain browser versions. We are working with our third-party vendor to prioritize this issue and drive resolution for all affected customers. \n\nWe'll provide another update as additional information becomes available.","createdAt":"2026-09-14T17:21:35.125Z","updatedAt":"2026-09-14T17:21:35.127Z","entryType":"informational_message_update","sourceId":20000465,"sourceType":"update"},{"title":"Update","content":"Upon further investigation, we have identified this as a non-Salesforce issue. The incident was triggered by an external environmental change, specifically the auto-update of Chromium-based browsers (Chrome and Microsoft Edge) to version 153, which began around 2026-09-08. While this browser update was the primary trigger, the direct cause of the UI freeze was not within Salesforce's codebase.\n\nWe have also published a knowledge article that provides additional information.\n\nKnowledge article link: https://help.salesforce.com/s/articleView?id=005459650&type=1","createdAt":"2026-09-12T03:02:13.984Z","updatedAt":"2026-09-14T17:26:00.236Z","entryType":"informational_message_update","sourceId":20000461,"sourceType":"update"},{"title":"Update","content":"We continue to investigate intermittent Salesforce UI freezing affecting some customers using Chrome or Microsoft Edge version 153 on Windows. A customer-side investigation has shown that when the problem happens, the page may still scroll but will stop receiving mouse and pointer events. A browser setting that was tested before did not fix the problem. Our teams are now collecting deeper browser-level diagnostic logs and preparing to engage third-party vendor to help isolate the cause. \n\nWe’ll provide another update upon significant update.","createdAt":"2026-09-11T23:45:11.762Z","updatedAt":"2026-09-11T23:45:11.765Z","entryType":"informational_message_update","sourceId":20000460,"sourceType":"update"},{"title":"Update","content":"We continue to investigate intermittent Salesforce UI freezing affecting some customers using Chrome or Microsoft Edge version 153 on Windows. Customer-side debugging has shown that, when the issue occurs, the page may remain scrollable but will stop receiving mouse and pointer events, and a previously-tested browser setting did not resolve the behavior. Our teams are now collecting deeper browser-level diagnostic logs and preparing to engage the third-party vendor to help isolate the cause. \n\nWe’ll provide another update in 60 minutes or sooner.","createdAt":"2026-09-11T22:36:16.072Z","updatedAt":"2026-09-11T22:36:16.073Z","entryType":"informational_message_update","sourceId":20000459,"sourceType":"update"},{"title":"Update","content":"We continue to investigate reports of intermittent Salesforce UI freezing for some customers using Chrome or Microsoft Edge version 153 on Windows. We’ve confirmed the behavior can occur across both console and non-console applications, and are continuing to review diagnostic data to determine the trigger. A browser configuration change tested during the investigation did not resolve the issue. Where organizational policies permit, using another supported browser or reverting to version 152 may provide temporary relief. \n\nWe’ll provide another update in 60 minutes or sooner.","createdAt":"2026-09-11T21:42:58.433Z","updatedAt":"2026-09-11T21:42:58.436Z","entryType":"informational_message_update","sourceId":20000458,"sourceType":"update"},{"title":"Update","content":"We continue to investigate reports of intermittent Salesforce UI freezing for some customers using Chrome or Microsoft Edge version 153 on Windows. The issue may occur while switching between Salesforce tabs and can leave the page unresponsive. We’ve engaged additional engineering resources and are reviewing customer-provided recordings, browser information, and affected environment data while working to reproduce the behavior internally. Where permitted by organizational device-management policies, using another supported browser or reverting to version 152 may provide a temporary workaround, though this may not be feasible for all customers. \nWe’ll provide another update in 60 minutes or sooner.","createdAt":"2026-09-11T20:33:43.773Z","updatedAt":"2026-09-11T20:33:43.775Z","entryType":"informational_message_update","sourceId":20000457,"sourceType":"update"},{"title":"Intermittent UI Freezing on Salesforce in Chrome and Edge 153","content":"We’re aware of an issue affecting some customers using Chrome and Microsoft Edge version 153, where Salesforce pages may intermittently freeze or become unresponsive across multiple workflows. \n\nWe have identified this as a non-Salesforce issue. The incident was triggered by an external environmental change, specifically the auto-update of Chromium-based browsers (Chrome and Microsoft Edge) to version 153, which began around 2026-09-08.","createdAt":"2026-09-11T19:58:39.772Z","updatedAt":"2026-09-17T22:57:58.384Z","entryType":"informational_message_created","sourceId":20000264,"sourceType":"message"}],"productKeys":[],"InformationalMessageUpdates":[{"id":20000457,"message":"We continue to investigate reports of intermittent Salesforce UI freezing for some customers using Chrome or Microsoft Edge version 153 on Windows. The issue may occur while switching between Salesforce tabs and can leave the page unresponsive. We’ve engaged additional engineering resources and are reviewing customer-provided recordings, browser information, and affected environment data while working to reproduce the behavior internally. Where permitted by organizational device-management policies, using another supported browser or reverting to version 152 may provide a temporary workaround, though this may not be feasible for all customers. \nWe’ll provide another update in 60 minutes or sooner.","createdAt":"2026-09-11T20:33:43.773Z","updatedAt":"2026-09-11T20:33:43.775Z","GeneralMessageId":20000264},{"id":20000458,"message":"We continue to investigate reports of intermittent Salesforce UI freezing for some customers using Chrome or Microsoft Edge version 153 on Windows. We’ve confirmed the behavior can occur across both console and non-console applications, and are continuing to review diagnostic data to determine the trigger. A browser configuration change tested during the investigation did not resolve the issue. Where organizational policies permit, using another supported browser or reverting to version 152 may provide temporary relief. \n\nWe’ll provide another update in 60 minutes or sooner.","createdAt":"2026-09-11T21:42:58.433Z","updatedAt":"2026-09-11T21:42:58.436Z","GeneralMessageId":20000264},{"id":20000459,"message":"We continue to investigate intermittent Salesforce UI freezing affecting some customers using Chrome or Microsoft Edge version 153 on Windows. Customer-side debugging has shown that, when the issue occurs, the page may remain scrollable but will stop receiving mouse and pointer events, and a previously-tested browser setting did not resolve the behavior. Our teams are now collecting deeper browser-level diagnostic logs and preparing to engage the third-party vendor to help isolate the cause. \n\nWe’ll provide another update in 60 minutes or sooner.","createdAt":"2026-09-11T22:36:16.072Z","updatedAt":"2026-09-11T22:36:16.073Z","GeneralMessageId":20000264},{"id":20000460,"message":"We continue to investigate intermittent Salesforce UI freezing affecting some customers using Chrome or Microsoft Edge version 153 on Windows. A customer-side investigation has shown that when the problem happens, the page may still scroll but will stop receiving mouse and pointer events. A browser setting that was tested before did not fix the problem. Our teams are now collecting deeper browser-level diagnostic logs and preparing to engage third-party vendor to help isolate the cause. \n\nWe’ll provide another update upon significant update.","createdAt":"2026-09-11T23:45:11.762Z","updatedAt":"2026-09-11T23:45:11.765Z","GeneralMessageId":20000264},{"id":20000461,"message":"Upon further investigation, we have identified this as a non-Salesforce issue. The incident was triggered by an external environmental change, specifically the auto-update of Chromium-based browsers (Chrome and Microsoft Edge) to version 153, which began around 2026-09-08. While this browser update was the primary trigger, the direct cause of the UI freeze was not within Salesforce's codebase.\n\nWe have also published a knowledge article that provides additional information.\n\nKnowledge article link: https://help.salesforce.com/s/articleView?id=005459650&type=1","createdAt":"2026-09-12T03:02:13.984Z","updatedAt":"2026-09-14T17:26:00.236Z","GeneralMessageId":20000264},{"id":20000465,"message":"We are reopening this informational message to ensure that affected customers are provided with any information we have regarding this third-party issue.\n\nWe are continuing to receive reports of intermittent freezing on the Salesforce UI affecting a subset of customers using certain browser versions. We are working with our third-party vendor to prioritize this issue and drive resolution for all affected customers. \n\nWe'll provide another update as additional information becomes available.","createdAt":"2026-09-14T17:21:35.125Z","updatedAt":"2026-09-14T17:21:35.127Z","GeneralMessageId":20000264},{"id":20000466,"message":"The vendor has released a fix for the intermittent freezing issue affecting Chrome 153 version. Customers using Chrome should update to the latest available version, which resolves the issue.\n\nCustomers using Microsoft Edge 153 version may continue to experience intermittent freezing, as the fix for Edge browser is still pending.\n\nWe recommend that affected Chrome customers update their browser as soon as possible. Customers who cannot update immediately may continue to experience the issue. If freezing persists after updating to the latest Chrome version, please contact Salesforce Support.\n\nFor additional details about the Chrome fix, please refer to the KA: https://help.salesforce.com/s/articleView?id=005459650&type=1","createdAt":"2026-09-16T05:13:32.794Z","updatedAt":"2026-09-16T05:13:32.797Z","GeneralMessageId":20000264},{"id":20000467,"message":"The provider has released a fix in Chromium version 153.0.8010.52, which is now available for browser updates.\n\nChrome:\nTo update, select the three dots in the top-right corner of the browser, then go to Help → About. Restart the browser when prompted to apply the update.\n\nEdge:\nBrowser updates are managed by the vendor and are typically released on a two-week cadence. As of September 10, the current version is 153.0.4234.32. To check for and apply an update, select the three dots in the top-right corner of the browser, then go to Help and feedback → About. Restart the browser when prompted.\n\nFor more information regarding Edge browser update cadences, you can refer to the browser vendor's website for additional details and the latest stable channel release.","createdAt":"2026-09-17T22:57:58.381Z","updatedAt":"2026-09-17T22:57:58.382Z","GeneralMessageId":20000264}]},{"id":20000265,"subject":"Data Cloud CRM Connector Issue on Sandbox Environments","body":"We’re aware of an issue affecting the Data Cloud CRM Connector ingesting data from sandbox environments. Customers can’t verify connections or deploy CRM streams, which impacts connection setup and data stream deployment. We identified a connection error occurring when the connector calls backend services, and we’re actively investigating the cause. We’ll provide an update upon significant update or if additional information becomes available.","incidentId":null,"publicView":true,"startDate":"2026-09-01T20:34:00.000Z","endDate":"2026-09-12T20:46:00.000Z","createdAt":"2026-09-12T01:39:34.063Z","updatedAt":"2026-09-12T20:48:49.919Z","externalId":"95264805","isVisibleWhenClosed":false,"isVisible":true,"informationalMessageType":"informationalMessage","status":"Resolved","timeline":[{"title":"Update","content":"We identified a network configuration change affecting the Data Cloud CRM Connector on sandbox environments, preventing some customers from verifying connections or deploying CRM streams. We rolled back the change across all affected environments.. Connections and stream deployments are now fully restored. 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.","createdAt":"2026-09-12T20:46:43.994Z","updatedAt":"2026-09-12T20:46:43.996Z","entryType":"informational_message_update","sourceId":20000464,"sourceType":"update"},{"title":"Update","content":"We're continuing to work on restoring the Data Cloud CRM Connector for customers on affected sandbox environments. We identified a network configuration change coinciding with the start of impact and completed targeted rollbacks on two environments. The issue has since been found affecting additional sandboxes, and remediation is underway. We're also contacting a small number of customers to coordinate extra steps needed to repair their connection settings. We’ll provide an update upon significant update or if additional information becomes available.","createdAt":"2026-09-12T16:31:58.904Z","updatedAt":"2026-09-12T16:31:58.906Z","entryType":"informational_message_update","sourceId":20000463,"sourceType":"update"},{"title":"Update","content":"We identified the potential cause of the issue and are working on implementing a fix to resolve the impact on customers.","createdAt":"2026-09-12T05:34:03.970Z","updatedAt":"2026-09-12T05:34:03.972Z","entryType":"informational_message_update","sourceId":20000462,"sourceType":"update"},{"title":"Data Cloud CRM Connector Issue on Sandbox Environments","content":"We’re aware of an issue affecting the Data Cloud CRM Connector ingesting data from sandbox environments. Customers can’t verify connections or deploy CRM streams, which impacts connection setup and data stream deployment. We identified a connection error occurring when the connector calls backend services, and we’re actively investigating the cause. We’ll provide an update upon significant update or if additional information becomes available.","createdAt":"2026-09-12T01:39:34.063Z","updatedAt":"2026-09-12T20:48:49.919Z","entryType":"informational_message_created","sourceId":20000265,"sourceType":"message"}],"productKeys":[],"InformationalMessageUpdates":[{"id":20000462,"message":"We identified the potential cause of the issue and are working on implementing a fix to resolve the impact on customers.","createdAt":"2026-09-12T05:34:03.970Z","updatedAt":"2026-09-12T05:34:03.972Z","GeneralMessageId":20000265},{"id":20000463,"message":"We're continuing to work on restoring the Data Cloud CRM Connector for customers on affected sandbox environments. We identified a network configuration change coinciding with the start of impact and completed targeted rollbacks on two environments. The issue has since been found affecting additional sandboxes, and remediation is underway. We're also contacting a small number of customers to coordinate extra steps needed to repair their connection settings. We’ll provide an update upon significant update or if additional information becomes available.","createdAt":"2026-09-12T16:31:58.904Z","updatedAt":"2026-09-12T16:31:58.906Z","GeneralMessageId":20000265},{"id":20000464,"message":"We identified a network configuration change affecting the Data Cloud CRM Connector on sandbox environments, preventing some customers from verifying connections or deploying CRM streams. We rolled back the change across all affected environments.. Connections and stream deployments are now fully restored. 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.","createdAt":"2026-09-12T20:46:43.994Z","updatedAt":"2026-09-12T20:46:43.996Z","GeneralMessageId":20000265}]},{"id":20000246,"subject":"How Salesforce is preparing for the frontier AI threat landscape","body":"Anthropic’s announcement of Claude Mythos underscores a reality Salesforce has been preparing for: increasingly capable frontier AI models will continue to accelerate the evolution of the cybersecurity landscape.\n\nOur security teams are continuously evaluating how frontier models like Mythos may change attacker and defender capabilities, and we are applying those insights to strengthen our security posture and guide continued enhancements across our environment.\n\nWe view this as an acceleration of work already underway, not a departure from it. Salesforce has long invested in automation and AI to help identify risk, strengthen defenses, and support the trust our customers place in us.\n\nTrust remains our #1 value, and we remain focused on helping protect our customers’ data in a rapidly evolving threat environment.","incidentId":null,"publicView":true,"startDate":"2026-04-14T06:23:00.000Z","endDate":null,"createdAt":"2026-04-13T23:24:55.319Z","updatedAt":"2026-04-13T23:24:55.322Z","externalId":null,"isVisibleWhenClosed":false,"isVisible":true,"informationalMessageType":"informationalMessage","status":"Active","timeline":[{"title":"How Salesforce is preparing for the frontier AI threat landscape","content":"Anthropic’s announcement of Claude Mythos underscores a reality Salesforce has been preparing for: increasingly capable frontier AI models will continue to accelerate the evolution of the cybersecurity landscape.\n\nOur security teams are continuously evaluating how frontier models like Mythos may change attacker and defender capabilities, and we are applying those insights to strengthen our security posture and guide continued enhancements across our environment.\n\nWe view this as an acceleration of work already underway, not a departure from it. Salesforce has long invested in automation and AI to help identify risk, strengthen defenses, and support the trust our customers place in us.\n\nTrust remains our #1 value, and we remain focused on helping protect our customers’ data in a rapidly evolving threat environment.","createdAt":"2026-04-13T23:24:55.319Z","updatedAt":"2026-04-13T23:24:55.322Z","entryType":"informational_message_created","sourceId":20000246,"sourceType":"message"}],"productKeys":[],"InformationalMessageUpdates":[]},{"id":20000227,"subject":"Security Alert: Phishing Campaign with Malicious links","body":"Salesforce is aware of and closely monitoring a phishing campaign appearing as fraudulent emails from Salesforce with a malicious link to download Remote Monitoring & Management (RMM) software.\n\nOur security teams are working diligently to contain this issue and urge all customers to maintain a high level of vigilance against phishing and social engineering attempts, as these remain frequently used tactics by threat actors. If you receive requests from Salesforce to install RMM software, we recommend you validate its legitimacy with Salesforce Support or architect teams prior to taking action by opening up a ticket through the Salesforce Help portal.\n\nFor guidance and support, please reach out through the Salesforce Help portal. You can also refer to this article for guidance on how to protect your environments from social engineering threats: https://www.salesforce.com/blog/protect-against-social-engineering/. ","incidentId":null,"publicView":true,"startDate":"2025-10-21T14:48:00.000Z","endDate":null,"createdAt":"2025-10-22T01:49:54.286Z","updatedAt":"2025-10-22T02:17:32.054Z","externalId":null,"isVisibleWhenClosed":false,"isVisible":true,"informationalMessageType":"informationalMessage","status":"Active","timeline":[{"title":"Security Alert: Phishing Campaign with Malicious links","content":"Salesforce is aware of and closely monitoring a phishing campaign appearing as fraudulent emails from Salesforce with a malicious link to download Remote Monitoring & Management (RMM) software.\n\nOur security teams are working diligently to contain this issue and urge all customers to maintain a high level of vigilance against phishing and social engineering attempts, as these remain frequently used tactics by threat actors. If you receive requests from Salesforce to install RMM software, we recommend you validate its legitimacy with Salesforce Support or architect teams prior to taking action by opening up a ticket through the Salesforce Help portal.\n\nFor guidance and support, please reach out through the Salesforce Help portal. You can also refer to this article for guidance on how to protect your environments from social engineering threats: https://www.salesforce.com/blog/protect-against-social-engineering/. ","createdAt":"2025-10-22T01:49:54.286Z","updatedAt":"2025-10-22T02:17:32.054Z","entryType":"informational_message_created","sourceId":20000227,"sourceType":"message"}],"productKeys":[],"InformationalMessageUpdates":[]}],"Maintenances":[{"id":20136698,"message":{"maintenanceType":"release","availability":"available","eventStatus":"confirmed"},"externalId":"a3GEE000000RV1K2AW","name":"Winter '27 Major Release","externalMaintenanceType":"","substrate":"Hyperforce Core","releaseType":"Major","type":"release","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-10T04:30:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2025-12-16T22:50:16.350Z","updatedAt":"2026-08-11T04:02:48.857Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[{"id":20285275,"type":"scheduled","message":"This release is scheduled.","createdAt":"2026-08-11T04:02:48.850Z","updatedAt":"2026-08-11T04:02:48.854Z"}],"timeline":[{"title":"Maintenance Scheduled","content":"This release is scheduled.","createdAt":"2026-08-11T04:02:48.850Z","updatedAt":"2026-08-11T04:02:48.854Z","entryType":"maintenance_scheduled","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-10T04:30:00.000Z","sourceId":20285275,"sourceType":"event"}]},{"id":20141200,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000U66P2AS","name":"Financial Services Cloud - Winter '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-02-25T05:27:05.375Z","updatedAt":"2026-08-11T04:05:21.525Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[{"id":20285565,"type":"scheduled","message":"This release is scheduled.","createdAt":"2026-08-11T04:05:21.521Z","updatedAt":"2026-08-11T04:05:21.523Z"}],"timeline":[{"title":"Maintenance Scheduled","content":"This release is scheduled.","createdAt":"2026-08-11T04:05:21.521Z","updatedAt":"2026-08-11T04:05:21.523Z","entryType":"maintenance_scheduled","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","sourceId":20285565,"sourceType":"event"}]},{"id":20141287,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000U6812AC","name":"Health Cloud - Winter '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-02-25T05:27:27.044Z","updatedAt":"2026-08-11T04:03:41.965Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[{"id":20285363,"type":"scheduled","message":"This release is scheduled.","createdAt":"2026-08-11T04:03:41.960Z","updatedAt":"2026-08-11T04:03:41.963Z"}],"timeline":[{"title":"Maintenance Scheduled","content":"This release is scheduled.","createdAt":"2026-08-11T04:03:41.960Z","updatedAt":"2026-08-11T04:03:41.963Z","entryType":"maintenance_scheduled","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","sourceId":20285363,"sourceType":"event"}]},{"id":20141374,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000U69d2AC","name":"Life Sciences Cloud - Winter '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-02-25T05:27:50.086Z","updatedAt":"2026-08-11T04:04:20.375Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[{"id":20285438,"type":"scheduled","message":"This release is scheduled.","createdAt":"2026-08-11T04:04:20.368Z","updatedAt":"2026-08-11T04:04:20.372Z"}],"timeline":[{"title":"Maintenance Scheduled","content":"This release is scheduled.","createdAt":"2026-08-11T04:04:20.368Z","updatedAt":"2026-08-11T04:04:20.372Z","entryType":"maintenance_scheduled","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","sourceId":20285438,"sourceType":"event"}]},{"id":20148735,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000TAqQ2AW","name":"Communications, Media & Energy - Winter '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-03-05T06:59:25.809Z","updatedAt":"2026-08-11T04:00:46.079Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[{"id":20285143,"type":"scheduled","message":"This release is scheduled.","createdAt":"2026-08-11T04:00:46.071Z","updatedAt":"2026-08-11T04:00:46.075Z"}],"timeline":[{"title":"Maintenance Scheduled","content":"This release is scheduled.","createdAt":"2026-08-11T04:00:46.071Z","updatedAt":"2026-08-11T04:00:46.075Z","entryType":"maintenance_scheduled","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","sourceId":20285143,"sourceType":"event"}]},{"id":20148821,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000TB3J2AW","name":"Insurance, Financial Services Cloud - Winter '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-03-05T06:59:45.496Z","updatedAt":"2026-08-11T04:05:13.958Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[{"id":20285549,"type":"scheduled","message":"This release is scheduled.","createdAt":"2026-08-11T04:05:13.950Z","updatedAt":"2026-08-11T04:05:13.954Z"}],"timeline":[{"title":"Maintenance Scheduled","content":"This release is scheduled.","createdAt":"2026-08-11T04:05:13.950Z","updatedAt":"2026-08-11T04:05:13.954Z","entryType":"maintenance_scheduled","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","sourceId":20285549,"sourceType":"event"}]},{"id":20148908,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000TB1h2AG","name":"Omnistudio - Winter '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-03-05T07:00:10.204Z","updatedAt":"2026-08-11T04:06:22.715Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[{"id":20285690,"type":"scheduled","message":"This release is scheduled.","createdAt":"2026-08-11T04:06:22.710Z","updatedAt":"2026-08-11T04:06:22.713Z"}],"timeline":[{"title":"Maintenance Scheduled","content":"This release is scheduled.","createdAt":"2026-08-11T04:06:22.710Z","updatedAt":"2026-08-11T04:06:22.713Z","entryType":"maintenance_scheduled","plannedStartTime":"2026-10-10T04:00:00.000Z","plannedEndTime":"2026-10-12T04:00:00.000Z","sourceId":20285690,"sourceType":"event"}]},{"id":20164111,"message":{"maintenanceType":"release","availability":"available","eventStatus":"confirmed"},"externalId":"a3GEE000000YcPS2A0","name":"Spring '27 Major Release","externalMaintenanceType":"","substrate":"Hyperforce Core","releaseType":"Major","type":"release","plannedStartTime":"2027-02-20T05:00:00.000Z","plannedEndTime":"2027-02-20T05:30:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-08-20T00:10:40.148Z","updatedAt":"2026-08-20T00:10:40.156Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[],"timeline":[]},{"id":20167058,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000YuhJ2AS","name":"Health Cloud - Spring '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2027-02-20T05:00:00.000Z","plannedEndTime":"2027-02-22T05:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-09-02T04:54:54.430Z","updatedAt":"2026-09-02T04:54:54.441Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[],"timeline":[]},{"id":20167163,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000Yufh2AC","name":"Financial Services Cloud - Spring '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2027-02-20T05:00:00.000Z","plannedEndTime":"2027-02-22T05:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-09-02T04:55:19.210Z","updatedAt":"2026-09-02T04:55:19.217Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[],"timeline":[]},{"id":20167270,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000Z1fZ2AS","name":"Life Sciences Cloud - Spring '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2027-02-20T05:00:00.000Z","plannedEndTime":"2027-02-22T05:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-09-02T04:55:45.853Z","updatedAt":"2026-09-02T04:55:45.863Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[],"timeline":[]},{"id":20170139,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000Yyhh2AC","name":"Communications, Media & Energy - Spring '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2027-02-20T05:00:00.000Z","plannedEndTime":"2027-02-22T05:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-09-02T05:10:43.215Z","updatedAt":"2026-09-02T05:10:43.229Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[],"timeline":[]},{"id":20170245,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000YyjJ2AS","name":"Omnistudio - Spring '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2027-02-20T05:00:00.000Z","plannedEndTime":"2027-02-22T05:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-09-02T05:11:06.657Z","updatedAt":"2026-09-02T05:11:06.666Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[],"timeline":[]},{"id":20170351,"message":{"maintenanceType":"release","availability":"fullyAvailable","eventStatus":"confirmed"},"externalId":"a3GEE000000Yykv2AC","name":"Insurance, Financial Services Cloud - Spring '27 - Major Release","externalMaintenanceType":"","substrate":"Default","releaseType":"Major","type":"release","plannedStartTime":"2027-02-20T05:00:00.000Z","plannedEndTime":"2027-02-22T05:00:00.000Z","additionalInformation":"","isCore":true,"affectsAll":false,"status":"Confirmed","createdAt":"2026-09-02T05:11:29.744Z","updatedAt":"2026-09-02T05:11:29.755Z","instanceKeys":["USA1"],"serviceKeys":["coreService"],"MaintenanceImpacts":[],"MaintenanceEvents":[],"timeline":[]}]}