To find which server is carrying traffic, start with the server view; to check activity for an app, start with the app view. This guide uses an iPhone or iPad that’s connected and can open the Data screen. Compare the same row before and after an action to identify traffic direction, check whether the counters reset, and compare your device’s readings with an existing provider dashboard.
The Two Data Views: Don’t Add the Same Traffic Twice
The server and app views show different breakdowns. A download through a proxy may appear in both a server row and an app row if it can be attributed to each. The server view shows where traffic went; the app view shows which app it’s attributed to. Adding the two rows double-counts traffic, and different totals don’t necessarily mean anything is missing.
From the device’s perspective, uploads are bytes sent and downloads are bytes received. Downloading a file also sends requests and connection data, so the upload counter may rise too. Uploading a file generates download traffic as the response comes in. Compare the change in both columns to see which direction dominates; a nonzero reading in just one column isn’t required for a transfer to have occurred.
What to Check in the Server and App Views
Before testing, check the current server and Global Routing on Home. With Config, the selected server won’t necessarily carry every connection: a request may match DIRECT or use another outbound specified by the configuration. So a test page loading successfully doesn’t guarantee that the selected server’s row will increase.
Record the Server
- Start
- Note the time, upload, and download readings in the target server’s row.
- Check
- On Home, confirm the connection status and Global Routing. With
Config, open Config and check the active configuration’s[Rule]. - Finish
- After one transfer, return to Data and check the same row. If it hasn’t changed, check the other server rows.
This row tracks traffic for the listed server; it doesn’t show total usage across all devices on the account.
Record the App
- Start
- In the app view, find the app you want to test and note both readings in the same row.
- Check
- Perform one action in that app only, and pause downloads and syncing in other apps if possible.
- Finish
- Return to Data and compare the same row. If the app isn’t listed, don’t treat its absence as zero usage.
This view shows traffic that Data can attribute and display; it isn’t a substitute for system-wide usage statistics.
How to Measure the Data Used by One Download
- Choose an easy-to-identify action. Use the same app to download a small file that isn’t already cached there. Reopening a page you’ve already viewed may load it from cache, so a completed page doesn’t necessarily mean much network traffic occurred.
- Record both sets of starting readings. Note the upload, download, and units for the target app and target server rows. During the test, don’t switch servers, networks, or Global Routing, and don’t clear the statistics.
- Subtract each column separately when you’re done. For example, if the download reading in the same row goes from 24.6 MB to 29.1 MB and upload goes from 1.2 MB to 1.4 MB, the displayed change is about 4.5 MB downloaded and 0.2 MB uploaded. These are example readings, not a fixed ratio for file size or protocol overhead. Display precision is limited, so differences may include rounding.
- Check units and refresh timing first. If the unit changes from MB to GB, convert to the same unit before subtracting. After the transfer, allow time for the display to refresh, then check the same row again. If only the last digit changes, try a larger test file so rounding in the interface isn’t mistaken for stalled traffic.
App Usage Increased but the Target Server Didn’t: Check Routing
First check whether another server row increased during the same period. If Global Routing is set to Config, use the test file’s actual download domain to check [Rule]—don’t rely only on the domain of the webpage you were on before opening the file. They may differ and match different policies.
When Do Counters Reset, and How Do You Set a New Baseline?
Device counters and a provider’s billing cycle are managed separately. A new provider billing cycle doesn’t mean Data resets at the same time, and resetting local statistics won’t reverse usage already recorded by the provider. If you need to clear statistics, save the current readings first, then follow the clear action and confirmation shown on the Data screen. Check whether it applies to the current item or a broader scope. If there’s no clear option, record the current values as your test baseline.
- Clearing may not show a full zero. Counters can increase immediately if a transfer is still running. To confirm what was cleared, stop active downloads or syncing first, then check the same view and row and record the new starting reading.
- Disconnecting and reconnecting, closing the app, or a new day doesn’t mean the counters reset. Compare the same view, row, and unit before and after. If an entry disappears, changes name, or shows a lower reading, don’t keep using the old baseline. Confirm it’s still the same entry, then record a new baseline.
- Don’t subtract an old reading from a new one across a reset. If the last reading before a reset was 80 MB and the next reading is 3 MB, the difference isn’t negative traffic. You can combine known increments only if you recorded separate readings before and after the reset.
Provider Dashboard Doesn’t Match? Align the Time, Scope, and Measurement
Choose a specific time window for comparison, such as 2:00–2:10 p.m. on the same day, and note the time zone. Compare the increase in Data over that window with the increase for the same window in the provider dashboard. If the provider shows only a billing-cycle total or updates in batches, two pages from different times can’t confirm the usage from a single transfer.
Why Does the Dashboard Show Much More Than This Phone’s Server Row?
First check whether the dashboard shows one server or the whole account. If the account is also connected on other devices or multiple servers were used during the test, the dashboard may combine their traffic. Pause transfers on other devices, then measure a new difference using the same device and server.
The Download Finished. Why Hasn’t the Dashboard Changed Yet?
First check Data for a download increase on the target server, then check the dashboard’s last update time. If the dashboard posts usage after the transfer, wait for its next update before comparing. If the target server’s row in Data hasn’t changed either, check whether the request went through another server or DIRECT; don’t assume it’s just a reporting delay.
The Time and Server Match. Why Is There Still a Small Difference?
First check whether the dashboard counts downloads only or combines uploads and downloads, then confirm the units, such as MB versus MiB. If the counters are measured at different points, they may account differently for connection overhead, retransmitted data, and other bytes. Use the provider’s published measurement method rather than applying a fixed conversion ratio.
Why Are the Readings Increasing When I’m Not Browsing?
Pause system syncing, media preloading, and file transfers, then record readings over a short interval. If a connection appears after disconnecting, check whether Settings → On Demand is configured to connect on demand under the current network conditions. Check connection status and traffic volume separately; rising counters alone don’t identify which background activity caused them.