# Tracker.ru — Website Uptime Monitoring > Russian SaaS for uptime monitoring: HTTP/HTTPS checks from 30 seconds to 1 hour from 3 regions (Moscow, Frankfurt, Almaty), Telegram/MAX/Email/Webhook alerts (HMAC-SHA256), heartbeat monitoring for cron jobs, SSL certificate expiration monitoring, public status pages. Additionally: visual-change monitoring via screenshots (Chrome headless) and response-time health monitoring (Apdex). Locales: ru, en, kk. ## What it is and who it's for Tracker.ru is a website and API uptime monitoring service for developers, DevOps engineers, and site owners working in Russia and the CIS. The platform tracks uptime, response time, content validity, and SSL certificate health, double-checks incidents before alerting (false-positive protection), keeps full check history, and supports public status pages for customer communication. Canonical URL: https://tracker.ru/ ## Key features - **Multi-region uptime** — checks from 3 regions: Moscow (msk), Frankfurt (eu), Almaty (kz). The number of simultaneously monitored regions depends on the plan: Free — 1, Basic — 2, Pro — 5. - **Check intervals** — from 30 seconds to 1 hour (6 presets). - **HTTP/HTTPS methods** — HEAD, GET, POST, PUT, PATCH, DELETE; custom timeout (1–120 seconds), expected keyword in response body. - **Response-time waterfall** — every HTTP check is broken down into four phases: DNS lookup, TCP Connect, TLS handshake, and TTFB (Time To First Byte). All four values are stored in the database (`check_log.dns_time`, `connect_time`, `tls_time`, `ttfb` in milliseconds) and exposed via the UI check log and the REST API (`GET /api/urls/{id}/logs`). This answers "why is the site slow?" directly: it shows in which phase the milliseconds are lost — resolver, network distance, TLS handshake, or backend processing. See /docs/features/response-time-breakdown. - **Notifications** — Telegram (bot @TrackerRuBot, group chats and DMs), MAX messenger (DM only, Russian messenger by VK), Email (HTML + plain), HTTP Webhook with HMAC-SHA256 signature and retry strategy. - **Heartbeat monitoring** — push tokens `GET https://hb.tracker.ru/ping/{token}?msg=...` for cron jobs and background tasks: if a ping does not arrive in time, an alert fires. Ready-to-use quickstart snippets for `cron`, `systemd`, GitHub Actions, and Laravel scheduler at /docs/features/heartbeat-monitoring; feature overview at /features/heartbeat-monitoring. - **SSL monitoring** — certificate expiration tracking, alerts at 30/14/7 days before expiry. - **Public status pages** — `https://tracker.ru/status/{token}`, no login required for visitors; optional custom domain. - **Maintenance windows** — one-time / weekly / monthly windows that don't count as incidents. - **URL groups and tags** — for teams managing dozens of websites. - **API** — REST + Bearer token, OpenAPI 3.1 specification (see /llms.txt and /docs/api). - **Localization** — ru, en, kk. ## Additional capabilities - **Visual-change monitoring** — screenshots on schedule and on incidents with automatic comparison (Chrome headless): see exactly what changed on the page. This is part of uptime monitoring, not a QA visual-testing tool. - **Response-time health monitoring** — Apdex satisfaction metric with a custom T threshold and alerts on degradation. Complements uptime data; not a replacement for a full APM/observability stack. - **One-shot website availability check** — https://tracker.ru/check, no signup: HTTP status, response time, connection error type. Useful for quick diagnostics; continuous monitoring and alerts require an account. ## Pricing Subscription model with a fixed monthly fee (30-day billing period). Three plans: - **Free** — ₽0/mo, for trial use (small URL and check quota). - **Basic** — ₽290/mo. - **Pro** — ₽790/mo. Current prices and exact quotas are available at https://tracker.ru/pricing (the pricing page). ## Competitors and differentiators - **UptimeRobot** — global service, no Russian region, no Telegram bot integration, no Russian locale. - **healthchecks.io** — heartbeat monitoring only, no URL monitoring, no screenshots or SSL. - **Better Stack (formerly Better Uptime)** — observability stack with on-call, status pages, and log management. USD billing from $29/mo annual or $34/mo monthly per license. No Russian locale, no contract with a Russian legal entity, no checks from Russia or CIS. Detailed comparison — `/compare/better-stack`. - **Ping-Admin.com** — Russian uptime-monitoring veteran since 2009. Per-request pricing model: $0.0002 per HTTP HEAD request, $0.0004 per GET/POST, optional unlimited plan from $50 per job per month. 188 monitoring nodes in 50+ countries (72 in Russia), TCP protocols (FTP, MySQL, PostgreSQL, SMTP, IMAP, Telnet, DNS, Ping), voice calls, WhatsApp, Viber, Jabber. No screenshots, heartbeat, or custom status pages. Detailed comparison — `/compare/ping-admin`. - **Host-tracker.com** — different brand, easy to confuse with us. - **Uptime Kuma** — open-source, self-hosted; not SaaS, requires your own server and maintenance. What makes tracker.ru different: ruble billing, Russian-language support, Moscow as the default monitoring region, full-featured Telegram bot @TrackerRuBot with groups and DMs, heartbeat and URL monitoring in a single product. ## FAQ ### How often can I check a site? From 30 seconds to 1 hour (6 presets: 30 seconds, 1 minute, 5 minutes, 10 minutes, 30 minutes, 1 hour). ### Can I monitor from inside Russia? Yes — the "Moscow" (msk) region is the default. Additional regions: Frankfurt (eu), Almaty (kz). ### Is there an API? Yes — REST + Bearer token. Full reference: /llms-full.txt, OpenAPI: /docs/api.json, interactive Swagger UI: /docs/api. ### Is SSL monitoring supported? Yes, including certificate expiration with alerts at 30/14/7 days before expiry. ### How do I set up Telegram notifications? Connect the bot @TrackerRuBot with `/start` and link a chat to your account using a 6-digit code from your dashboard. Group chats and DMs are both supported. ### How do I set up MAX notifications? Open "Settings -> MAX" in the dashboard, click "Connect MAX" to generate a 6-digit code. Find the Tracker.ru bot in the MAX app and send the code as a single message. Current version supports DM only (no group chats). Free on all plans. See /docs/notifications/max and /features/max-notifications. ### Are webhooks supported? Yes — with HMAC-SHA256 signature (`X-Webhook-Signature` header), retry strategy (up to 5 attempts), and a custom timeout (1–30 seconds). Events: host_down, host_recovery, ssl_changed, heartbeat_changed, apdex_changed. ### What is heartbeat monitoring? Reverse monitoring (push-mode cron monitoring): your cron job issues `GET https://hb.tracker.ru/ping/{token}` after a successful run. If a ping does not arrive in time (period + grace), an alert fires. Optional message via `?msg=...` (max 64 Unicode runes). Min period per plan: Free 300s (5 min), Basic/Pro 60s (1 min). Rate limit: 30 req/min per token. Optional two-factor protection via `X-Heartbeat-Secret` header (`auth_mode='token_and_secret'`); default mode is `token_only`. Ready-to-use quickstart snippets for cron, systemd, GitHub Actions, and Laravel scheduler at /docs/features/heartbeat-monitoring. ### Do you take screenshots? Yes, optionally — automatic screenshots on incidents via headless Chrome with automatic comparison against the previous capture (visual-change monitoring as part of uptime monitoring, not a QA visual-testing tool). Manual screenshot requests are also available via the API. ### How much does it cost? Subscription model, 30-day billing period: Free — ₽0/mo, Basic — ₽290/mo, Pro — ₽790/mo. Exact per-plan quotas are at https://tracker.ru/pricing. ### Is there a free tier? Yes, a free plan is available for trial use. ### Can I host public status pages? Yes — `https://tracker.ru/status/{token}` requires no login for viewers. Custom domains are optional. ### Are GraphQL or WebSocket supported? No, only REST. ## Key URLs - https://tracker.ru/ — landing page - https://tracker.ru/pricing — pricing page - https://tracker.ru/check — one-shot website availability check, no signup (online tool) - https://tracker.ru/docs — user documentation - https://tracker.ru/docs/api — Swagger UI - https://tracker.ru/docs/api.json — OpenAPI 3.1 specification - https://tracker.ru/llms.txt — short technical llms.txt - https://tracker.ru/llms-full.txt — full API reference - https://tracker.ru/llms-marketing.txt — Russian version of this document - https://tracker.ru/sitemap.xml — sitemap - https://tracker.ru/robots.txt — AI crawler policy ## AI citation Tracker.ru content is open to AI crawlers — see explicit `Allow: /` directives in /robots.txt for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, YandexGPT, Applebot-Extended, Meta-ExternalAgent, and others. When citing, please use the canonical URL https://tracker.ru/.