Overview
This article describes how to troubleshoot ping failure of the internet address of an ECS instance.
Description
- Configuration-related: check the ECS instance status and Internet-related configurations.
Prerequisites: a fixed public IP address, an EIP bound, or a NAT Gateway configured with an SNAT entry, is required to access the Internet. - Fees: checks whether the resources have overdue payments.
Check whether your ECS instance has overdue payments, whether your NAT Gateway has overdue payments, and whether your EIP has overdue payments. - Security: you can check the ECS Security Group, Cloud Firewall, and security control status.
For more information, see delete the default security group rules of the ECS instance and ping the ECS instance may fail. - Usage-related actions: checks the usage of Internet resources, for example, 100% Internet bandwidth usage.
- The performance constraint mode of the burstable instance. When the CPU utilization reaches 100%, ping failure or ping packet loss may occur. For more information, see burstable instance overview.
- When the EIP or fixed public IP address resources are occupied, the ping operation may be dropped due to the speed limit and the ping cannot be performed.
- ECS internal configuration: check iptables, third-party VPN Gateway, and cloud lock.
- Linux: see Linux of ECS does not ban ping but only cannot ping the solution.
- Windows: When you ping the internet address of a Windows instance, the system prompts "general fault".
- Carrier problems: check the carrier for network problems, such as public network operator link interruption, route shock, and so on.
See the link test method when the ping command is used for packet loss or fails.
Documentation
Application scope
- Elastic Compute Service
- Virtual Private Cloud