Usage Analytics
Available for both Freemium and Premium users.
Ankr gives you two levels of visibility into your traffic: a high-level Statistics overview, and a per-request Requests view for raw, self-serve debugging.
Statistics overview
To open the Statistics pane, sign in to the Web3 API platform and click Statistics in Navigation.
Here you can monitor:
- Total Requests — the total number of requests.
- Top chain — your most-queried chain.
- Requests health — overall success-to-failure rate based on our node performance.
- Requests — a diagram of requests over time.
- Requests overview — requests broken down by one of: projects, chains, IPs, countries, or methods.
- Requests health breakdown — a detailed success/failure distribution.
- Usage History — chain requests by month.
Requests (raw request telemetry)
The Requests tab shows every individual request your account made over the last 7 days, in raw form — so you can answer "what exactly happened to this call?" yourself, without opening a support ticket.
Open it from Statistics > Requests.
The Requests tab is available to paid accounts and populates once your account has request history. A brand-new account with no traffic will see an empty table.
Screenshot: the Requests tab — one row per request, with filters.
Columns
Each row is a single request. Columns include:
| Column | What it shows |
|---|---|
| Time | When the request was received (UTC). |
| Trace ID | Unique identifier for the request — use it to look up one specific call. |
| Status | Outcome of the request (HTTP status combined with the first error, if any). |
| Chain | The blockchain queried. |
| Method | The RPC method(s) called. |
| Protocol | HTTP or WebSocket. |
| Latency | End-to-end response time in milliseconds. |
| Req / Resp | Request and response sizes in bytes. |
| Calls | Number of calls in the request (more than one for batch requests). |
| Country / City | Approximate, general location the request came from. |
| IP | The client network, anonymized (see Privacy). |
| Origin / Referer / User-Agent | Client metadata, where available. |
Filters
Narrow the table to exactly what you're investigating:
- Time range — within the last 7 days.
- Project / API key — one or more of your keys.
- Chain — one or more blockchains.
- Protocol — HTTP or WebSocket.
- Method — specific RPC methods.
- Country — origin country.
- Minimum latency — show only requests slower than a threshold.
- Error code — filter by a specific error code.
- Errors only — show only failed requests.
- Batch — only batch, only non-batch, or any.
- Trace ID — jump straight to one request.
- Error message — search by error text (partial match).
Common workflows
- Why did my request fail? Turn on Errors only, filter by Chain, and read the Status / Error code columns.
- Trace one specific call. Paste its Trace ID into the filter.
- Find slow calls. Set a Minimum latency (e.g. 1000 ms) and sort by Latency.
- See where traffic comes from. Filter or group by Country.
Privacy
The Requests view is designed to be safe to expose: client IP addresses are anonymized to the network only (/24 for IPv4, /48 for IPv6), only general location (country/city) is shown, and internal infrastructure details (node names, endpoints, exact coordinates) are never returned.
Access it via the API
The same data is available programmatically, so you can pull request telemetry into your own tooling. Use the Telemetry endpoint exposed in the Platform Swagger — POST /api/v1/telemetry/requests — which accepts the same filters (chains, methods, protocols, countries, error codes, errors-only, minimum latency, batch, trace ID, time range) and returns results with cursor-based pagination.
Congrats — you can now inspect, filter, and export every request your account makes.