European providers block gambling domains one at a time. Orange Polska starts filtering
while Netia still resolves — your uptime monitor stays green and your tracker calls it a
soft week. ASNWatch names the provider, within minutes.
Reachability of offer123.com by provider and country
provider
PL
DE
IT
ES
Baseline established across 20 pairs.
Pulls campaigns and budgets from
Keitaro
Binom
Voluum
Telegram
Webhooks
Mechanism
Cheap checks find it. Expensive checks prove it.
A residential check through a real consumer ISP is what proves a block — and it is the
expensive part. So it never runs on healthy pairs.
01
Sweep every pair, slowly
Each domain × country × provider pair is checked every one to two hours through the
cheap pool. The classifier separates a live landing page from a regulator stub, a
captcha, a redirect and a genuine outage — not just 200 or not-200.
costs ~nothing02
One pair looks wrong — only that pair escalates
The suspect pair moves to every 5–10 minutes and re-tests through a residential exit
inside that exact ASN. Nothing else in your account changes speed.
the expensive part03
Confirmed twice, then you hear about it
Two consecutive residential confirmations open the incident and send one alert —
domain, country, provider, event type, plus the campaign and daily budget bound to it.
Three clean checks close it.
≈15 min
A domain that fails from every provider at once is an origin outage, not a block. It is
grouped into one domain-level incident instead of forty per-ASN alerts.
Category
Four tools claim this job. None answers the question.
Question you actually have
Uptime monitor
Free ping tool
Affiliate tracker
ASNWatch
Which ISP is blocking?
No
No
No
Named provider and ASN
Block or captcha?
Both read “down”
Both read “down”
No
Five distinct verdicts
How much budget is exposed?
No
No
After the fact
Campaign and daily budget in the alert
How long will this domain last?
No
No
No
Expected lifetime per country
When do I find out?
Minutes, if fully down
When you remember
Days, via conversions
≈15 minutes, confirmed
Analytics
Plan the rotation before the ban, not after it.
Every check is kept. Over weeks that becomes the one number no uptime monitor can give you:
how long a domain typically survives in each market.
ITmedian 17 days
PLmedian 20 days
ESmedian 38 days
DEmedian 80 days
Median, not mean — a couple of domains that survived six months would drag an average far
from the typical case. Domains still alive stay in the sample rather than being dropped,
because counting only the ones already banned biases the estimate downward. Below ten
confirmed blocks every figure is labelled provisional.
Coverage
Collected, verified and published — not promised.
ASNWatch harvests public node lists, resolves every node's real exit ASN against its own
IP-to-ASN map, and probes each one against a canary page it controls. A node that alters the
canary is quarantined permanently — that node is exactly the one that would report a block
that never happened.
25European markets
81consumer providers
455,792IP ranges in ASN map
0API keys required
Straight talk about the free tier: public nodes skew heavily toward datacenter networks.
Where the pool has no node inside the provider you care about, the matrix says
no coverage rather than showing a green cell that means nothing. Paid plans reach any
consumer ASN on demand.
Pricing
Start on three domains. Pay when the answer has to be certain.
The free plan detects. Paid plans confirm — every anomaly is re-tested through a
residential exit inside the provider itself, so the alert names it.
Because that is how the blocking happens. A registry entry lands, one provider implements
it this week, another next month, a third never. A country-level check averages that into
a green light while a quarter of your audience already cannot load the page.
How is this different from an uptime monitor?
An uptime monitor answers “up or down, from where I stand”. ASNWatch answers “reachable,
blocked, captcha'd, redirected or down — from inside this provider, in this country”.
Those are different questions, and only one of them tells you which geo to pause.
Won't free proxies produce false alarms?
They would, unmanaged. Every node is verified against a canary page we control before it
joins the pool, and any node that modifies that page is quarantined for good. Free-plan
alerts still carry lower confidence than residential-confirmed ones, and they say so.
What does an alert actually contain?
Domain, country, provider name and ASN, event type, the rules that matched, the final URL
after redirects, and the campaign plus daily budget bound to that domain. Enough to act
without opening the dashboard.
What do I actually get by paying?
Residential confirmation. The free plan runs on a collected public node pool, which skews
toward datacenter networks and often has no node inside the consumer provider you care
about. Paid plans re-test every anomaly through a residential exit inside that exact ASN
before alerting you — so the alert names the provider, and you can act on it.
Which countries are covered?
Twenty-five European markets with 81 consumer providers seeded — Poland, Germany, Italy,
Spain, France, Portugal, Greece, Czechia, Romania, Hungary, Bulgaria, Slovakia, Croatia,
Austria, the Netherlands, Belgium, the Nordics and the Baltics.
Do I need DevOps to set this up?
No. Paste a list of domains, pick your geos, and the matrix fills in. That path is designed
to take under five minutes from an empty account.