Understand usage measurement

The console reports traffic by API key and shows a workspace usage chart. Use these measurements to understand traffic direction and trends; the bytes can differ from the payload sizes your application records.

What the counters mean

Counter	Meaning
Uploaded	Bytes sent toward the destination through the upstream connection.
Downloaded	Bytes received from the destination through the upstream connection.
Total	Uploaded bytes plus downloaded bytes.

The counters include bytes carried by the upstream connection, such as forwarded HTTP headers. For HTTPS destinations reached through HTTP CONNECT or SOCKS5, the encrypted TLS traffic is carried on that connection. HTTP proxy setup messages and SOCKS5 negotiation, authentication, and CONNECT messages between your client and the proxy are excluded.

HTTP and SOCKS5 use the same per-key usage measurements. Application bytes sent alongside a SOCKS5 handshake are counted when they pass through the established upstream tunnel; sending them early does not exclude them from usage.

uploaded bytes + downloaded bytes = total bytes

The totals count bytes, not requests. One tunnel can carry more than one HTTPS request.

Read the console

Open Usage in the console. Its Usage by API key table shows recorded totals for each key and retains entries for revoked keys. Revoking a key does not remove its prior usage history. The per-key table is shown to workspace owners and admins; every member sees the workspace chart.

The workspace chart supports these ranges:

Range	Chart grouping
24 hours	Hourly buckets
7 days	Daily buckets
30 days	Daily buckets

The chart range selects its time-series window, and its buckets are aligned to UTC. The per-key totals are recorded cumulative totals; they do not change to the chart’s selected date range.

The console formats byte values using binary units: 1 KiB = 1,024 bytes, 1 MiB = 1,048,576 bytes, and 1 GiB = 1,073,741,824 bytes.

Allow for reporting delay

Usage arrives asynchronously. Select Refresh to retrieve currently available totals. During an outage, usage may appear later; an unchanged counter immediately after a request is not proof that no traffic passed through the proxy.

Compare the same key and time window when investigating a discrepancy. Include the key’s non-secret ID or name, approximate request times, and the client behavior. Keep the secret password out of diagnostics.

Separate usage from pricing

This page defines the current traffic measurements. It does not specify prices, free allowances, charging increments, invoice timing, or a billing accuracy guarantee. Refer to the commercial terms provided for your account when interpreting a charge.