I built a live VPN streaming monitor using WireGuard pools

I built a live VPN streaming monitor using WireGuard pools (real HTTP checks, not marketing claims)
Most VPN review sites say things like:
“Works with Netflix”
“Unblocks Hulu”
“Supports BBC iPlayer”

But almost none of them show real-time data.

As someone working deeply with VPN infrastructure, I wanted to answer a simple question:
Does a streaming service actually load right now through a real VPN tunnel?
Not based on marketing. Not based on assumptions. Based on real HTTP responses.
So I built a live monitoring system.
The core idea Instead of testing once and writing an article, the system continuously checks streaming services using real VPN tunnels.
It connects through multiple WireGuard configurations and tests services like:
-Netflix
-Hulu
-Disney+
-BBC iPlayer
Each test is performed from real VPN exit nodes.
The system records:
-exit IP
-HTTP response code
-reachability status
-timestamp
-region

This allows building a live status view instead of static claims.
Architecture overview
The system runs on a Linux VPS and uses WireGuard pools.
Each region has multiple configs:
/etc/wireguard/proton/pool/us/
/etc/wireguard/proton/pool/uk/
/etc/wireguard/proton/pool/fr/
/etc/wireguard/proton/pool/es/
/etc/wireguard/proton/pool/ca/
A monitor script:
-connects to each config
-tests streaming endpoints
-records HTTP responses
-selects best working exit IP
-stores results as JSON
Example data structure:
/var/lib/saomonitor/regions/us.last.json
/var/lib/saomonitor/regions/uk.last.json

Then everything is aggregated into a public live JSON feed.
Why HTTP tests instead of DNS or ping?
Because streaming services don’t block DNS.

They block HTTP access.
The only real test is:

Can the streaming website actually load over VPN?
So the monitor uses real HTTP requests.
Example:
curl --interface wg-proton-us https://www.netflix.com/
This confirms whether the service loads through that exit IP.
Live public JSON feed
The monitor generates a live JSON feed that powers the status page.
It includes:
-multiple countries
-exit IPs
-HTTP response status
-last check timestamps
Live data example is publicly visible here:

https://smartadvisoronline.com/status/

This page shows real-time reachability based on automated checks.
Not assumptions.
Actual responses.
Why multiple regions matter
Streaming availability depends heavily on exit IP reputation.

Some IPs work.
Some get blocked.
Some work temporarily.

Testing multiple regions allows understanding patterns like:
-which regions work best
-how often exit IPs change
-how stable connectivity is

This is much more useful than static VPN reviews.
Automation and reliabilityThe system runs automatically using cron.
It continuously:
-probes regions
-updates JSON
-publishes live data
-rotates configs when needed
It also tracks exit IP changes and service availability over time.
What I learned building this
A few key observations:
-exit IP stability matters more than provider brand
-streaming services frequently rotate blocks
-different regions behave very differently
-real monitoring gives much clearer insights than one-time tests
Why I made this public
Transparency matters.
Instead of telling users what should work”, it’s better to show what works right now.This helps users understand real behavior, not marketing claims.
If you’re working with VPN infrastructure, automation, or network monitoring, I’d be curious how you approach streaming reachability testing. There’s a lot happening behind the scenes most users never see.