We can't access to any tcp ports of 15.223.143.32

0

We can't access to 15.223.143.32(EIP) from internet since Jun 9 9:30 PM UTC. We have not changed any security group configurations. Please help to find out the reason as soon as possible, thank you very much.

2 Answers
5

Please check at the following:

  1. Verify Security Group Rules – Ensure inbound and outbound rules allow traffic on the required TCP ports.
  2. Check Network ACLs – Confirm that your Network Access Control Lists (ACLs) aren't blocking traffic.
  3. Inspect Route Table Settings – If this EIP is associated with an AWS instance, verify that the route table correctly directs traffic.
  4. Review AWS Service Health – AWS occasionally experiences regional outages. You can check the AWS Service Health Dashboard for any reported issues.
  5. Run Connectivity Tests – Use telnet 15.223.143.32 <port> or nc -zv 15.223.143.32 <port> to test port accessibility.
  6. Check for Port Exhaustion – If the instance is running Windows, port exhaustion could be a factor.
EXPERT
answered 5 days ago
EXPERT
reviewed 5 days ago
1

What do you mean by you cannot access 15.223.143.32. I can easily ping this IP and it returns a response.

Enter image description here

answered 5 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions