# Statistics

Same dashboards, headers, and API as residential — switch the path from `/v1/residential/...` to `/v1/mobile/...`. See [Residential statistics](/products/overview/statistics.md) for the full reference. The mobile-specific dimensions are noted below.

## Dashboard

**Dashboard → Mobile → Statistics** adds these views on top of the standard ones:

* **Top ASNs (carriers)** — most-used carrier IPs
* **Carrier repinning rate** — % of sticky sessions that got a new IP mid-flight
* **Per-carrier error rate** — when a single carrier is degraded

## REST API

```bash
curl -H "Authorization: Bearer API_KEY" \
     "https://api.helodata.com/v1/mobile/traffic?from=2026-05-01&to=2026-05-28&group_by=asn"
```

`group_by` adds `asn` and `carrier_name` on top of the residential options.

## Per-response headers (mobile-only fields)

```
X-Helodata-Exit-IP: 198.51.100.42
X-Helodata-Exit-Geo: us
X-Helodata-Exit-ASN: 6167
X-Helodata-Exit-ASN-Name: Cellco Partnership d/b/a Verizon Wireless
X-Helodata-Exit-Connection: lte           # one of: 3g / lte / 5g / wifi-handoff
X-Helodata-Session-Repinned: true
X-Helodata-Bytes-In: 1248
X-Helodata-Bytes-Out: 38745
X-Helodata-Request-Id: req_01HX2K3PQ4M5
```

`X-Helodata-Exit-Connection` reports the technology layer of the IP at request time — useful when a site treats 5G and LTE differently.

## Tagging requests

Same as residential — `X-Helodata-Tag` header, max 64 chars, `[a-z0-9_-]`. Tags appear in dashboard filters and the `group_by` parameter of the traffic API.

## Billing reconciliation

Mobile traffic is invoiced separately from residential. Pull the mobile traffic API at day granularity for the billing period and compare against **Billing → Invoices**.

## Alerts

Mobile-specific alerts available under **Dashboard → Alerts**:

* Mobile traffic exceeds X GB / day
* Per-ASN error rate exceeds Y%
* Carrier repinning rate exceeds Z% over Z minutes (signals a regional outage)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helodata.com/products/overview-1/statistics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.