---
title: HTTP Ping
description: Measure response latency of a web endpoint over the cellular connection.
lastUpdated: "2026-09-23"
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

Repeatedly request a URL and measure response latency. Closest to what an end user experiences when reaching your service over the mobile network.

## Parameters

| Parameter | Required | Description |
| ----------- | ---------- | ------------- |
| Host | Yes | URL to ping, for example `http://kapptivate.com`. |
| Ping count | No | Number of requests. Default: 10. |
| Ignore SSL certificate | No | Skip certificate verification. Default: off. |
| HTTP Ping should fail | No | Invert the verdict. |

Plus the shared [connection settings](/tests/actions/cellular/overview#connection-settings) and DNS override (`command.override_dns`, `command.dns`).

## Results and metrics

In the action report (`result`):

| Field | Description |
|-------|-------------|
| `rtt_mean` | Mean response time. |
| `packet_loss_pct` | Percentage of failed requests. |
| `ping_count` | Number of requests. |
| `dns_server` | DNS servers used. |
| `duration` | Total execution time in seconds. |

In Analytics, each run feeds the HTTP ping measurement with `rtt_seconds`, `packet_loss_percent`, and `duration_seconds`, tagged by status, APN, DNS server, antenna, and access technology.

## What's next?

<Columns cols={2}>
  <Card title="API Call" icon="cloud" href="/tests/actions/cellular/api-call">

    Verify the response too: status code, body, headers

</Card>
  <Card title="Download File" icon="cloud-arrow-down" href="/tests/actions/cellular/download-file">

    Measure throughput instead of latency

</Card>
</Columns>