Invalid Recipient Error Exceeds Threshold Impacting Twilio Messaging Channels

The issue with "Invalid recipient" errors due to a high volume of INBOUND_RECEIPT events with invalid remoteId values has been resolved and is operating normally at this time.

Our engineers have deployed a fix to address the high volume of INBOUND_RECEIPT events with invalid remoteId values, which previously caused a spike in "Invalid recipient" errors. We will continue to monitor for system stability. We’ll provide another update in 30 minutes or sooner if more information becomes available. Thank you for your patience as we resolved this issue.

Our engineers have identified the issue as a high volume of INBOUND_RECEIPT events with invalid remoteId values, which is causing a spike in "Invalid recipient" errors. They are actively working on deploying a fix. We expect to provide another update in 2 hours or as soon as more information becomes available.

Our engineers have identified the issue as a high volume of INBOUND_RECEIPT events with invalid remoteId values, which is causing a spike in "Invalid recipient" errors. They are actively working on deploying a fix. We expect to provide another update in 1 hour or as soon as more information becomes available.