The four layers
| Layer | Failure looks like | What it tells you |
|---|---|---|
| Resolution and transport | Nothing loads at all; name errors | Node or DNS problem, not a streaming problem |
| Exit acceptance | Region or proxy error page | The platform refuses this exit or this region |
| Catalogue | Loads, but the expected title is absent | Region differs from what you assumed |
| Playback | Starts, then buffers or errors mid-stream | Throughput, routing or platform-side throttling |
Diagnose in that order. A playback failure on a node that cannot resolve anything is not a streaming question yet.
Step 1: confirm transport, not the page
- With the node active, request a plain HTTPS site and confirm it loads.
- Check the exit IP and compare it against at least two independent data sources — the node label is a claim.
- Confirm the client is actually capturing this browser: system proxy for a browser, or TUN for the whole device. A browser extension with its own proxy setting bypasses the system proxy entirely.
Step 2: read the error for what it is
| What you see | Likely layer | Next step |
|---|---|---|
| Region or availability notice for your area | Exit not accepted for that region | Try a node in the region you need; verify the exit, not the label |
| A message about proxy or unblocker detection | The exit is treated as a proxy, not as a household | Change exit type; do not keep retrying the same address |
| Login or password loop | Account or session, possibly triggered by many region changes | Stop switching; secure the account and contact support |
| Loads, then buffers | Throughput at the current hour | Measure a sustained transfer, not a small file, at your actual viewing time |
| Nothing loads, name errors | Resolution | Go to the DNS path; this is not a streaming fault |
Step 3: test the title you actually want
Catalogue rights are per title, not per platform. A node can pass the region gate and still lack the specific title, because that title is licensed differently. Test the exact thing you intend to watch, with the account you actually use, and note whether the failure is “not available in your region”, “not in this catalogue”, or playback-level.
Step 4: sustained throughput, at your hour
A 1 MB download proves that bytes moved. Streaming needs a sustained bitrate with buffering margin, and both degrade at peak hours on shared routes. Test at the hour you watch, on the device you watch on, and note whether the failure appears immediately or after a few minutes.
What a node cannot fix
- Account region. If the account was created and paid in one region, some behaviour follows the account, not the IP.
- Payment methods. A card issued in one country can create inconsistencies a proxy cannot resolve.
- Simultaneous streams and household limits. These are plan properties.
- Detection. If an exit is classified as hosting rather than residential, changing nodes within the same range usually changes nothing.
Recording a comparison
- Time and hour, since peak matters.
- Node label, protocol and observed exit IP.
- Exact error text or the point in playback where it failed.
- Whether a second title behaved the same way.
- Whether the same node behaves differently on another network.
One test at one moment is a data point. It is not a statement about the node's long-term suitability.
Scope
This page describes a verification order. It contains no tests of specific streaming services, names no provider, and makes no claim about which node type passes any platform's checks. Platform behaviour changes without notice; your own test at your own hour is the only measurement that applies to you.