SES Connection Timed out

Based on the information you've provided, it's unlikely that Amazon has blocked your IP. The issue you're experiencing is more likely related to network connectivity or configuration problems specific to the server that can't connect. Here are a few points to consider:

1. IP blocking: Amazon SES doesn't typically block IPs without notification. If there were issues with your account or sending practices, you would usually receive a notification from AWS.

2. Network issues: The fact that one server can connect while another can't suggests a localized network problem rather than an IP block. This could be due to firewall settings, routing issues, or other network configuration problems on the affected server.

3. Security groups: If you're using AWS EC2 instances, check the security group settings for the problematic server. Ensure that outbound rules allow traffic to the SES SMTP endpoints.

4. Port restrictions: If you're using port 25 for SMTP, note that Amazon EC2 restricts this port by default. Try using ports 465 or 587 instead, which are typically unrestricted.

5. VPC configuration: If you're using a VPC, ensure that the network ACLs and route tables are correctly configured to allow outbound traffic to SES.

To troubleshoot further:

1. Check your server's firewall settings and ensure they're not blocking outbound connections to SES endpoints.

2. Verify that your DNS resolution is working correctly on the problematic server.

3. Try connecting to SES using a different port (465 or 587) if you're currently using port 25.

4. Review any recent changes to your network configuration or security settings.

5. If you're using a VPC endpoint for SES, ensure it's correctly configured and the associated security group allows inbound traffic from your application.

If the issue persists after checking these points, it would be advisable to contact AWS Support for further assistance, as they can provide more detailed insights into any potential account-specific issues or regional SES problems.
Sources
Amazon SES SMTP issues - Amazon Simple Email Service
Springboot Java application SES is not working | AWS re:Post
Amazon SES SMTP issues - Amazon Simple Email Service

Severs are on Digital ocean . I am not using Amazon EC2 - Just Amazon SES . No network changes has been made but it not easy to check as I can not ping " email-smtp.us-east-2.amazonaws.com" But I try telnet , works from one VPS and not from another ! both on port 587. How can I check if Amazon has blocked the IP ? I have opened a ticket with Digital Ocean as well but I am sure they will say both severs are on same network and behind same firewall so most likely it is on AWS's side.