Proxy Analytics
Read your proxy traffic in the dashboard: usage and request trends, the domains you reach, and a searchable log of every request with error reasons.
Analytics answers three kinds of question: how much you are using, whether it is working, and why a request failed.
It covers all three plans, and everything on the page follows the scope and period you set at the top.
You will find it under Proxies → Analytics in the sidebar.
Scope your view first
Type picks the product and Plan picks the access model, then Data Scope narrows it further.
On Per Proxy you can filter by Proxies and by Tags. On Per GB you filter by Access Points. Leave a selector empty to include everything.
Period offers Last Hour, Last 24 hours, Last 7 Days and Last 30 Days, plus a Custom Date Range with Apply.
Refresh at the top right reloads the data without changing your selections.
The two views
The toggle at the top right of the chart block switches between two different reports, not just two units.
Data Usage answers how much. The block is titled Data Consumption Analysis and gives you Usage Trends, with a Total Usage badge, alongside Top 10 Domains (By Volume).
Requests answers how well. The block becomes Network Traffic Insights and gives you Request Volume, which plots Successful against Failed and shows an Avg success rate, alongside Top 10 Domains (By Request Count).
The Month, Week, Day and Hour tabs control how finely the data is grouped, and the sensible one for your period is picked for you.
Avg success rate is your successful requests divided by your total requests across the whole period, so a bad hour in a good month barely moves it. Hovering any point on Request Volume gives that moment's successful count, failed count and success rate, which is how you find the hour something broke.
Connection History
One row per outbound request, newest first, for whatever you have scoped. Requests stay here for 60 days.
Eight columns are shown by default:
TIME
When the request was made
DOMAIN
The destination host
METHOD
The HTTP method, or CONNECT for HTTPS
STATUS
The status Proxidize recorded for the request. See what the status means before drawing conclusions from it
TRAFFIC
Data down and data up, separately
PROXY NUMBER
Which proxy carried it. On Per GB this is ACCESS POINT and shows the access point name
PROTOCOL
HTTP, HTTPS or SOCKS5
LOCATION
Where the proxy exited, as far as it resolves
Columns adds nine more, and they are where the diagnostic value is:
ERROR TYPE
The reason a request failed, in plain words. Turn this on first
DURATION
How long the request or connection lasted
CARRIER / ISP
Which ISP carried it, useful when one network behaves differently
AUTH
Whether the request authenticated by credentials or by IP
SOURCE IP
The public IP that sent the request to us, so you can tell which of your machines or servers it came from
PORT
The destination port, 80 or 443
SESSION KEY
The session the request used, so a row ties back to a specific session
POOL KEY
The pool the request used, on pooled traffic
USERNAME
The username the request presented
Filtering and exporting
Filters builds rules rather than offering fixed choices. Each rule is a column, an operator and a value, and once you have more than one you choose whether they combine with And or Or.
The operators fit the column: text columns offer contains, equals, starts with and ends with, Traffic offers numeric comparisons, and Status, Auth, Protocol and Error Type offer is and is any of.
Export takes the current view as a CSV, so set your scope, period, columns and filters first.
What the status and error columns mean
STATUS and ERROR TYPE are independent. A request can carry a status with no error type, and an error type can appear with more than one status.
STATUS is what Proxidize recorded, not what the website answered.
Ordinary HTTP requests are logged as 200 once we have passed them through, whatever the destination itself returned. If you need to know that a page came back 404 or 429 from the site you were reaching, read that in your own tool. Analytics tells you whether the request got out of our network, not what it found at the other end.
Status codes
200
The request or tunnel succeeded
400
The request was malformed or invalid: an invalid protocol, an invalid Simple Mode port, an unsupported command, or missing proxy configuration
401
Authentication failed, mostly on SOCKS
402
Your bandwidth allowance is exhausted
403
We refused the request on policy: a blocked domain, port or country, an invalid session, an IP not on your allowlist, or a disabled account
404
No usable route was found, or the account or access point could not be found
407
We are asking your client to authenticate. Common on IP-authenticated and browser setups before credentials are supplied, and not a response from the destination
409
A connection conflict, mainly during UDP or SOCKS handling
429
You exceeded your concurrent thread limit
What the error types mean
These are the errors you will meet most often. Others exist, so treat an unfamiliar value as a reason to contact support rather than a sign something is wrong with your setup.
No Bandwidth Available
402
Your data allowance is used up. Buy more data or add a package, and check your balance in the header of your product page
Blocked Domain
403
The destination is not permitted. The request never left our network, so there is nothing to retry. See the policy below
Blocked Port
403
The destination port is not permitted. Only ports 80 and 443 are allowed, so point your tool at a standard web port
Thread Limit Exceeded
429
You are running more than 2,000 concurrent connections. Reduce concurrency, spread the work across more proxies or access points, or complete KYB verification to lift the limit
Authentication Failed
401, 403 or 404
The credentials or source IP were not accepted. Causes include wrong credentials, an access point that no longer exists, the wrong authentication mode, an IP missing from your allowlist, an expired session, and access that has been disabled. Re-copy your credentials from the dashboard and check your allowlist
No Route Found
usually 404
We could not select a usable route. Most often this means nothing was available matching what you asked for, so loosen a pinned location or ISP, though it can also mean a proxy or session that no longer resolves
Why a domain is blocked
Some categories are restricted for accounts verified with KYC only, and KYB verification lifts them: financial services, HR platforms, and user-review sites.
A separate set is blocked for everyone and is never unlocked: anything abusive, anything used for hacking, and anything else Proxidize considers unsafe.
Finding the cause of a problem
Quick FAQ
Related articles
Need help?
If you have any questions, concerns, or need further clarification, feel free to reach out to us via live chat or email us directly at support@proxidize.com.
Last updated
Was this helpful?