Troubleshoot ECS-to-Lindorm Connectivity via Ping Test - Lindorm

Run ping from your ECS instance to verify basic network reachability to a Lindorm instance. This is useful after creating a new Lindorm instance or when an existing instance becomes unreachable.

Prerequisites

Before you begin, ensure that you have:

A running ECS instance with access to the Lindorm instance
The Lindorm instance endpoint (see View endpoints)

Test connectivity

Log on to the ECS instance.
Run the following command, replacing <host> with the endpoint you retrieved. Use the hostname only — do not include the port number.
Windows — stops automatically after four attempts:
```
ping <host>
```
To run a continuous test on Windows:
```
ping <host> -t
```
Linux — runs continuously until you press Ctrl+C:
```
ping <host>
```
Press Ctrl+C to stop and view statistics. Example:
```
ping ld-bp1mq0tdzbx1m****-proxy-lindorm-pub.lindorm.aliyuncs.com
```
Review the output.
The following examples use the Lindorm time series engine endpoint.
Windows:
Linux:

Interpret the results

Result	Status	Next step
All replies show bytes received and response times	Normal — the network path is reachable	No action needed
Request timed out or 100% packet loss	Abnormal — the instance is unreachable	Check your whitelist and security group settings (see below)

If the connection is abnormal, check the ECS security group and Lindorm whitelist settings. For common causes and fixes, see Lindorm connection issues and solutions.