- Newest
- Most votes
- Most comments
We apologize for this inconvenience. I checked the case, and I see that your sending ability has been reinstated. You should be able to send emails now. In the future, if your production is being impacted and you want us to expedite the review of your case (related to SES account pause) please open a Technical support case and request for the same. The technical support team can place an expedite request internally.
However, please note that even technical support cases have their own SLAs. If you need immediate help, you can consider upgrading to a Business Support plan. With this plan, you can initiate chats/calls directly with technical support and request for an expedite.
AWS Support plans - https://aws.amazon.com/premiumsupport/plans/ Thank you.
I understand your frustration with the situation regarding your AWS SES (Simple Email Service) account being paused and the lack of response to your support ticket. This is indeed a critical issue that can severely impact business operations, especially for startups.
When an SES account is paused due to high bounce rates, it's part of AWS's measures to maintain good email sending practices and protect their IP reputation. However, I acknowledge that in cases with low email volume, a single bounce can disproportionately affect the bounce rate percentage.
Regarding the support response, the experience you're describing is not typical of AWS support. Response times can vary based on the support plan level (Basic, Developer, Business, or Enterprise), with higher-tier plans generally receiving faster responses. However, for account and billing support issues, which this appears to be, all customers should receive attention.
Here are some steps you can take to potentially expedite the resolution:
-
If you haven't already, ensure you've responded to the initial notification email about the account pause. Follow their instructions carefully and provide all requested information.
-
In your support case, clearly outline the steps you've taken to address the issue, including any changes to your email sending practices to reduce bounce rates.
-
Explain the critical nature of the service to your business operations and the impact of the outage.
-
If you haven't received a response in over 24-48 hours, you may want to open a new support case specifically about the lack of response to your original case.
-
Consider upgrading your support plan temporarily if possible, as this can sometimes lead to faster response times.
-
Review your email sending practices to ensure compliance with AWS policies, including proper handling of bounces and complaints.
Regarding the startup credits request, these are typically handled separately from technical support issues. You may want to follow up on this through the appropriate channels once the SES issue is resolved.
While waiting for a response, it would be prudent to review your email sending practices and implement any necessary improvements to prevent similar issues in the future. This could include better list management, more robust bounce handling, and improved email content to reduce the likelihood of being marked as spam.
I hope you receive a response soon and that your SES service is restored quickly. Remember to maintain open communication with AWS support and provide any additional information they may request promptly.
Sources
Paused account's ability to send email using SES | AWS re:Post
SES send suspended without notification | AWS re:Post
Seeking Urgent Assistance: SES Account Paused Due to High Complaint Rate, Need Clarification and Resolution Timelines | AWS re:Post
Amazon SES Sending Pause for AWS Account - Not responding for 24 hours on System impaired case | AWS re:Post
Relevant content
- asked 6 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 22 days ago
- AWS OFFICIALUpdated a year ago