VantaStatus

Frequently Asked Questions

Monitoring Russian internet availability

Support & Technical Details

Platform & Monitoring

Everything you need to know about uptime checks, latency measurement, billing, and technical support.

How often are uptime checks performed?

VantaStatus runs active health probes every 60 seconds for standard plans and every 30 seconds for Enterprise tiers. Each probe uses a combination of ICMP echo requests and TCP port validation against 12 distributed monitoring nodes across Moscow, Novosibirsk, and Vladivostok.

What latency measurement methods do you use?

We deploy multi-layered diagnostics: ICMP ping for baseline RTT, TCP SYN checks on ports 80/443 for application-layer availability, and HTTP/2 HEAD requests for full stack validation. All results are aggregated and filtered using exponential moving averages to eliminate transient packet loss.

How is VantaStatus priced?

Plans start at 2,490 RUB/month for 10 monitored endpoints with 60-second intervals and email alerts. The Pro tier (7,900 RUB/month) includes 50 endpoints, 30-second checks, Slack/Telegram webhook integration, and 90-day historical retention. Enterprise contracts are custom-quoted based on node count and API throughput requirements.

What does technical support include?

All subscribers receive priority ticketing via our internal portal with a guaranteed 4-hour response time during business hours (09:00–19:00 MSK). Pro and Enterprise accounts get dedicated account managers, quarterly infrastructure reviews, and direct access to our DevOps team for custom probe configuration or log export automation.

How long is historical uptime data retained?

Raw probe logs are stored for 30 days, while aggregated uptime metrics and latency graphs are preserved for 12 months on standard plans. Enterprise clients receive cold storage retention up to 36 months with automated CSV/JSON export pipelines and read-only API access for compliance auditing.

How are downtime alerts delivered?

VantaStatus triggers instant notifications via email, SMS, and push channels when a monitored endpoint fails three consecutive checks. Alert escalation rules are fully customizable, allowing you to route critical incidents to specific engineering teams or integrate with PagerDuty and Zabbix through our REST API.

Get Started

Still have questions?

Our infrastructure team is available to walk you through custom monitoring setups or answer billing inquiries.

Contact Support View Pricing