We’ve successfully tested the remediation on a subset of codes to backfill the missing data and reprocess the codes. We're now in the process of performing the remediation to all impacted codes.

Update timeline

1. identified Jun 25, 2026, 08:18 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jun 25, 2026, 08:29 AM UTC

   We’re investigating an issue impacting inbound SMS messaging for a subset of Marketing Cloud Growth & Advanced Editions on Core where customers are unable to receive inbound SMS messages or delivery receipts when end users reply to SMS. Outbound SMS messaging is not impacted. We’ve identified the trigger as a recent migration during which certain sender codes were not migrated correctly. The issue is limited to customers using the impacted sender codes. We’re applying the required configuration changes and validating the changes as they are deployed. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 25, 2026, 08:55 AM UTC

   We are implementing a code change to restore service. Before deployment, we’re validating the code changes to ensure it fully resolves the issue without creating additional impact. This validation is taking additional time. We’ll provide another update in 60 minutes or sooner if additional information becomes available.

4. monitoring Jun 25, 2026, 09:55 AM UTC

   Investigation has identified two contributing issues impacting inbound event processing. The first issue was caused by a synchronization gap that prevented a required configuration field from being propagated for a subset of sender codes. A remediation has been applied, and validation across multiple regions confirms inbound event processing has resumed for remediated codes. During the investigation, we identified a second issue impacting a subset of codes that were not fully synchronized between dependent systems. We've implemented a targeted remediation to backfill the missing data and reprocess impacted codes. The remediation is being validated on a limited set of records before being rolled out in phases to all impacted codes to ensure newly provisioned codes are not impacted by this synchronization issue. The implementations will take 2 to 3 hours and will provide an update as additional information becomes available.

5. monitoring Jun 25, 2026, 11:35 AM UTC

   We’ve successfully tested the remediation on a subset of codes to backfill the missing data and reprocess the codes. We're now in the process of performing the remediation to all impacted codes. We'll provide the next update in 60 minutes or sooner if additional information becomes available.