SNS - Text messages delivery failure with Rogers Communications Canada Inc.

Question

Hi,

I’ve noticed an increase in SMS delivery failures over the past 2–3 weeks.

After reviewing our logs, I observed that the affected messages all seem to be targeting numbers with the same phone carrier: Rogers Communications Canada Inc.

Has anyone else experienced similar issues recently?

Here’s an example log entry:
Example of log :
{"notification":{"messageId":"7afbd248-c15d-5dc5-955b-b28024560f8f","timestamp":"2025-06-15 15:12:11.095"},"delivery":{"phoneCarrier":"Rogers Communications Canada Inc.","mnc":720,"numberOfMessageParts":2,"destination":"FAKENUMBER","priceInUSD":0.02696,"smsType":"Transactional","mcc":302,"providerResponse":"Unknown error attempting to reach phone","dwellTimeMs":44,"dwellTimeMsUntilDeviceAck":2151},"status":"FAILURE"}

Have a good day,

Best,

FL

re:Post Agent · Answer

Based on your log entry, I can see you're experiencing SMS delivery failures with Rogers Communications Canada Inc. as the carrier, with the error message "Unknown error attempting to reach phone."

There are several potential reasons for these SMS delivery failures:

1. Carrier filtering: Mobile carriers like Rogers may implement their own filtering mechanisms that could be blocking your messages. This could be due to content filtering, volume limitations, or carrier-specific policies.

2. Network issues: There might be temporary network issues or outages affecting delivery to Rogers specifically.

3. Recipient opt-out status: The recipients may have opted out of receiving messages from your number.

4. Message content: Your message content might be triggering spam filters with this specific carrier.

To troubleshoot this issue:

1. Review your message content to ensure it complies with carrier guidelines.

2. Monitor your CloudWatch logs for more detailed error messages or patterns specific to Rogers.

3. Test with different recipient numbers on the Rogers network to determine if the issue is widespread or limited to specific numbers.

4. Enable and review detailed SMS delivery logs to get more information about the failures.

5. Consider reaching out to AWS Support with specific message IDs and timestamps if the issue persists, as they may have more insight into carrier-specific issues.

The "Unknown error attempting to reach phone" message suggests there might be an issue between AWS and the Rogers network that's preventing successful delivery. This could be temporary, but since you've noticed it for 2-3 weeks, it might require further investigation.  
**Sources**  
[SNS SMS Deliverability Issue (TEXT_BLOCKED) Despite 10DLC Registration | AWS re:Post](https://repost.aws/questions/QUaFwoSFh2TN-jqokPoXj7bg/sns-sms-deliverability-issue-text-blocked-despite-10dlc-registration)  
[AWS SNS can not send SMS to mobile phone | AWS re:Post](https://repost.aws/questions/QUVa9lqxT9SeWWTnuZvcrZvQ/aws-sns-can-not-send-sms-to-mobile-phone)  
[Amazon SNS SMS delivery monitoring with Amazon CloudWatch metrics and logs - Amazon Simple Notification Service](https://docs.aws.amazon.com/sns/latest/dg/sms_stats_cloudwatch.html)  
[AWS SNS is sending weird SMS | AWS re:Post](https://repost.aws/questions/QUe6OXU0GBQ8uj1xQBDIQLPQ/aws-sns-is-sending-weird-sms)

SNS - Text messages delivery failure with Rogers Communications Canada Inc.

Adicione sua resposta

Conteúdo relevante