Only one country fails
Check Is it that checker's network, a CDN or firewall rule for that country, or the route?
Fix Re-test the country from a second IP, then check geo and firewall rules for it before calling it an outage.
Know whether your site is down — or only down in one country.
A check from one place can't tell 'down' from 'down for me'. Google Cloud's uptime checks require at least three checkers and, by default, notify only when at least two regions report a failure — so one failing location alone doesn't raise an alert.
Sites also fail by country while the origin is fine. CDN and firewall rules can block or challenge a country, a network or an IP range — Cloudflare offers all three — and networks fail by country too: Cloudflare reported that since June 9, 2025, ISPs in Russia have throttled connections to sites behind it to roughly the first 16 KB, leaving pages broken for visitors there.
Static datacenter IPs make dependable checkers: fixed for the whole term, fast and priced per IP. Put one in each country you serve and run your own multi-location checks, or route monitors in a tool such as Uptime Kuma, which lists proxy support, through them.
Scroll horizontally with the arrow keys to read all content.
| Criterion | Choose | Why |
|---|---|---|
| Product | Static datacenter proxy | Fixed, fast and priced per IP — a checker that doesn't move |
| How many IPs | At least three, in different countries | Lets you require two failing locations before you alert |
| Countries | Where your users are: US, CA, GB, DE, NL, JP, KR or SG | Static datacenter IPs are listed in these 8 countries; stock varies |
| Other countries or a home-user view | Rotating residential, Choose region / sticky IP | Household IPs in the country you pick, billed per GB |
| Protocol | HTTP | Works in httpx, requests, curl and most monitors |
| Alert rule | Two or more locations failing, twice in a row | One failing checker is often a problem on its own network |
The button below opens Static Datacenter Proxies with the AI and automation use case. Buy one IP per country: choose the Region, Term and Protocol before you pay, keep Quantity at 1 and repeat for each country.
Scroll horizontally with the arrow keys to read all content.
| Criterion | Static ISP | Rotating residential | Datacenter |
|---|---|---|---|
| What you get | A dedicated home-broadband IP that stays yours for the whole term | Real household IPs: rotating exits, or a sticky session in a chosen country or city | Fast fixed server IPs, HTTP and SOCKS5 |
| Price | Per IP and term — live price at checkout | Budget US$1.50/GB (US$1.35/GB at 100 GB); Premium US$5.00/GB | Per IP and term — the cheapest per IP |
| Best for uptime monitoring | Checks that must come from one home-broadband IP for weeks | What visitors on consumer ISPs see, in almost any country | Fixed multi-country checkers for sites and APIs |
Prices in US dollars. Top up your wallet once and pay any line from it. Nothing renews automatically — renew in My assets to keep an IP.
The button below opens Static Datacenter Proxies (Per IP and term) with the AI and automation use case. Pick one Region, choose a Term, set Protocol to HTTP and keep Quantity at 1, then click Review cost and generate. Repeat for each country.
In My assets, Copy gives host:port:user:password. Store each as a proxy URL — PROXY_US, PROXY_DE, PROXY_SG — in the form http://USER:PASS@HOST:PORT.
Use the code below from a scheduler: it requests your health URL through every proxy and prints status and response time.
Expected result One line per country with 200 and a time; an ALERT line only when two or more countries fail.
In a monitor that accepts an HTTP proxy with username and password, add one proxy per country and attach each to the checks for that market.
Scroll horizontally with the arrow keys to read all content.
# pip install httpx
import os
import httpx
URL = "https://www.example.com/health"
# One static datacenter IP per country (Region), each copied from My assets
CHECKERS = {"US": os.environ["PROXY_US"], "DE": os.environ["PROXY_DE"], "SG": os.environ["PROXY_SG"]}
failed = []
for country, proxy in CHECKERS.items():
try:
r = httpx.get(URL, proxy=proxy, timeout=10)
ok = r.status_code == 200
print(country, r.status_code, f"{r.elapsed.total_seconds():.2f}s")
except httpx.HTTPError as exc:
ok = False
print(country, "error:", type(exc).__name__)
if not ok:
failed.append(country)
if len(failed) >= 2: # one failing checker is often its own network; two or more is an outage
print("ALERT: down from", ", ".join(failed))Checked on 2026-10-18 (httpx 0.28.1) against a local health endpoint: three 200 responses and no alert; when the endpoint returned 503 from all three, the script raised the alert.
Check Is it that checker's network, a CDN or firewall rule for that country, or the route?
Fix Re-test the country from a second IP, then check geo and firewall rules for it before calling it an outage.
Check Are the IPs active and unexpired in My assets? Do the credentials match?
Fix Renew or replace the IPs and copy the lines again.
Check How far is the checker from your origin?
Fix Compare with a direct check from the same region and set response-time limits per location.
Check Do you alert on a single failure?
Fix Require two locations and two consecutive failures before paging anyone.
Because one location can't tell a real outage from a local network, routing or firewall problem. Several countries agreeing is a much stronger signal.
At least three, alerting when two fail — the default Google Cloud uses for its uptime checks.
Static datacenter IPs are listed for the US, Canada, the UK, Germany, the Netherlands, Japan, South Korea and Singapore, and stock varies by country. For other countries, use rotating residential with Choose region / sticky IP.
Datacenter for steady, cheap checkers with a fixed IP. Residential when you want the view of a visitor on a consumer ISP.
Uptime Kuma lists proxy support among its features, so you can route a monitor through one of these IPs; any monitor that accepts an HTTP proxy with a username and password works the same way.
Official documentation · Checked:
Official documentation · Checked:
Third-party source · Checked:
Official documentation · Checked:
Official documentation · Checked:
Product observation · Checked:
Rotating residential per-GB prices as published on the pricing page and used by the console (Budget US$1.50/GB, US$1.35/GB in the 100 GB package; Premium US$5.00/GB; 1 PTC = US$1). Static ISP and datacenter IPs are quoted live per IP and term.
Product observation · Checked:
Option names, billing modes and limits as shown in the live console on 2026-10-18: Line (Premium/Budget), Exit mode, Region, State, City, Protocol (HTTP/SOCKS5), Quantity (1–500), Term, Auto-renew IP (not yet available), My assets → Copy / Rotate / Renew / Copy for AI. Rotating residential connects through proxy.proxy302.com:2222 (HTTP) and :3333 (SOCKS5). Static datacenter IPs were sold in 8 countries on 2026-10-18 (read-only check of the production catalogue): US, CA, GB, DE, NL, JP, KR, SG.
Local example · Checked:
The code block was executed on 2026-10-18 against a local password-protected HTTP proxy that answers 407 without valid credentials; httpx 0.28.1 against a local health endpoint through three proxy URLs: three 200 responses and no alert; when the endpoint returned 503, all three failed and the script raised the alert.
A local check proves the configuration syntax and authentication path, not access to any specific website, country or platform.
Create an account, top up once and pick rotating residential, static ISP or datacenter. Rotating residential exits cover 195+ countries and regions.