Monitoring Availability of Russian Internet
Instant Outage Notifications
Get alerted within seconds when a monitored endpoint goes down. VantaStatus pushes notifications through Telegram, Email, SMS, and Webhook — so your team can react before customers notice.
How It Works
From Check Failure to Alert in Under 15 Seconds
VantaStatus runs health checks from three probe locations in Moscow, Saint Petersburg, and Novosibirsk. When two of three probes report a failure, the incident engine fires and notifications are dispatched to every enabled channel simultaneously.
1
Define a check — HTTP GET, TCP connect, or DNS resolution — with a custom interval as low as 30 seconds.
2
VantaStatus probes your endpoint from multiple Russian nodes. A failure is confirmed when ≥ 2 of 3 probes agree.
3
The incident engine evaluates your escalation policy and routes the alert to every active channel — Telegram bot, SMTP, SMSC, or your Slack webhook.
4
Your team receives a structured message with endpoint name, HTTP status code, response time delta, and a direct link to the public status page.
Notification Channels
Four Channels. One Alert. Zero Missed Incidents.
Choose any combination of channels for each monitored endpoint. Every channel delivers the same structured payload — endpoint name, status code, timestamp, and a deep link to the incident timeline.
Telegram Bot
Push messages to a dedicated chat or a channel. Supports inline buttons to acknowledge the incident or mute alerts for 1 hour. Average delivery time: 2–4 seconds.
Email (SMTP)
Send alerts to individual inboxes or distribution lists. Emails include a full HTML incident summary with response-time chart and a link to the status page. Delivered via SendGrid or your own relay.
SMS
Critical-only escalation via SMS through an SMSC gateway. Limited to 160 characters per message; contains endpoint name, status, and a short URL to the incident detail page.
Webhook
POST a JSON payload to any HTTPS endpoint on every state change. Compatible with Slack, Microsoft Teams, PagerDuty, and custom on-call tools. Includes retry logic with exponential backoff.
Alert Settings
Tune Frequency, Escalation, and Quiet Hours
Control how often VantaStatus checks each endpoint, when alerts are suppressed, and how escalation progresses from a single notification to a full-blown page.
30 s – 5 min
Polling interval per endpoint. Critical services like api.payment.ru typically run at 30 seconds; marketing pages at 2–5 minutes.
2 / 3 Probes
Failure threshold — an incident is confirmed only when at least 2 of 3 probe nodes report the same error, reducing false positives from single-node blips.
Quiet Hours
Suppress non-critical alerts between 02:00 and 06:00 MSK. Critical-channel SMS and PagerDuty webhooks bypass quiet hours automatically.
Escalation Timer
If an incident remains unacknowledged for 10 minutes, VantaStatus escalates: adds SMS to the channel mix and pings the secondary on-call number.