Multi-region monitoring in Tracker.ru actively checks the availability of one URL from three regions in parallel: Moscow (Russia), Frankfurt (Germany, EU) and Almaty (Kazakhstan). Each region is an independent worker — separate server, separate ISP, separate route to your site. The aggregated status helps tell a local network flap of one provider apart from a real outage. If you need geo-distributed uptime monitoring focused on the Eurasian perimeter (Russia, EU, Kazakhstan), Tracker.ru's multi-region covers that case. For checks from the US, China or Australia, see the honest disclaimer below: those markets are better served by global services like UptimeRobot.
Why monitor a site from multiple countries?
The modern internet is not a single network — it's a patchwork of autonomous systems, regional ISPs and CDN edges. A site that's reachable from Moscow can be unreachable from Frankfurt because of CDN-side blocking, upstream routing problems or regulatory restrictions. Single-region monitoring misses such cases entirely: the service reports «all good», while real users in another country see 503s or timeouts.
Geo-distributed monitoring across three countries solves four practical problems. First, false-positive filtering: if one region reports an error and the other two report 200 OK, the issue is most likely local and doesn't warrant a 3 AM page. Second, CDN sanity: different edge points (CloudFlare, Bunny CDN, Yandex Cloud) can return different responses, and multi-region surfaces the divergence immediately. Third, cross-border path monitoring: if your site is hosted in Moscow but the audience is in Kazakhstan, you want to know that the msk → kz path stays healthy, not just that the server itself is up. Fourth, real-UX correspondence: when a customer in Frankfurt loads your site, you're verifying the exact path they take. If response time from Frankfurt jumped from 200 ms to 2 seconds, your European users are waiting right now — even if the local Moscow monitor is happy.
Multi-region also helps post-incident analysis: at a glance you can tell whether the outage was regional or global and trace how the wave of degradation propagated — first msk, then eu, then kz, or simultaneously everywhere. Without multi-region you collect this manually with ping from a few servers, or trust your hosting provider's word.
What regions are available and where are they physically located?
Tracker.ru runs three active regions as of 2026 — each in independent datacenter infrastructure with independent upstream providers.
Moscow (msk, Russia). The central region, hosted in a Moscow DC. Baseline check point for sites with a Russian audience: traffic goes through local ISPs, exactly as a Russian visitor would experience it. Available on every plan, including Free.
Frankfurt (eu, Germany, European Union). The European region in one of Europe's largest internet exchanges (DE-CIX area). Used to monitor sites with European audiences, validate CDN configurations and verify reachability from the EU. If your task is monitoring a site from Europe under realistic routing — the eu region answers that.
Almaty (kz, Kazakhstan). The Central-Asian region, hosted in a Kazakhstan DC. Covers monitoring from Kazakhstan — relevant for businesses operating in the KZ market or serving customers in Central Asia. Almaty is independent and is not routed through msk, so changes in the cross-border ru ↔ kz path show up as their own signal.
All three regions publish a heartbeat every few seconds, and if a region loses connectivity it's automatically flagged as inactive — visible in the cabinet and not triggering false-positive alerts on the «whole» monitoring system.
How does status aggregation across regions work?
Each monitor has two status models in the database: per-region status (url_region_status) and the aggregated status (urls.http_status). The aggregation logic is straightforward but matters for reliability.
Each region runs its HTTP check independently: HEAD (or GET, depending on configuration), measures response time, validates the SSL chain, classifies the error. The result is published to the central NATS bus, picked up by the statusWorker and written to url_region_status — one row per region.
A detection threshold then applies: status down is set only when all active regions for a URL have crossed the confirmed-error threshold. If msk reports an error while eu and kz return 200 OK, the aggregated status stays up — that's a local network blip, not an alert-worthy event. If all three regions simultaneously report errors or timeouts, the status flips to down and notifications fire on the configured channels (Telegram, Email, MAX, webhook).
The threshold is service-side — by default 1–2 confirmed fails in a row, to avoid single hiccups. Per-region history is stored in check_log.region_id and is available in the cabinet for post-incident review: you can replay how degradation spread across the points over time.
If a region physically goes offline (a remote VPS stops sending heartbeat), it's excluded from aggregation until connectivity is restored — preventing the status from getting stuck in an undefined state and avoiding noisy alerts about the monitoring infrastructure itself.
What if your audience is in the US, China or Australia?
Tracker.ru focuses on the Eurasian perimeter — Russia, EU, Kazakhstan. This is a deliberate choice: three regions that work reliably under a clear legal regime, with Russian-language support and ruble billing. We have no check points in the US, China or Australia, and adding them is not on the near-term roadmap.
If your target audience is in the US, China or Australia, those markets are better served by global services. UptimeRobot offers four global regions (North America, Europe, Asia, Australia) and covers the «monitoring by continent» case directly. Better Stack (formerly Better Uptime) is an observability stack with four global check regions (us/eu/as/au) without points in Russia or the CIS. StatusCake and Pingdom are other international alternatives with similar global coverage.
Running two services in parallel is a normal practice: Tracker.ru for the primary multi-region uptime within the Eurasian contour (with local support and a Russian legal entity), plus an international service for an extra check from American or Asian points. That gives you complete coverage without paying the international service's premium tier for the entire monitor fleet.
We don't try to be a universal global service — for that, UptimeRobot or similar serve better. Tracker.ru does one segment well: the Eurasian perimeter, transparent ruble pricing, Russian-language support, screenshot monitoring with pixel diff and a native Telegram bot. If that segment is your priority, multi-region from Moscow, Frankfurt and Almaty fits.
How are regions allocated per plan?
Multi-region is a paid feature, but Free includes one region for evaluation.
- Free (0 ₽). 1 region of choice (Moscow by default). 5 monitors, 5-minute interval. Fits pet projects and product evaluation.
- Basic (290 ₽/mo). 2 regions of 3 (for example, msk + eu, or msk + kz). 20 monitors, intervals from 60 seconds. Enough for most commercial sites.
- Pro (790 ₽/mo). All three regions simultaneously — msk + eu + kz. 100 monitors, intervals from 30 seconds, public API and extended status pages. Full multi-region out of the box.
Multi-region is part of the subscription, not a separate line item: Free gives one region, Basic two of choice, Pro all three (msk + eu + kz). Number of URLs and chosen regions stay within a fixed monthly fee — no per-check billing, no hidden fees. More on limits and pricing — /pricing.
Enable multi-region monitoring
Frequently asked questions
Can a site be checked from all three regions simultaneously?
Yes — on Pro all three regions (Moscow, Frankfurt, Almaty) are active simultaneously. On Basic — two of three of choice; on Free — one. Each region is an independent worker, hits the site in parallel, results are written to url_region_status and aggregated into the overall status. This is exactly what's known internationally as a multi-region monitoring service or multi-location uptime monitoring: checking one URL from several geographically separated points in parallel.
What happens if one of the regions goes offline?
If a region stops sending its heartbeat (for example, the remote VPS goes down), it's automatically marked inactive and excluded from aggregation until connectivity is restored. A site-down alert does not fire while at least one active region returns 200 OK — the status stays up. This avoids false-positive alerts caused by problems in the monitoring infrastructure itself.
Can Tracker.ru check a site from the US or China?
No. Tracker.ru focuses on the Eurasian perimeter — Russia, EU, Kazakhstan. There are no check points in the US, China or Australia, and adding them is not on the roadmap. For checks from American or Asian servers, use international services: for example, UptimeRobot with four global regions (North America, Europe, Asia, Australia). Running two services in parallel is a normal practice when you need both Eurasian and global coverage.
See also
- /features/heartbeat-monitoring — heartbeat monitoring for cron jobs
- /features/screenshot-monitoring — visual regression and pixel diff
- /compare/uptimerobot — comparison with UptimeRobot (4 global regions)
- /compare/better-stack — comparison with Better Stack
- /pricing — full plan and pricing comparison