Skip to main content
The Usage Analytics dashboard gives you a detailed breakdown of how your proxies are being used. You can find it by clicking the bar chart icon in the left sidebar, or going to Usage breakdown.

Filtering by date range

Use the date picker at the top of the page to change the time window. The summary cards and chart both update to reflect whichever range you select. This is useful for comparing a specific week or day against your baseline.

The summary cards

At the top of the page, three cards give you a snapshot of activity for the selected time range.

Total credits

The total number of credits consumed in the selected period. Credits are deducted based on the volume of traffic you route through SOAX and the country tier you target. If this number is higher than expected, the usage log below will help you narrow down which package or country is driving it.

Total traffic

The total data transferred through your proxies, shown in GB. This is the raw volume your credits are spent on. A spike here is worth investigating in the chart.

Credits/GB avg

Your average credits spent per GB in the selected period. This reflects the blend of country tiers you’ve been targeting. A higher number means more traffic through Tier 1 countries (US, UK, Western Europe), which cost more per GB. A lower number means more Tier 2 or Tier 3 traffic. If it’s trending up, check the Country and Tier filters in the usage insights to see what’s shifted.

Usage insights

The chart section lets you slice your traffic data to understand exactly where consumption is coming from.

Filters

You can filter the chart and table by:
  • Proxy package — isolate traffic from a specific package if you’re running multiple
  • Proxy network — filter by network type (e.g. residential)
  • Tier — see how much of your traffic is going through Tier 1, 2, or 3 countries
  • Country — drill down to a specific country
  • Interval — switch between daily, weekly, or hourly granularity
Filters stack, so you can combine them — for example, residential traffic in Tier 1 countries over the last 7 days.

Reading the chart

The Usage over time chart shows traffic volume in GB or consumed credits (toggle with the Gb / Credits buttons in the top right) broken down by your chosen grouping. By default it groups by package, with each package shown as a separate colour in the stacked columns. Switch between Columns and Lines views depending on what you’re trying to see:
  • Columns make it easy to compare total volume across days
  • Lines make it easier to see trends and rate of change over time
Use Group by to pivot the view — grouping by Country or Tier is useful when you want to understand your geographic cost distribution.
A sudden spike on a single day usually means a job ran with misconfigured session settings, or a retry loop sent far more requests than intended. Cross-reference the date in the usage log to find the package and egress IP involved.

Usage log

Below the chart, the usage log gives you a row-by-row record of traffic activity. Each row represents an aggregated record for a specific combination of package, network, tier, country, egress IP, and domain as well as month / date / hour. The columns are:

Exporting data

Click Export CSV in the top right of the usage log to download the full log for the current filter and date range. This is useful for reconciling usage against your own application logs, or sharing consumption data with your team. Use All columns selected to choose which columns to include in the export before downloading.

How to spot issues

A few patterns worth knowing: Unexpectedly high traffic on a single day — check the usage log filtered to that date. Look for a high-traffic egress IP or a domain you don’t recognise. This often points to a misconfigured retry loop or a job that ran longer than expected. Credits/GB avg is higher than your plan rate — this means you’re routing traffic through more expensive country tiers than you intended. Filter the chart by Tier to confirm, then check whether your proxy configuration is targeting the right countries. Traffic spread across many egress IPs to the same domain — this is normal for rotating proxy sessions. If you’re seeing it on a session-based package, it may indicate your session duration is too short and connections are cycling more often than expected. No traffic showing for a package — if a package shows zero usage when you expect some, check that the package is active in Package Management and that your credentials are correct. Authentication failures don’t generate usage records.